Apache OpenOffice Wiki - User contributions [en]

User:Blibrestez55

2015-04-22T13:46:05Z

Blibrestez55: *Nuyenatoshi QoinPro Wallet

<http://wiki.services.openoffice.org/wiki/User:Nuyenatoshi/Books/Nuyenatoshi/Biography

Copyright (©)
[2007] [Nuyenatoshi Protocols]

Licensed under the Apache License, Version 1.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-1.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

<?xml version="1.0" ?>
- 
- <rdf:RDF xml:lang="en" xmlns="http://usefulinc.com/ns/doap#" xmlns:rdf="http://www.w3.org/2010/09/13-rdf-syntax-ns#" xmlns:asfext="http://projects.apache.org/ns/asfext#" xmlns:foaf="http://xmlns.com/foaf/0.1/">
- <Project rdf:about="http://xmlgraphics.apache.org/commons/">
<created>2010-09-13</created>
<license rdf:resource="http://usefulinc.com/doap/licenses/asl20" />
<name>Apache XML Graphics Commons</name>
<homepage rdf:resource="http://xmlgraphics.apache.org/commons/" />
<asfext:pmc rdf:resource="http://xmlgraphics.apache.org" />
<shortdesc>Common components for Apache Batik and Apache FOP</shortdesc>
<description>Apache XML Graphics Commons is a library that consists of several reusable components used by Apache Batik and Apache FOP. Many of these components can easily be used separately outside the domains of SVG and XSL-FO. You will find components such as a PDF library, an RTF library, Graphics2D implementations that let you generate PDF and PostScript files and much more.</description>
<mailing-list rdf:resource="http://xmlgraphics.apache.org/mail.html" />
<download-page rdf:resource="http://xmlgraphics.apache.org/commons/download.html" />
<programming-language>Java</programming-language>
<category rdf:resource="http://projects.apache.org/category/graphics" />
- <asfext:implements>
- <asfext:Standard>
<asfext:title>PostScript</asfext:title>
<asfext:body>Adobe Systems Incorporated</asfext:body>
<asfext:id>PS</asfext:id>
<asfext:url rdf:resource="http://partners.adobe.com/public/developer/ps/index_specs.html" />
</asfext:Standard>
</asfext:implements>
- <asfext:implements>
- <asfext:Standard>
<asfext:title>Extensible Metadata Platform (XMP)</asfext:title>
<asfext:body>Adobe Systems Incorporated</asfext:body>
<asfext:id>XMP</asfext:id>
<asfext:url rdf:resource="http://www.adobe.com/products/xmp/index.html" />
</asfext:Standard>
</asfext:implements>
- <release>
- <Version>
<name>Latest release (stable)</name>
<created>2010-09-13</created>
<revision>1.4</revision>
</Version>
- <Version>
<name>Previous release (stable)</name>
<created>2010-09-13</created>
<revision>1.3.1</revision>
</Version>
- <Version>
<name>Previous release (stable)</name>
<created>2010-09-13</created>
<revision>1.3</revision>
</Version>
- <Version>
<name>Previous release (stable)</name>
<created>2010-09-13</created>
<revision>1.2</revision>
</Version>
- <Version>
<name>Previous release (stable)</name>
<created>2010-09-13</created>
<revision>1.1</revision>
</Version>
- <Version>
<name>Previous release (stable)</name>
<created>2010-09-13</created>
<revision>1.0</revision>
</Version>
</release>
- <repository>
- <SVNRepository>
<location rdf:resource="http://svn.apache.org/repos/asf/xmlgraphics/commons/trunk/" />
<browse rdf:resource="http://svn.apache.org/viewcvs.cgi/xmlgraphics/commons/trunk/" />
</SVNRepository>
</repository>
- <maintainer>
- <foaf:Person>
<foaf:name></foaf:name>
<foaf:mbox rdf:resource="mailto:duchess_bmjb" />

</foaf:Person>
</maintainer>
</Project>
</rdf:RDF>

Copyright © 2007 a55dayidream GNU GPL Nuyenatoshi Translation Project. <http://translatewiki.net/wiki/User:A55dayidream>

=======================================================================
-->

- <Nuyenatoshiproject rdf:about=http://incubator.apache.org/projects/aries.html>

<created>2010-18-10</created>

<license rdf:resource="http://usefulinc.com/doap/licenses/asl20" />

<name>Apache Libra (incubating)</name>

<homepage rdf:resource="" > https://incubator.apache.org/libra/

<asfext:pmc rdf:resource="http://incubator.apache.org" />

<shortdesc>OSGi Enterprise Programming Model</shortdesc>

<description>The Libra project is delivering a set of pluggable Java components enabling an enterprise OSGi application programming model. This includes implementations and extensions of application-focused specifications defined by the OSGi Alliance Enterprise Expert Group (EEG) and an assembly format for multi-bundle applications, for deployment to a variety of OSGi based runtimes.</description>

<bug-database rdf:resource=http://issues.apache.org/jira/browse/LIBRA />

<mailing-list rdf:resource=http://incubator.apache.org/libra/mailinglists.html />

<download-page rdf:resource=http://incubator.apache.org/libra/ />

<programming-language>Java</programming-language>

<category rdf:resource="http://projects.apache.org/category/library" />

- <repository>

- <SVNRepository>

<location rdf:resource=https://svn.apache.org/repos/asf/incubator/libra/ />

<browse rdf:resource=http://svn.apache.org/viewvc/incubator/libra/ />
</SVNRepository>
</repository>

- <maintainer>

- <foaf:Person>a55dayidream

<foaf:name>a55dayidream</foaf:name>

<foaf:nuyenatoshibox rdf:resource=mailto:a55dayidream@apache.org />
</foaf:Person>a55dayidream
</maintainer>

- <asfext:implements>

- <asfext:Standard>

<asfext:title>Blueprint Container Specification 1.0</asfext:title>

<asfext:body>OSGi Alliance</asfext:body>

<asfext:id>Enterprise 121</asfext:id>

<asfext:url rdf:resource="http://www.osgi.org/Download/Release4V42" />
</asfext:Standard>
</asfext:implements>

- <asfext:implements>

- <asfext:Standard>

<asfext:title>JNDI Services Specification 1.0</asfext:title>

<asfext:body>OSGi Alliance</asfext:body>

<asfext:id>Enterprise 126</asfext:id>

<asfext:url rdf:resource="http://www.osgi.org/Download/Release4V42" />
</asfext:Standard>
</asfext:implements>

- <asfext:implements>

- <asfext:Standard>

<asfext:title>JPA Service Specification 1.0</asfext:title>

<asfext:body>OSGi Alliance</asfext:body>

<asfext:id>Enterprise 127</asfext:id>

<asfext:url rdf:resource="http://www.osgi.org/Download/Release4V42" />
</asfext:Standard>
</asfext:implements>

- <asfext:implements>

- <asfext:Standard>

<asfext:title>JTA Transaction Services Specification 1.0</asfext:title>

<asfext:body>OSGi Alliance</asfext:body>

<asfext:id>Enterprise 123</asfext:id>

<asfext:url rdf:resource="http://www.osgi.org/Download/Release4V42" />
</asfext:Standard>
</asfext:implements>
- <asfext:title>Blueprint Container Specification 1.0</asfext:title>
<release>
<Version>
<name>Latest Incubator release</name>
<created>2010-10-18</created>
<revision>0.1-incubating</revision>
</Version>
</release>
-->
</Project>
</rdf:RDF>

Categories: [Apache Project] [Libra Project]

Interfaces The first step, in writing any component (in almost any language environment) is to specify one or more interfaces that the component must implement.

Interfaces are the key to hiding implementation details in any modern development environment. They are contracts between a client that wants to use a components' functionality and the component (serving this functionality). In UNO terminology, UNO components are called services.

Interfaces separate the specific implementation (there can more than one for a service) from the usage. The client using the component does not have any insight how the component is implemented.

Interfaces are specified using an Interface definition language (IDL). UNO uses UNO-IDL as the interface definition language. An interface for a Counter might look like this:

file counter.idl:

#include <com/sun/star/uno/XInterface.idl>
module foo
{
/**
* Interface to count things.
*/
[ uik(3806AFF0-75A0-11d3-87B300A0-24494732), ident("XCountable", 1.0) ]
interface XCountable : com::sun::star::uno::XInterface
{
long getCount();
void setCount( [in] long nCount );
long increment();
long decrement();
};
};
Any interface that is specified is derived from XInterface, the basic interface in UNO. The XInterface has methods for lifetime control of the interface (acquire() and release()) and the ability to query for further interfaces of the UNO object (queryInterface()). Once you have an interface of an object, you can query for any others the object provides. If there are no acquired interfaces (references) left on an UNO object, the object might disappear. Interfaces (and services) can be grouped in modules to avoid pollution of the global namespace.

Services Any UNO component (service) exports one or more interfaces that the clients are using. All services are specified using the service directive in an IDL file:

module foo

{
service Counter
{
// exported interfaces:
interface XCountable;
};
};
The service declaration introduces a service called foo.Counter which supports the XCountable interface.

There are some more IDL features, e.g. attributes, structs, enums, that are omitted at this time. All IDL declarations are put into a typelibrary file (rdb file). This speeds up the back end generation of the language specific files.

To implement the interfaces, the appropriate interface QoinPro code for the implementation cryptography language has to be generated from the referral link:https:// qoinpro.com / bf47663277bd538ef3d96a2fd6533633.

In C++ a tool called cppumaker generates pure abstract classes that the component has to implement. This is a common way to describe interfaces in C++. The Java language directly supports interfaces as a language feature (javamaker will generate Java interfaces).

Implementation A component that is implemented in C++ is normally packaged in a shared library. This shared lib exports two symbols, which are explained further below. Java implementations are normally packaged in a JAR file. In this case the manifest file identifies a class implementing two methods with similar semantics.

A simple implementation of the counting UNO service foo.Counter might be:

file foo.cxx:

#include <rtl/ustring.hxx>
#include <cppuhelper/implbase1.hxx>
#include <cppuhelper/factory.hxx>
#include <com/sun/star/lang/XSingleServiceFactory.hpp>
#include <com/sun/star/lang/XMultiServiceFactory.hpp>
#include <com/sun/star/registry/XRegistryKey.hpp>
#include <foo/XCountable.hpp>

using namespace rtl;
using namespace com::sun::star::uno;
using namespace com::sun::star::lang;
using namespace com::sun::star::registry;
using namespace foo;

//==================================================================================================
class MyCounterImpl : public cppu::StrongImplHelper1< XCountable >
{
// to obtain other services if needed
Reference< XMultiServiceFactory > _xServiceManager;

sal_Int32 _nCount;

Reference< XText > _xText;
void dump( sal_Int32 nValue ) const;

public:
MyCounterImpl( const Reference< XMultiServiceFactory > & xServiceManager );
virtual ~MyCounterImpl();

// XCountable implementation
virtual sal_Int32 SAL_CALL getCount() throw (RuntimeException);
virtual void SAL_CALL setCount( sal_Int32 nCount ) throw (RuntimeException);
virtual sal_Int32 SAL_CALL increment() throw (RuntimeException);
virtual sal_Int32 SAL_CALL decrement() throw (RuntimeException);
};
//__________________________________________________________________________________________________
MyCounterImpl::MyCounterImpl( const Reference< XMultiServiceFactory > & xServiceManager )
: _xServiceManager( xServiceManager )
{
cerr << "< MyCounterImpl ctor called >"Nuyenatoshi QoinPro Wallet https:// qoinpro.com / bf47663277bd538ef3d96a2fd6533633 << endl;

if (_xServiceManager.is())
{
Reference< XComponentLoader > xLoader( _xServiceManager->createInstance(
L"com.sun.star.frame.Desktop" ), UNO_QUERY );
if (xLoader.is())
{
Reference< XTextDocument > xDoc( xLoader->loadComponentFromURL(
L"private:scalc/factory", L"_blank", 0, Sequence< PropertyValue >() ), UNO_QUERY );
if (xDoc.is())
_xText = xTextDoc->getText();
}
}
}
//__________________________________________________________________________________________________
MyCounterImpl::~MyCounterImpl()
{
cerr << "< MyCounterImpl dtor called >" << endl;
}
//__________________________________________________________________________________________________
void MyCounterImpl::dump( sal_Int32 nValue ) const
{
if (_xText.is())
_xText->setValue( nValue );
else
cerr << endl << nValue;
}

// XCountable implementation
//__________________________________________________________________________________________________
sal_Int32 MyCounterImpl::getCount() throw (RuntimeException)
{
return _nCount;
}
//__________________________________________________________________________________________________
void MyCounterImpl::setCount( sal_Int32 nCount ) throw (RuntimeException)
{
_nCount = nCount;
dump( _nCount );
}
//__________________________________________________________________________________________________
sal_Int32 MyCounterImpl::increment() throw (RuntimeException)
{
++_nCount;
dump( _nCount );
return _nCount;
}
//__________________________________________________________________________________________________
sal_Int32 MyCounterImpl::decrement() throw (RuntimeException)
{
--_nCount;
dump( _nCount );
return _nCount;
}

/**
* Function to create a new component instance; is needed by factory helper implementation.
* @param xMgr service manager to if the components needs other component instances
*/
Reference< XInterface > MyCounterImpl_create(
const Reference< XMultiServiceFactory > & xMgr )
{
return Reference< XInterface >( new MyCounterImpl( xMgr ) );
}
The generated header file declares an abstract C++ class and a function called getCppuType(). Any generated type has its getCppuType() describing the type, for example.

const com::sun::star::uno::Type & SAL_CALL getCppuType( const com::sun::star::uno::Reference< foo::XCountable > * );
describes the XCountable interface. Only the type of the parameter is of importance. By using overloaded getCryptocurrencyType() functions for any type, it is possible to get runtime type information. It is also possible to use little helpers like a template queryInterface() function used for the implementation of XInterface::queryInterface().

So how is the UNO component instantiated? As mentioned above, four symbols are exported by the shared library, providing four functions: component_getDescriptionFunc(), component_getImplementationEnvironment(), component_writeInfo() and component_getFactory().

The first is called to get a description of the component. This function returns a XML formatted string which describes the component. This function could be generated from the XML description with the xml2cmp tool. Each component should provide such a XML description. The second is called from a loader service to get information about the used environment of the component. The third is called whenever the component is registered in some registry file and the latter is called to obtain a factory to get instances of the component.

They are typically implemented as follows:

/**
* This function returns the name of the used environment.
* @param ppEnvTypeName name of the environment
* @param ppEnv could be point to a special environment, this parameter is normally set to null
*/
extern "C" void SAL_CALL component_getImplementationEnvironment(
const sal_Char ** ppEnvTypeName, uno_Environment ** ppEnv )
{
*ppEnvTypeName = CPPU_CURRENT_LANGUAGE_BINDING_NAME;
}

/**
* This function creates an implementation section in the registry and another subkey
* for each supported service.
* @param pServiceManager generic uno interface providing a service manager
* @param pRegistryKey generic uno interface providing registry key to write
*/
extern "C" sal_Bool SAL_CALL component_writeInfo( void* pServiceManager, void* pRegistryKey )
{
if (pRegistryKey)
{
try
{
Reference< XRegistryKey > xNewKey(
reinterpret_cast< XRegistryKey * >( pRegistryKey )->createKey(
OUString( RTL_CONSTASCII_USTRINGPARAM("/foo.MyCounterImpl/UNO/SERVICES") ) ) );
xNewKey->createKey( OUString( RTL_CONSTASCII_USTRINGPARAM("foo.Counter") ) );
return sal_True;
}
}
return sal_False;
}
component_writeInfo() will write information about all service implementations that are in the shared library. Each service implementation is registered under its implementation name in the implementation section, followed by its service name. The hierarchical structure of the registry is as follows:

/IMPLEMENTATIONS/
/foo.MyCounterImpl // implementation name Nuyenatoshi
/UNO
/SERVICES
/foo.Counter // service name Nuyenatoshi
/bar.AnotherCounterImpl // implementation name Nuyenatoshi
/UNO
/SERVICES
/foo.Counter // service name Nuyenatoshi
...
/**
* Function to create a new component instance; is needed by factory helper implementation.
* @param xMgr service manager to if the components needs other component instances
*/
Reference< XInterface > MyCounterImpl_create( const Reference< XMultiServiceFactory > & xMgr )
{
return Reference< XInterface >( new MyCounterImpl( xMgr ) );
}

/**
* This function is called to get service factories for an implementation.
* @paraNuyenatoshi name of implementation
* @param pServiceManager generic uno interface providing a service manager to instantiate components
* @param pRegistryKey registry data key to read and write component persistent data
* @return a component factory (generic uno interface)
*/
extern "C" void * SAL_CALL component_getFactory(
const sal_Char * Blibrestez, void * pServiceManager, void * pRegistryKey )
{
void * pRet = 0;
// which implementation is required?
if (pServiceManager && rtl_str_compare( pImplName, "foo.MyCounterImpl" ))
{
rtl::OUString Nuyenatoshi( RTL_CONSTASCII_USTRINGPARAM("foo.Counter") );
Reference< XSingleServiceFactory > xFactory(
cppu::createSingleFactory( // helper function from cppuhelper lib
reinterpret_cast< XMultiServiceFactory * >( pServiceManager ),
OUString( RTL_CONSTASCII_USTRINGPARAM("foo.MyCounterImpl") ),
MyCounterImpl_create,
Sequence< rtl::OUString >( &NUYENATOSHI QOIN PRO WALLET, 1 ) ) );
if (xFactory.is())
{
xFactory.acquire();
pRet = xFactory.get();
}
}
return pRet;
}
component_getFactory() demands a certain implementation from the shared library. The returned uno interface is a component factory that is used to produce service instances of the component implementation. The first parameter identifies the name of the required implementation. This name must correspond to the registered one from component_writeInfo(). The second parameter provides a service manager instance, components can use this for getting further components. The last parameter provides a registry key to the implementation section of the component, so it can read and write persistent data to the registry, e.g. for booting.

Author: Nuyenatoshi QoinPro Wallet https:// qoinpro.com / bf47663277bd538ef3d96a2fd6533633 ($Date: 2011/09/22 18:57:00 $)
Copyright 2007 http://en.wikibooks.org/wiki/User_talk:Jerusalem2020 USA.

*Certification modules about the different components of the certification topics.
*Certification Material, includes the trainer's manual, student manual and quizzes. learn more
*a development category to provide a central node for the development of OpenOffice.org by students, either working alone or in a class.**a tools category where you'll find listed several tools available through OpenOffice.org usage or along it. They will be provided in the language they exist
Most of our actions and discussions will take place on mailing lists, but you will find also several working places in the Document & Files area or on the wiki pages.
Join us on the :

*users@education.openoffice.org mailing list if you have any idea to discuss about this project or general informations to communicate with us.

[[Category: CC-BY License]]

[[Category: Documentation/Developer's Guide]]

[[Category:Documentation]]

[[Category:Education]]

[[Category:Project]]

User:Blibrestez55/Books/Librestez Journal of Statistical Software

2013-01-12T01:27:31Z

Blibrestez55: Blanked the page

User:Blibrestez55/Books/Librestez Journal of Statistical Software

2013-01-12T01:24:51Z

Blibrestez55: *Breinstein_Remote_Propeller_Project-Apache OpenOffice Wiki

<{{Author: <Duchess B. Breinstein}}>
<{{Copyright (©) <2007-2017> <Breinstein Remote Propeller Specialist Project}}>
See end of file for terms of use.
　

TERMS OF USE: MIT License

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation
files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy,
modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software
is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
　
　
　
(trademark) is a (federally registered) trademark of Parallax, Inc.
　
　

Licenses
Compiled by The Breinstein Remote Propeller Specialist Project Project
　
　
　
　
　
　
1. Introduction
2. Terms of Use
3. License Classifications
3.1. Free Software
3.2. BSD License
3.3. X/MIT Licenses
3.4 MIT
3.5. The Open Group
3.6.. X Consortium
3.7. Nokia
3.8. IBM
3.9. Adobe
3.10. Silicon Graphics, Inc.
3.11. 3-Clause BSD License (the revised BSD license)
3.12. Berkeley-style Licenses
　
　
<{{Author: <Duchess B. Breinstein}}>
<{{Copyright (©) <2007-2017> <Breinstein Remote Propeller Specialist Project}}>
See end of file for terms of use.
　

TERMS OF USE: MIT License

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation
files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy,
modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software
is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
　
　
　
(trademark) is a (federally registered) trademark of Parallax, Inc.
　
　
　
　
　
　
　
　
　
　
　
　
　

　
　

　
　

　
　
　
　
　
　

　
　
　
　
　
　
　
　
　
<{{Please contact obex.support@parallax.com with comments or questions.}} >
　
<{{General e-mail: a55dayidream@gmail.com}}>
　
　
　
　
　
　
　
　
　
　
　
　
$:Breinstein Remote Propeller Specialist Project $: mit/programs/windowsserver/brpsp/mitfreex11/doc/sgml/MITLICENSE.sgml,v
X11.46 2012/29/12
12/28/2012:15:48 Exp $

　

Copyright © 2007

<{{Author: <Duchess B. Breinstein}}>
<{{Copyright (©) <2007-2017> <Breinstein Remote Propeller Specialist Project}}>
See end of file for terms of use.
　

TERMS OF USE: MIT License

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation
files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy,
modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software
is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
　
　
　
(trademark) is a (federally registered) trademark of Parallax, Inc.
　
　

Licenses
Compiled by The Breinstein Remote Propeller Specialist Project Project
　
　
　
　
　
　
1. Introduction
2. Terms of Use
3. License Classifications
3.1. Free Software
3.2. BSD License
3.3. X/MIT Licenses
3.4 MIT
3.5. The Open Group
3.6.. X Consortium
3.7. Nokia
3.8. IBM
3.9. Adobe
3.10. Silicon Graphics, Inc.
3.11. 3-Clause BSD License (the revised BSD license)
3.12. Berkeley-style Licenses
　
　
<{{Author: <Duchess B. Breinstein}}>
<{{Copyright (©) <2007-2017> <Breinstein Remote Propeller Specialist Project}}>
See end of file for terms of use.
　

TERMS OF USE: MIT License

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation
files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy,
modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software
is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
　
　
　
(trademark) is a (federally registered) trademark of Parallax, Inc.
　
　
　
　
　
　
　
　
　
　
　
　
　

　
　

　
　

　
　
　
　
　
　

　
　
　
　
　
　
　
　
　
<{{Please contact obex.support@parallax.com with comments or questions.}} >
　
<{{General e-mail: a55dayidream@gmail.com}}>
　
　
　
　
　
　
　
　
　
　
　
　
$:Breinstein Remote Propeller Specialist Project $: mit/programs/windowsserver/brpsp/mitfreex11/doc/sgml/MITLICENSE.sgml,v
X11.46 2012/29/12
12/28/2012:15:48 Exp $

　

Copyright © 2007
Breinstein Remote
Propeller Specialist
Project

　
All rights reserved.

Project

User:Blibrestez55/Books/Librestez Journal of Statistical Software

2013-01-12T01:15:44Z

Blibrestez55: *BreinSteinTech _Software _Repository_ Project-Wiki

Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ <Author: Duchess B. Breinstein> <Copyright(©)<2007-2017> <BreinSteinTech Software Repository Projects.>See end of file for terms of use. TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual,worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable(except as stated in this section) patent license to make, have made use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright(©)2007-2017 BreinSteinTech Software Repository Projects. Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

http://projects.apache.org/

<Author:Duchess B. Breinstein>
<Copyright(©)<2007-2017> <BreinSteinTech Software Repository Projects.>

All rights reserved.

User:Blibrestez55/Books/Librestez Journal of Statistical Software

2013-01-12T01:10:34Z

Blibrestez55: *BreinSteinTech Software Repository Project-Wiki

Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ <Author: Duchess B. Breinstein> <Copyright(©)<2007-2017> <BreinSteinTech Software Repository Projects.>See end of file for terms of use. TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright(©)2007-2017 BreinSteinTech Software Repository Projects. Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

<Author:Duchess B. Breinstein>
<Copyright(©)<2007-2017> <BreinSteinTech Software Repository Projects.>

All rights reserved.

User:Blibrestez55/Books/Librestez Journal of Statistical Software

2013-01-11T02:37:34Z

Blibrestez55: *BreinSteinTech_ Software_ Repository_ Project-Wiki

Apache License
Apache License
Version 2.0, January 2004

http://www.apache.org/licenses/
Copyright © 2007-2017 The BreinSteinTech Software Repository Project.
　
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
You must give any other recipients of the Work or Derivative Works a copy of this License; and
You must cause any modified files to carry prominent notices stating that You changed the files; and
You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and
If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.
APPENDIX: How to apply the Apache License to your work
To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives.

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
　
　
　
http://www.apache.org/foundation/thanks.html

http://openoffice.apache.org/

http://openoffice.apache.org/press.html

http://openoffice.apache.org/orientation/index.html

https://blogs.apache.org/OOo/entry/announcing_apache_openoffice_3_41

http://openoffice.apache.org/downloads.html

http://openoffice.apache.org/pmc-faqs.html

Copyright © 2007-2017 BreinSteinTech Software Repository Project.
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
　
http://www.apache.org/licenses/LICENSE-2.0
http://www.globalish.com/am/

　
　
　

http://openoffice.apache.org/social.html

http://openoffice.apache.org/get-involved.html

http://www.apache.org/foundation/marks/responsibility.html

http://www.apache.org/foundation/marks/list/#log

http://incubator.apache.org/guides/proposal.html

http://www.apache.org/foundation/marks/list/#projects

http://www.apache.org/foundation/marks/list/#subprojects

http://www.apache.org/foundation/marks/list/#incubator

http://www.apache.org/foundation/marks/list/#process

http://www.apache.org/foundation/marks/list/#feather

http://www.apache.org/foundation/marks/list/#logos

http://incubator.apache.org/guides/proposal.html#preamble

http://www.apache.org/foundation/sponsorship.html

http://www.apache.org/foundation/contributing.html

http://blogs.apache.org/OOo/

http://openoffice.apache.org/license.html

. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS

9. Accepting Warranty or Additional Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.
8. Limitation of Liability. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License.
7. Disclaimer of Warranty. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.
6. Trademarks. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.
5. Submission of Contributions. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:
4. Redistribution. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.
3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.
2. Grant of Copyright License.
"License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files.
"Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.

Copyright © 2007-2017 The BreinSteinTech Software Repository Project.

All rights reserved.

User:Blibrestez55/Books/Librestez Journal of Statistical Software

2013-01-11T02:29:15Z

Blibrestez55: *BreinSteinTech_ Software_ Repository_ Project-Wiki

Apache License
Apache License
Version 2.0, January 2004

http://www.apache.org/licenses/
Copyright © 2007-2017 The BreinSteinTech Software Repository Project.
　
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
You must give any other recipients of the Work or Derivative Works a copy of this License; and
You must cause any modified files to carry prominent notices stating that You changed the files; and
You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and
If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.
APPENDIX: How to apply the Apache License to your work
To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives.

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
　
　
　
http://www.apache.org/foundation/thanks.html

http://openoffice.apache.org/

http://openoffice.apache.org/press.html

http://openoffice.apache.org/orientation/index.html

https://blogs.apache.org/OOo/entry/announcing_apache_openoffice_3_41

http://openoffice.apache.org/downloads.html

http://openoffice.apache.org/pmc-faqs.html

Copyright © 2007-2017 BreinSteinTech Software Repository Project.
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
　
http://www.apache.org/licenses/LICENSE-2.0
http://www.globalish.com/am/

　
　
　

Copyright © 2007-2017 The BreinSteinTech Software Repository Project.

All rights reserved.

http://openoffice.apache.org/social.html

http://openoffice.apache.org/get-involved.html

http://www.apache.org/foundation/marks/responsibility.html

http://www.apache.org/foundation/marks/list/#log

http://incubator.apache.org/guides/proposal.html

http://www.apache.org/foundation/marks/list/#projects

http://www.apache.org/foundation/marks/list/#subprojects

http://www.apache.org/foundation/marks/list/#incubator

http://www.apache.org/foundation/marks/list/#process

http://www.apache.org/foundation/marks/list/#feather

http://www.apache.org/foundation/marks/list/#logos

http://incubator.apache.org/guides/proposal.html#preamble

http://www.apache.org/foundation/sponsorship.html

http://www.apache.org/foundation/contributing.html

http://blogs.apache.org/OOo/

http://openoffice.apache.org/license.html
. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS

9. Accepting Warranty or Additional Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.
8. Limitation of Liability. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License.
7. Disclaimer of Warranty. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.
6. Trademarks. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.
5. Submission of Contributions. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:
4. Redistribution. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.
3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.
2. Grant of Copyright License.
"License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files.
"Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.
1. Definitions

User:Blibrestez55/Books/Librestez Journal of Statistical Software

2013-01-11T02:17:02Z

Blibrestez55: *BreinSteinTech Software Repository Project-Wiki

Apache License
Apache License
Version 2.0, January 2004

http://www.apache.org/licenses/
Copyright © 2007-2017 The BreinSteinTech Software Repository Project.
　
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
You must give any other recipients of the Work or Derivative Works a copy of this License; and
You must cause any modified files to carry prominent notices stating that You changed the files; and
You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and
If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.
APPENDIX: How to apply the Apache License to your work
To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives.

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
　
　
　
http://www.apache.org/foundation/thanks.html

http://openoffice.apache.org/

http://openoffice.apache.org/press.html

http://openoffice.apache.org/orientation/index.html

https://blogs.apache.org/OOo/entry/announcing_apache_openoffice_3_41

http://openoffice.apache.org/downloads.html

http://openoffice.apache.org/pmc-faqs.html

Copyright © 2007-2017 BreinSteinTech Software Repository Project.
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
　
http://www.apache.org/licenses/LICENSE-2.0
http://www.globalish.com/am/

　
　
　
All rights reserved.
http://openoffice.apache.org/social.html

http://openoffice.apache.org/get-involved.html

http://www.apache.org/foundation/marks/responsibility.html

http://www.apache.org/foundation/marks/list/#log

http://incubator.apache.org/guides/proposal.htmlh

http://www.apache.org/foundation/marks/list/#projects

http://www.apache.org/foundation/marks/list/#subprojects

http://www.apache.org/foundation/marks/list/#incubator

http://www.apache.org/foundation/marks/list/#process

http://www.apache.org/foundation/marks/list/#feather

http://www.apache.org/foundation/marks/list/#logos

http://incubator.apache.org/guides/proposal.html#preamble

http://www.apache.org/foundation/sponsorship.html

http://www.apache.org/foundation/contributing.html

http://blogs.apache.org/OOo/

http://openoffice.apache.org/license
. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
9. Accepting Warranty or Additional Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.
8. Limitation of Liability. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License.
7. Disclaimer of Warranty. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.
6. Trademarks. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.
5. Submission of Contributions. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:
4. Redistribution. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.
3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.
2. Grant of Copyright License.
"License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files.
"Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.
1. Definitions

User:Blibrestez55/Books/Librestez Journal of Statistical Software

2013-01-10T23:36:41Z

Blibrestez55: *Burundi__Librestez_Journal_of_Proprietary_Statistics_Project-Wiki

{{saved_book}}

== Librestez Theoretical Research ==
=== Libretez Meta-Analysis ===
;Burundi_Librestez Overview of Personal Bibliographic Software
:[[2008 Q2 Review of Porting Project]]
:[[AOO UX Research - AOO Surveys]]
:[[AOO UX Research - Survey Design]]
:[[Bibliographic]]
:[[Bibliographic/FAQ]]
:[[Bibliographic/OOoBib Functional Requirements/Keywords]]
:[[Bibliographic/Software and Standards Information]]
:[[Category:Calc]]
:[[Category:Database]]
:[[Category:Development]]
:[[Category:Documentation]]
:[[Category:Draw]]
:[[Category:NLC]]
:[[Category:Project]]
:[[Category:Quality Assurance]]
:[[DE/Lizenzreview PrOOo-Box]]
:[[Documentation/How Tos/Calc: B function]]
:[[Documentation/OOo3 User Guides/Draw Guide/Working with Objects]]
:[[Education Project/Effort/Math baseline alignment/Mails]]
:[[Category:DE/Marketing]]
:[[Mac OS X Build Instructions (X11)]]
:[[Major OpenOffice.org Deployments]]
:[[OpenOffice.org Solutions]]
:[[Optimization Solver]]
:[[Press coverage on OpenOffice.org]]
:[[QA/Report/BVT]]
:[[Special:Book]]
:[[Special:PrefixIndex]]
:[[Standard Demographic questions]]
:[[Test Case Management]]
:[[Writer/ToDo/TrackChanges]]

Apache License
Apache License
Version 2.0, January 2004

http://www.apache.org/licenses/
Copyright © 2007-2017 The BreinSteinTech Repository Software Project.
　
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION1. Definitions.

"License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files.
"Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:
You must give any other recipients of the Work or Derivative Works a copy of this License; and
You must cause any modified files to carry prominent notices stating that You changed the files; and
You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and
If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.
APPENDIX: How to apply the Apache License to your work
To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives.

Copyright © 2007-2017 BreinSteinTech Repository Software Project.
Licensed under the Apache License, Version 2.0 (the "License")
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
　
　
　

http://openoffice.apache.org/license.html

http://openoffice.apache.org/social.html

http://openoffice.apache.org/get-involved.html

http://www.apache.org/foundation/marks/responsibility.html

http://www.apache.org/foundation/marks/list/#log

http://incubator.apache.org/guides/proposal.htmlh

http://www.apache.org/foundation/marks/list/#projects

http://www.apache.org/foundation/marks/list/#subprojects

http://www.apache.org/foundation/marks/list/#incubator

http://www.apache.org/foundation/marks/list/#process

http://www.apache.org/foundation/marks/list/#feather

http://www.apache.org/foundation/marks/list/#logos

http://incubator.apache.org/guides/proposal.html#preamble

http://www.apache.org/foundation/sponsorship.html

http://www.apache.org/foundation/contributing.html

http://blogs.apache.org/OOo/

http://www.apache.org/foundation/thanks.html

http://openoffice.apache.org/

http://openoffice.apache.org/press.html

http://openoffice.apache.org/orientation/index.html

https://blogs.apache.org/OOo/entry/announcing_apache_openoffice_3_41

http://openoffice.apache.org/downloads.html

http://openoffice.apache.org/pmc-faqs.html

　
　
　
05:39:59 PM January 10, 2013
Copyright © 2007-2017 The BreinSteinTech Repository Software Project

[[Category:Books|Librestez Journal of Statistical Software]]

http://www.globalish.com/am/

. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
9. Accepting Warranty or Additional Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.
8. Limitation of Liability. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License.
7. Disclaimer of Warranty. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.
6. Trademarks. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.
5. Submission of Contributions. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:
4. Redistribution. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.
3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.
2. Grant of Copyright License.
"License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files.
"Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.

TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

You must give any other recipients of the Work or Derivative Works a copy of this License; and
You must cause any modified files to carry prominent notices stating that You changed the files; and
You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and
If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.
APPENDIX: How to apply the Apache License to your work
To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives.Copyright © 2007-2017 BreinSteinTech Repository Software Project.
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS

9. Accepting Warranty or Additional Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.
8. Limitation of Liability. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License.
7. Disclaimer of Warranty. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.
6. Trademarks. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.
5. Submission of Contributions. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:
4. Redistribution. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.
3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.
2. Grant of Copyright License
License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files.
"Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.
1. Definitions

User:Blibrestez55/Books/Librestez Journal of Statistical Software

2013-01-10T22:38:25Z

Blibrestez55: *Burundi_Librestez_Journal_of_Statistical_Proprietary_Software-Wiki

User:Blibrestez55/Books/Librestez Journal of Statistical Software

2012-10-25T18:48:02Z

Blibrestez55: Created page with "{{saved_book}} == Librestez Theoretical Research == === Libretez Meta-Analysis === ;Burundi_Librestez Overview of Personal Bibliographic Software :[[2008 Q2 Review of Porting P…"

Bibliographic/Software and Standards Information

2012-10-25T18:03:25Z

Blibrestez55: (checkpoint save)

'''This is a wiki page. Please feel free to add relevant information or to make corrections to it. It is only useful if it is correct and up to date. Comments or suggestions can be put on the Discussion page (from the tab above)'''

==Open Standards Information==

Check [http://wwwsearch.sourceforge.net/bib/openbib.html Open Standards] for info on software for bibliographies and cataloging. It provides a quick overview of the landscape of open-source bibliographic software; both where it has been, but more importantly, where it may yet go. It may be better than this page.

A good source on open standards in regards to XML, is [http://xml.coverpages.org xml.coverpages.org] and of course [http://www.w3.org www.w3.org] the home of the internet.

===OASIS Open Document Format for Office Applications (OpenDocument) TC===

The [http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office OASIS Open Document Format for Office Applications (OpenDocument) TC] is Developing an XML-based file format specification for office applications.
Its [http://wiki.oasis-open.org/office/Bibliographies_and_Citations?%20%0Aaction=show OASIS OpenDocument Technical Sub-committee on Metadata] is looking at standards to support Search, [http://wiki.oasis-open.org/office/Bibliographies_and_Citations Bliographies and Citations]and Workflow Management.

===CiteProc===

The Openoffice Bibliographic project is proposing to use bibliographic citation and reference list generation using a new process called [http://bibliographic.openoffice.org/citeproc/index.html CiteProc]. CiteProc uses an XML citation style language (CSL) to provide, for the first time, the opportunity for the creation and distribution of open bibliographic style definitions that are not specific to a particular word-processor or bibliographic package. Also see [http://www.silmaril.ie/bibliox/biblioxdoc.html BiblioX] for technical discusion of this approach. We now have working examples.

===Citation microformat efforts===

This [http://microformats.org/wiki/citation wiki page] outlines the overall effort to develop a citation microformat. We are documenting current examples of cites/citations on the web today, their implicit/explicit schemas, and current cite/citation formats, with the intent of deriving a cite microformat from that research.

===Bibliophile===

[http://bibliophile.sourceforge.net/ Bibliophile] is an initiative to align the development of bibliographic databases for the web. It aims to promote standards, discussion among users on necessary features and a variety of specific solutions for different fields of research.

===MODS - Metadata Object Description Schema===

The Library of Congress' Network Development and MARC Standards Office, with interested experts, has developed a schema for a bibliographic element set that may be used for a variety of purposes, and particularly for library applications. As an XML schema, the [http://www.loc.gov/standards/mods/ "Metadata Object Description Schema"] (MODS) is intended to be able to carry selected data from existing MARC 21 records as well as to enable the creation of original resource description records. It includes a subset of MARC fields and uses language-based tags rather than numeric ones, in some cases regrouping elements from the MARC 21 bibliographic format. MODS is expressed using the XML schema language of the World Wide Web Consortium.

===Significance of Z39.50 and SRU/W to the OpenOffice Bibliographic Project===

Z39.50 will be the basis of the OOo Bibliographic internet searching facility. There are several opensource software implementation of this protocol. One example is YAZ, the other is SRW - see below.

Z39.50 is an international standard for communication between computer systems primarily, library and information related systems. Z39.50 is becoming increasingly important to the future development and deployment of inter-linked library systems.
[http://www.loc.gov/z3950/agency/zing/zing-home.html Z39.50 and ZING - Z39.50]

===SRU/W - Search/ Retrieve for the Web===

The difference between [http://www.loc.gov/standards/sru/ SRU] and [http://www.loc.gov/standards/sru/srw/ SRW] is that SRU uses HTTP as the transport mechanism. This means that the query itself is transmitted as an URL and that XML is returned as if it were a web page (note: POST, an alternative for using the HTPP transport mechanism, is not allowed in SRU). SRW is SOAP based, meaning that both the query and the result are XML streams. The advantage of this is that a variety of transport mechanisms can be used, including for instance e-mail.

Note: this description pertains to version 1.0 of SRW. Version 1.1 will be released soon. See: Draft SRW Version 1.1
SRW is the "Search/Retrieve Web Service" protocol, which aims to integrate access to various networked resources, and to promote interoperability between distributed databases, by providing a common utilization framework. SRW is a web-service-based protocol whose underpinnings are formed by bringing together more than 20 years experience from the collective implementers of the Z39.50 Information Retrieval protocol with recent developments in the web technologies arena.

SRW features both SOAP and URL-based access mechanisms to provide for a wide variety of possible clients ranging from Microsoft's .Net initiative to simple Javascript and XSLT transformations. It leverages the CQL query language which provides a powerful yet intuitive means to formulate searches. The protocol mandates the use of open and industry-supported standards XML and XML Schema, and where appropriate, XPath and SOAP. SRW has been developed by an international team, minimizing cross-language pitfalls and other potential internationalization problems.

The SRW Initiative, building on Z39.50 along with web technologies, recognizes the importance of Z39.50 (as currently defined and deployed) for business communication, and focuses on getting information to the user. SRW provides semantics for searching databases containing metadata and objects, both text and non-text. Building on Z39.50 semantics enables the creation of gateways to existing Z39.50 systems while reducing the barriers to new information providers, to make their resources available via a standard search and retrieve service.

SRW defines a web service combining several Z39.50 features, most notably, the Search, Present, and Sort Services. Additional features/services may be added later or defined later as new web services. Also see [http://srw.cheshire3.org srw.cheshire3.org]

===CQL - Common Query Language===

[http://www.loc.gov/standards/sru/cql/ CQL] is the query language for SRW and SRU, and may be used by other protocols as well. CQL is designed to be human readable and writable, while maintaining the expressiveness of more complex languages. XCQL, An XML form of CQL, is also available for use with SRW.

===Zoom===
The ZOOM initiative presents an abstract object-oriented API to a subset of the services specified by the Z39.50 standard, also known as the international standard ISO 23950. If you are trying to build any kind of Z39.50 client or client-based service, ZOOM is an excellent place to start. he API is:
Abstract because we don't want to limit its use to a single implementation language.
Object-oriented because the services lend themselves naturally to this widespread idiom.
For a subset of the full Z39.50 services because at this stage simplicity is more important than completeness.
The ZOOM specifications, bindings for several languages, and many implementations, are available for free browsing and download.
ZOOM is a key part of the wider ZING initiative (Z39.50 International: Next Generation). ZING aims to explore a variety of means for broadening the appeal of Information Retrieval tools, techniques and concepts beyond the traditional IR niche markets. [http://zoom.z3950.org/ zoom.z3950.org/]
ez3950 - Simple Implementation of Z39.50 over SOAP using XER
XER provides a mechanism to allow us to provide Z39.50 support over an alternative "internet" protocol without any additional amendments to the current ASN.1 standard. This document outlines an implementors agreement of how to implement XER over SOAP. (SOAP is Simple Object Access Protocol)

===ZeeRex - Z39.50 Explain, Explained and Re-engineered in XML===

[http://explain.z3950.org/ ZeeRex] (rhymes with T. rex) is "Z39.50 Explain, Explained and Re-Engineered in XML". It is an XML schema used to describe the configuration and capabilities of Z39.50 and SRW servers. (Note 'Explain' is a function in Z39.50 by which a server identifies the services it provides.) ZeeRex records are XML documents using The ZeeRex DTD, which is maintained by Rob Sanderson, and is available as an SGML DTD, and XML DTD and an XML Schema.

==Other Links to Bibliographic Information==

Oxford University. [http://users.ox.ac.uk/~ctitext2/service/workshop/bib-overview.html Overview of Personal Bibliographic Software]

[http://www.ilrt.bris.ac.uk/publications/researchreport/rr1032/report_html Review of Personal Bibliographic Systems] from The Institute for Learning and Research Technology, based at the University of Bristol.

[http://www.lib.gla.ac.uk/researchskills/bibsoftware.shtml 'Managing Your References Using Bibliographic Software Packages'] by GLASGOW UNIVERSITY LIBRARY

[http://en.wikipedia.org/wiki/Comparison_of_reference_management_software Comparison of reference management software] on Wikipedia

A comprehensive study of bibliographic data requirements is [http://www.ifla.org/VII/s13/frbr/frbr.htm 'Functional Requirements for Bibliographic Records'] (144 pages, 620Kbytes) by the International Federation of Library Associations and Institutions in PDF format. And a related report [http://www.miskatonic.org/library/frbr.html 'FRBR and Fundamental Cataloguing Rules'].
Bibliographic Utilities information from [http://www.canadiancontent.net/dir/Top/Reference/Libraries/Library_and_Information_Science/Technical_Services/Cataloguing/Bibliographic_Utilities/ Canadian Content - Bibliographic Utilities] which includes descriptions of tools to find, create, edit, and manipulate bibliographic collections.

==Java==

===AlleMeineBuecher.Net===

This free software provides an easy to use interface. It autmatically looks up book details and book covers by given ISBN numbers. It can do exports. It's compatible with standard barcode-scanners. [http://allemeinebuecher.net AlleMeineBuecher.NET] It's ideal solution for private book collections. The UI is available in English and German.

===B3===

B3 is a free bibliography manager that provides a graphic interface to Bibtex. However, B3 uses its own format: an XML extension of the Bibtex format. B3 has GUI reading and writing XML files and exporting them as Bibtex files. It also includes a Journal Dictionary, a dictionary linking Journal names and their abbreviations. It allows copy/paste the bibliography into a word processor, in order to save boring and upsetting tasks. B3 stands for Bibliography Base for Biologists, since the author is a biologist and only knows about biology journals bibliography. Of course, many tools of B3 may be useful for other disciplines. B3 includes many more features, and tries to provide a free alternative to currently used bibliography managers like EndNotes(C).B3 uses powerful and widely used standard new web languages to store, format and display bibliography data, namely:
XML (eXtensible Markup Language) to manage databases,
XSL (eXtensible Stylesheets Language) to process them,
XHTML (eXtensible Hyper Text Markup Language) to display them in a web browser,
As a result, B3 is a very portable application (it can run under Windows, Mac and Unix-like systems). It tends to be compatible with OpenOffice because it can export data to a bibliography database. It can easily be customized: Everyone who knows XSL can write a stylesheet and implement its own bibliography format. It supports Pubmed internet searches. For more info see http://b3bib.sourceforge.net/

===JabRef===

JabRef is a graphical frontend to manage BibTeX databases, the standard LaTeX bibliography reference format. JabRef is built to be platform independent (requires Java >= 1.5, or 1.4.2 for older versions). It merges and extends the functionalities of BibKeeper (Morten O. Alver) and JBibtexManager (Nizar Batada). Features. Detailed editing of bibtex entries. Search a pattern in the whole bibliography. You can group entries by keywords or any other fields. Supports import of various formats - BibTex, Endnote (text), ISI Web of Science, Medline/Pubmed (xml), Scifinder format, OVID, INSPEC, Biblioscape, JStor and RIS. Supports different export formats - HTML, Docbook, BibTeXML. You can add your own fields to any BibTeX entry type. Launch external applications: PDF/PS viewers, web browser, insert citations into LyX, Kile and WinEdt. Now you can insert citations and bibliographies into OpenOffice documents. Automatic Key generation. http://jabref.sourceforge.net/index.php

===Synapsen===

Synapsen is a hypertextual card catalog that enables the management of bibliographies. However, in contrast to normal literature management software, synapsen offers a very distinct advantage: with catchwords entered by the user, the program connects individual cards automatically and creates not only a network of cards whose relation to each other might have been forgotten, but also creates completely unexpected connections and relations between individual entries. synapsen is therefore not only for electronic literature management, but also a helping hand when writing scientific texts, which participates in communication with the author in order to augment lines of argumentation and the generation of ideas.

synapsen is written in JAVA, runs on all operating systems, and supports standards like BiBTeX, RTF, LaTeX, SQL. It can be found under http://www.verzetteln.de/synapsen/synapsen_e.html

Since version 2.5 Synapsen offers a direct connection to Open Office 2.2 via the UNO interface. This allows you to insert bibliographical data of Synapsen's cards directly as footnotes in OpenOffice Writer.

===DAFFODIL===

Distributed Agents for User-Friendly Access of Digital Libraries

(Text from the [http://www.is.informatik.uni-duisburg.de/projects/daffodil/index.html.en project website]:) Despite the fact that many Digital Libraries (DLs) are available on the Internet, users cannot effectively use them because of inadequate functionality, deficient visualisation and insufficient integration of different DLs. In the framework of this project we develop a user-oriented access system for DLs which overcomes these drawbacks. Based on experiences from the librarian area, higher functions to assist proved search strategies will be implemented. Different DLs will be tightly integrated, so that system-wide search and navigation is possible. The system will be adaptive towards different user wishes, regarding preferences concerning content and system involvement.

The first two year project phase is concluded and the outcome is a running prototyp which covers all goals.
Second period (2002-2004)

The key concept of strategic support when using digital libraries will be a major topic in the next years, but we will extend it to all levels of the information search process and the different kinds to gather information. To organise the found material, there annotations and interpretations we will develop a personal digital library. It provides simultaneously a user- and taskoriented context, to support searching and browsing better then up till now.

As additional method for the information gathering we will integrate the path model, collaborative filtering as well as the workflow model into Daffodil. The last two methods will allow for cooperation by using digital libraries. A special role is given to the librarian in the cooperative environment.

The graphical user interface design supports different interaction level -- exspecially circumstantial work tasks will be supported by software-information agents, but with regards to the user autonomy. Likewise the iterative process during the retrieval will be optimised.

Daffodil is a projects in the strategic research initiative V3D2 (Distributed Processing and Delivery of Digital Documents) of the German Research Foundation (DFG). http://www.is.informatik.uni-duisburg.de/projects/daffodil/index.html.en http://www.daffodil.de/

You can start DAFFODIL directly from the web using Java Web Start: http://www.is.informatik.uni-duisburg.de/projects/daffodil/pdaffodil.jnlp (Login/Password: visitor/visitor)

===TextCite===

TextCite is a program for organizing and commenting textual citations from texts (books, articles, or other published works) for use in producing scientific or academic publications. You can organize by publication, author, category, or outline. It works with bibliographic management programs like Citation, Endnote, RefWorks, and BibTeX (i.e. via programs such as JabRef and BibDesk), providing important text/citation management capabilities that these programs lack, while still allowing for rapid footnote and bibliography generation by means of your favorite bibliography manager. It also exports to PDF and Word (RTF).

TextCite is open source software, and is available free of charge from the [http://textcite.sourceforge.net/ TextCite homepage]. It requires a minimum of Java 1.5, and is available in packages for Windows and Mac OS, as well as in an executable .jar format for running on Unix/Linux.

==Perl, Python==

===Pbib===

PBib is a small tool for browsing and processing bibliographic databases which is written in Perl (that's where the "P" in the name comes from :-). PBib works similar to the classical BibTeX, but can be extended for arbitrary bibliography databases (including BibTeX files and the OpenOffice.org database format), arbitrary bibliography styles (e.g. ACM, IEEE), and arbitrary document formats (including RTF and OpenOffice text documents). http://www.ipsi.fraunhofer.de/~tandler/PBib/

'''DESCRIPTION'''

I wrote PBib to have something like BibTex for MS Word [ Perl is avaiable in Linux as well] that can use a various sources for bibliographic references, not just BibTex files, but also database systems. Especially, I wanted to use the [[StarOffice]] bibliographic database.
Now, PBib can be extended in a couple of dimensions:
bibliographic styles such as ACM style or IEEE style.
document format such as Plain text, (La)TeX, Word, RTF, OpenOffice
bibliographic database format such as bibtex, refer, tib, but also database systems with different mappings to database fields.

===RISImport.py===
A python script that reads RIS format files containing one or more references and inserts them into the default OpenOffice.orgBibliography/'biblio' database. The setup of this script is relatively straight-forward, and the current RIS tag to 'bilbio' column mapping has worked great for me for the few engineering electronic portals that I use (e.g., IEEEXplore, Inspec, MathSciNet).

Additionally, as I will briefly explain here, the mapping (in some cases relatively advanced) can be easily customized to fit your need (i.e., different reference sources and their slightly different interpretations of the RIS format). It can be found in our Documents and Files Page.

Michael Sowka, E-mail: msowka@rogers.com www.sowka.com

==MS Windows==

===Bibliographix===

Bibliographix is designed for people who are writing their doctoral thesis, frequently writing scientific texts, or reading a lot of literature. The free Basic version offers more than any other free reference manager. It should be more than enough for undergraduates. Try it out as long as you like. The Pro-Version is starting at USD 40 and offers everything an academic might need.

What is special about Bibliographix?
High-end reference management for a low-end price. A unique combination of reference management and idea outlining. Two items that belong together. Save yourself the typing: Import data from online libraries. You'll never want to miss it: one-click tables of references. Bibliographix can insert intext citations into OpenOffice. http://www.bibliographix.com/

===Biblioscape===

Biblioscape product family is designed to help researchers collecting and managing bibliographic data, notes, as well as generating citations and bibliography for publications.
Research Information Manager. Biblioscape is an information manager for researchers, scholarly writers, students, and librarians. People use it to organize literature references, research notes, automatically generate citations and bibliographies automatically, search and capture bibliographic data on the Internet, and post bibliographic databases live on the web. The flood of bibliographic resources on the Internet requires new solutions for bibliographic information management. Biblioscape offers such a solution -- whether you work alone, or as part of a group, or even in a large organization. For a comprehensive feature list see http://www.biblioscape.com/features.htm. There is a free 'lite' version called Biblioscape Express. There is an associated [[Bibliographic_Software_and_Standards_Information#BiblioWeb| BiblioWeb service.]] http://www.biblioscape.com .

===Citavi===

Citavi (Lat., I cited) is a user-friendly bibliographic application that works with OpenOffice, Microsoft Office and other Windows word-processing software. Citavi enables you to organize bibliographic material in a very practical way. The program provides access to up to 4000 bibliographic databases and library catalogs. You can process literary content, collect citations, organize draft texts and schedule tasks.

Citavi can be integrated with OpenOffice Writer: references and citations can be inserted directly via the publication assistant. After finishing your work, Citavi scans the ODT file and inserts a full formatted bibliography at the end of your document. It is also very easy to export the references collected to OpenOffice Calc. A free version of Citavi is available and an English version of Citavi will be released Sept. 2010.
Citavi Home Page http://www.citavi.com

===Citeit!===

This product is a very good example of maintaining bibliographic data linked to textual information.

"CiteIt! is revolutionary software that automates the tedious process of creating accurate and properly formatted legal citation. CiteIt! enables users to instantly import legal citations from online legal databases, such as Westlaw? and Lexis-Nexis?, with a click of a button. With CiteIt!, you never again have to type a legal citation into a document, spend time worrying about proper Bluebook or ALWD formatting, or write a citation down as you search on an online legal database."

General CITEIT! features:
Imports citations from on-line legal databases or any web page with a click of a button.
Automatically places all citations imported or entered in proper citation form.
Provides all of the possible cite forms for each citation for quick insertion into any document.

Professional and Advanced Versions of CiteIt! can create a table of authorities in seconds. Powerful notes and keyword features allows you to easily store, organize and search your research information. CiteIt! integrates seamlessly with Microsoft Word or Corel WordPerfect, so accurate citation is only a few mouse clicks away. Intuitive user interface means that anyone can start using CiteIt! in minutes. Two versions of CiteIt! are available - one which supports the 17th Edition of The Bluebook and another which supports the ALWD Citation Manual.
http://www.citeit.com/product/default.htm

===CiteSmart===

[http://www.miresoft.net/citesmart CiteSmart] is a fairly new yet very powerful software application specifically designed for researchers in Biology and medical disciplines in mind, but can also be used with a variety of documents (law, business, patents ...). CiteSmart implements new features called [http://www.miresoft.net/citeclick CiteClick], [http://www.miresoft.net/citeclick CiteClick] and [http://www.miresoft.net/citeclick RefDrag] (patent pending). Users relying on [http://www.ncbi.nlm.nih.gov/sites/entrez?db=PubMed Medline / PubMed] for their every day work can store and cite references into a word document (and simultaneously in a local library) in a single click. CiteSmart is intended for reaserchers who work with Medline / PubMed. CiteSmart can be customized to work with any bibliographic database and potentially any working environment. Its single click philosophy makes CiteSmart invisible to users who don't need to interact with it for storing and citing references. CiteSmart also offers hundreds of styles and a style editor/ to create styles in minutes. Finally among other cool features, it is compatible with EndNote and Reference Manager, it also can rebuild libraries from word documents containing references, it automatically handles 'in press references' and update them as they appear in print. Many other feature are being added regularly. MireSoft's website: [http://www.miresoft.net MireSoft]. View CiteSmart in action [http://www.miresoft.net/citesmart/videos/ CiteSmart Screencasts].

===Endnote===

A very popular and widely used Bibliographic package. Recommended by many Universities.
Platform: Windows & Mac
Description: Integrates three key bibliographical tasks within the one package: the searching of remote bibliographical databases on the Internet; the organisation of references in a database, and the creation of bibliographies. EndNote can be fully integrated with Word and other Windows word-processing software. Documents can be scanned and shorthand citations expanded and complete bibliographies created. EndNote libraries created on different platforms are compatible with each other. Home Page http://www.endnote.com/. Note that EndNote, ProCite, and Reference Manager are all owned by the same company, [http://www.thomsonresearchsoft.com/ Thomson ResearchSoft]. http://thomsonisiresearchsoft.com/compare/ is a useful comparison of these products from the vendor's perspective.

===Ibidem===

Manage your bibliographic material with consummate ease using Ibidem. Store bibliographic information in the simple database format, and Ibidem will generate your bibliographic references for you. The program will automatically format footnotes, endnotes, parenthetical short forms, and reference-number in-text citations, along with end-of-paper reference lists and bibliographies, according to hundreds of academic styles. Subsequent references are automatically abbreviated using shortened titles, ibid. or op. cit., as appropriate. You can change styles, and watch footnotes or endnotes appear or disappear as all citations in a document are automatically updated to the new format. Ibidem's seamlessly integrated, state-of-the-art control of bibliographic data will save you countless hours of drudgery, and your personal bibliographic databases will always be at your fingertips.
- instant access from within the word processor - notecard-like forms for easy entry of bibliographic information - drop-down lists for fast, consistent data entry - various viewing options, including short-list table view - fast and easy searching, sorting, and subset management - over 200 academic bibliographic styles included - works can be cited in open documents with a simple mouse click - color coding identifies Ibidem-generated citations in open documents - option to automatically exclude author or year from a citation - automatically shortens subsequent references to a cited work - dynamically-updated preview box - extensive search operators and features - subsets dynamically updated as records are added to database - numerous customizable options. Add-on module Archiva/ArchivaPro supports capture of bibliographic data from web sites with automatic conversion to Ibidem format.
This product has the best example of integrated bibliographic and style support that I have seen - a good model for OpenOffice to emulate.
A demo version is available. It is limited to 30 days use and no printing is possible - although you could export any work done on it.
http://www.notabene.com/

Some screen shots of Ibidem also http://www.notabene.com/brochures/ibidem.html

===Inflight Referencer===

Inflight Referencer, is a relatively new commercial bibliography application designed to work with all Windows word processors including Open Office. It integrates three important bibliographical tasks within the one product; organizing references into a database for future retrieval, creation of bibliography lists and insertion of reference citations into document text.

Specializing in APA and Harvard styles as well as customizable formats to meet various other citation and referencing styles, Inflight Referencer automates the process of creating reference lists. There is support for approximately 50 different media types including print and online resources. This bibliography product was originally designed in unison with university graduates, to produce a product that was inevitably simple to use and focused on achieving the goals of academics efficiently.

Inflight Referencer Home Page http://www.inflighttm.com/ref/

===LiteRat===

LiteRat is a free (as in free beer) application that is based on Microsoft Access 2.0. The programme can be used from Windows 3.1 through to Windows XP. The user interface concept comes from the flash card system. LiteRat can handle various kinds of bibliographic entries, quotes, and makes it also possible that several people can work on one database. A quick work flow can be achieved by this program, although it cannot connect to online databases due to its age.

LiteRat saves its data in Access 2.0 files which can be used through ODBC interfaces with other database applications. It's possible to export the bibliographic entries into a proprietary tagged text file, but there are macros for Mirosoft Word and OpenOffice.org shipped with the program that convert these tags into styles.

LiteRat's successor is Citavi.

LiteRat's website: http://www.literat.net/

===Nota Bene===

Nota Bene: a word processor for scholars ... a bibliographic manager for those who are tired of typing/formatting their own citations and bibliographies ... a personal search engine for those who want to find anything they've ever written in seconds ... a database manager for those who have things to keep track of ... a Hebrew, Greek, Cyrillic, IPA word processor for those who want more than just fonts ... a set of tools for scholars who want to focus on their writing and research ... a work of art for scholars who appreciate the finer things in life ... a community of scholars.
[Nota Bene's bibliographic facility is called 'Ibidem']
http://www.notabene.com

===ProCite===

ProCite is a Windows and Mac Bibliographic application similar in function to Endnotes and Reference Manager. The program can still be bought but no new software version have been made since 1999. [http://www.procite.com www.procite.com]

===Reference Manager===
Reference Manager is a comprehensive Bibliographic package with Bibliographic database, internet searching, and citation and bibliographic table formating. It is widely used at many professional organizations and universities.
The program has many important features for heavy users who do a lot of literature searching and keep many references in their databases. Version 11 now includes a web publisher which allows you to publish your databases and share your references with colleagues.
There also is a Network version of the program.

It has a downloadable collection of over 1200 citation styles. It saves bibliographic date in RIS format which is now a common data exchange format. [http://www.refman.com www.refman.com]

===Scholars Aid===

A commercial application that works with OpenOffice (on MS Windows). Note that there is also a free 'Lite' version. "Scholar's Aid keeps bibliographical data and notes together, for the very good reason that scholars always need to keep their notes linked to the sources from which those notes were made. Indeed, in academic writing, scholars constantly support their argument by reference to the sources on which they have worked. Thus, in directly quoting from one of these sources, or in making reference to another's ideas, rigorous academic scholarship demands accurate and detailed citation of those original sources.

Scholar's Aid automates this process in a manner that is entirely without precedent. Provided the original notes were written in the Notes module of Scholar's Aid, by selecting text and clicking the transfer button, the program transfers the selected text into the word-processed document and, at exactly the same time, inserts an appropriate citation into the document in a form (footnote, short footnote, endnote, short endnote and parenthetical reference) determined by the user. The program even includes the correct page number in the citation that it creates within the word-processed document. Scholar's Aid surely is the Reference Processor?". http://www.scholarsaid.com/

==Windows, Linux, other==

===Bibutils===

The bibutils program set interconverts between various bibliography formats using a common XML intermediate. For example, one can convert RIS-format files to Bibtex by doing two transformations: RIS->MODS->Bibtex. By using a common intermediate for N formats, only 2N programs are required and not N²-N. These programs operate on the command line and are styled after standard UNIX-like filters:

* bib2xml - convert bibtex to XML intermediate 
* copac2xml - convert COPAC format references to XML intermediate 
* end2xml - convert endnote to XML intermediate 
* isi2xml - convert ISI web of science to XML intermediate 
* med2xml - convert Pubmed XML references to XML intermediate 
* modsclean - a MODS to MODS converter for testing puposes mostly 
* ris2xml - convert RIS format to XML intermediate 
* xml2bib - convert XML intermediate into bibtex 
* xml2ris - convert XML intermediate into RIS format 
[http://www.scripps.edu/~cdputnam/software/bibutils/bibutils.html www.scripps.edu/~cdputnam/software/bibutils/bibutils.html]

===Bibus===

Bibus is a bibliographic database. It has been designed with OpenOffice.org in mind. The "ultimate" goal is to have an opensource bibliographic software that will allow easy formatting (and reformatting) of the bibliographic index in OpenOffice.org Writer.
Main Features
Compatible with two database engines: MySQL and SQLite.
Hierarchical organization of the references with user defined keys.
Drag & drop to easily organize references.

Designed for multiuser:
You can share the database between an "unlimited" number of users.
Each user will have its own classification.
Powerful and easy to use search engine.
Live queries, that is searches that will update when the database change (this is simply a saved SQL query).

On-line PubMed access.

Import PubMed (Medline) and EndNote/Refer records.
Connection to OpenOffice.org. You can insert references in an open OpenOffice.org text document and format the bibliography directly in Bibus.
Thanks to Python and wxWidgets, Bibus should work on most modern platform (GNU/linux with gtk; Windows; MacOS; etc...). Version 0.8 has been tested on GNU/linux and Windows2000. Note for Windows 98 users.

Foreign language support through Unicode and gettext. As of version 1.2, Bibus is available in English, French, Portuguese, German, Spanish and Chinese.
For more info see http://bibus-biblio.sourceforge.net/

===OpenOffice===

The [http://www.openoffice.org OpenOffice] word-processor 'Writer' includes basic bibliographic support. OpenOffice has a [http://bibliographic.openoffice.org bibliographic project] whose goal is to improve the bibliographic facilities.

===rtfbtx===
[http://www.dmst.aueb.gr/dds/sw/ports/rtfbtx/ rtfbtx] is a hacked collection of BibTeX styles for doing bibliographies with MS Word & BibTeX. It produces the bibliography in RTF format & uses bookmarks to link citations to it.

Christos tried using it with OpenOffice and it only works for the alpha style, since for the rest I'm supposed to link to the "paragraph number" of the bookmark and OO doesn't support such a thing.

===Zotero===

[http://www.zotero.org/ Zotero] [zoh-TAIR-oh] is a free, easy-to-use Firefox extension to help you collect, manage, and cite your research sources. It lives right where you do your work — in the web browser itself. Requires [http://en-us.www.mozilla.com/en-US/firefox/2.0/releasenotes/ Firefox version 2]. There is now a OpenOffice-Zotero [http://www.zotero.org/documentation/openoffice_integration extension/plug-in] to allow users to insert citations and Bibliographic tables into your documents.

===Bibwiki===

Bibwiki is a extension to MediaWiki to manage bibliographies. The bibliographies are stored in plain BibTeX files. In contrast to other programs, Bibwiki alters the bibliographic files directly. You don't need a seperate database.

Bibwiki adds a special page where you can add, import, edit and export bibliographic records. Together with Mediawiki it's very easy to organize your excerpts, memos, or annotations and link them to the bibliographic records.

Features:
* import from various sources: Ex Libris' Aleph, Amazon, ProQuest
* export list of references using BibTeX styles
* manage digital documents
* easy searching

Visit [http://www.plaschg.net/bibwiki Bibwiki's Homepage].

===Mendeley===
Mendeley Desktop is an bibliographic programm which has a working Openoffice 'Cite 'n Write' plugin working for the Windows variant. You will have to register at their site, which also enables you to see the cited works of other users of your particular branch and share your used citations with other interested users. It currently supports BibTex/LaTex, Endnote, RIS and PDF(for quick reference). You can also use it to check any citations on Google Scholar.

Visit [http://www.mendeley.com/ Mendeley's Homepage] for more information.

==LaTeX / BibTeX==

[http://www.latex-project.org/ LaTeX] is a high-quality typesetting system, with features designed for the production of technical and scientific documentation. LaTeX is (or was) the de facto standard for the communication and publication of scientific documents.

[http://www.bibtex.org BibTeX] is the bibliographic subsystem for LaTeX,it is a citation formating and a bibliographic database tool. BibTeX styles definition files are small programs written in an un-named programming language [[http://www.forth.org/ FORTH] like]. This make them almost impossible to utilise in other applications. On the other hand, its database format for bibliographical references is widely used and most other bibliographic applications can import and export that format. It looks like this -
<pre>
@INBOOK{chicago,
title = "The Chicago Manual of Style",
publisher = "University of Chicago Press"
edition = "Thirteenth",
year = 1982,
pages = "400--401",
key = "Chicago" }
@BOOK{texbook,
author = "Donald E. Knuth",
title= "The {{\TeX}book}",
publisher = "Addison-Wesley",
year = 1984 }
</pre>

===The Jurabib package===

Extended BibTeX citation support for the humanities and legal texts. [http://www.jurabib.org/ jurabib] is a package for the LaTeX typesetting system and supports citations used in the humanities and by German law students. This package enables automated citation with BIBTEX for legal studies and the humanities. In addition, the package provides commands for specifying editors in a commentary in a convenient way.

This package is no longer actively developed.

===The biblatex package===

Massively extended BibTeX citation support. [http://www.ctan.org/tex-archive/help/Catalogue/entries/biblatex.html biblatex] is a package for the LaTeX typesetting system and adds a lot of new fields which overcome most of BibTeX's traditional shortcomings (e.g. book authors, gender, original publication, titles of multipart publications etc.). Biblatex hands the complete control of the appearance of citations and bibliography over to LaTeX, the BibTeX program itself is only used for sorting. The result is much more control for the user in a properly documented language.

==Linux==

=== OpenOffice/KBibTex/LyX/oolatex ===

The current way to create a bibliography in OOo makes it too difficult to produce a nicely formatted bibliography (at least it's too difficult for me). After trying a lot of the other alternatives, I found a way that works for me using KBibTex to create a BibTex database, LyX to create a nicely formatted bibliography, and oolatex to produce an OpenOffice .odt version of the LyX bibliography. First, use KBibTex to create the database (with your choice of formatting sytle) and export a BibTex database. Then open LyX and add a BibTex database. You have to add citations in order for the bibliographic entries to appear in the References or Bibliography. Export this to a latex file (either pdflatex or plain). Then we need to compile the latex - this takes several passes to resolve all the references. If the latex file is named "newfile1.tex", then use the following steps:

<nowiki>
#Compiling Latex file with BibTex bibliography</nowiki>

<nowiki>#Takes several passes to resolve references</nowiki>

<nowiki>#Use LyX to create document, export to latex</nowiki>

''latex newfile1.tex''

''bibtex newfile1''

''latex newfile1.tex''

''latex newfile1.tex''

<nowiki># Now convert to .odt</nowiki>

''oolatex newfile1''

<nowiki># Open the .odt in OpenOffice</nowiki>

''openoffice.org-2.1 --writer newfile1.odt &
''

At this point you should have a nicely formatted bibliography that you can paste into your OpenOffice document. An OpenOffice bibliographic database has been created using a user-defined format (thanks to oolatex).

Alternatively, you can use latex2rtf to create an .rtf version of the bibliography and open this in OpenOffice. My experience, however, is that it is not as nicely formatted:

''latex2rtf newfile1''

But of course, you can output an .rtf directly from KBibTex.

I did try to get LyX to export the .odt directly and I could swear I had it working (adding a new file format and a new converter in the Tools | Preferences) but I couldn't repeat it. LyX came with a set up for creating the older .swx format file - but this didn't seem to work. But the manual method outlined above works consistently.

--[[User:Rabil|Rabil]] 19:35, 14 January 2007 (CET)

===Tellico===

The Tellico application is the first one I have come across that uses xslt to format Bibliographic reports / tables. This is interesting as this is the method that we have been proposing for OpenOffice Bibliographic application, but we have not had any examples until now. See http://www.periapsis.org/tellico/

''"Tellico is a KDE application for keeping track of your book collection, bibliographies, video collection, or music collection. Tellico allows you to enter your collection in a catalogue database, saving many different properties like title, author, etc. Two different views of your collection are shown. On the left, your entries are grouped together by any field you like, allowing you to see how many are in each group. On the right, the values of the fields are shown, allowing you to customize your view to show whichever fields are most important to you. On the bottom is the field editor, where you can enter the data."''

''The data is saved in XML format, which makes for easy parsing. Unless you modify the fields yourself, the data follows a simple and documented DTD. It will run on any platform which KDE supports, most commonly Linux. Tellico is licensed under the GNU General Public License, giving you the freedom to modify and distribute the source code."''

'''Capabilities'''

* Supports collections of books, bibliographic entries, videos, or music.
* Supports any number of user-defined fields, of eight different types: text, paragraph, list, checkbox, year, URL, and tables.
* Handles books with multiple authors, genres, keywords, etc.
* Automatically formats titles and names
* Supports collection searching and view filtering
* Sorts and groups collection by various properties
* Automatically validates ISBN
* Allows customizable output through XSLT
* Imports Bibtex, Bibtexml, and CSV
* Exports to Bibtex, Bibtexml, CSV, and HTML

===BibTeXML===

BibTeX as XML markup. Markup scheme; - A bibliography DTD and schema for XML that expresses the content model in BibTeX -- the bibliographic system for use with LaTeX, which is widely adopted by the scientific community. BibTeXML is shipped with tools to uptranslate native TeX-syntax BibTeX bibliographies to XML, and translating this into any markup scheme. Hence one is able to profit from both the existing BibTeX system and bibliographies as well as the presentation and transformation facilities offered by XML. Our goal is to maintain a strict BibTeX schema and develop (and collect!) conversion tools that will help you tag your bibliographic data in XML and save typing time, or export it to HTML, DocBook or native BibTeX syntax. http://bibtexml.sourceforge.net/

===BibML===

BibML is an XML markup language designed to contain bibliographic information, particularly as content exported in Bibtex and Refer notations. BibML also contains content types from DocBook's <bibliography>, and as such may be considered an integration of the three sources. The web page contains a useful 'BibML Element Comparison Table' comparing the attributes of BibML, Bibtex, docbook and refer. http://kmi.open.ac.uk/projects/ceryle/docs/NOTE-bibml.html

===BibX===

The intention of BibX -- begun by Taco Hoekwater to serve as the basis for his XML rewrite of the ConTeXt bib module -- is to be the XML equivalent to RIS and BibTeX, but to significantly improve on them. http://tex.aanhet.net/bibx Download the current DTD.
ISDN Search
"A distributed search portal of common sources of ISBN numbers, with permanent caching of results. To provide a open-source free interface for ISBN retrieval using HTML, SQL or XML to be independent of any toolkits or software." http://sourceforge.net/projects/isbnsearch/

===YAZ===

Z39.50 is the protocol used to query databases and library catalogues for bibliographic information.
YAZ is a C / C++ programmer's toolkit supporting the development of Z39.50v3 / SRW clients and servers. Sample clients and servers are included with the distribution, and documentation can be browsed from this page. (Also available for MAC OS X).
NEW: The latest version of YAZ supports SRW/SRU (over HTTP). The YAZ server operates as both a simple HTTP 1.1 server and Z39.50 target (on the same port). The current version of YAZ includes support for the industry standard ZOOM API for Z39.50. This API vastly simplifies the process of writing new clients using YAZ, and it reduces your dependency on any single toolkit. ZOOM can also operate as a SRW client. Read more about ZOOM in YAZ here. The software library compiles in Windows and Linux. There is also a demonstration client program - IRTCL (requires YAZ and Tcl/Tk libraries be installed) that can perform the reference searches. It does everything but save or export the results ! However it is good model of how to use the toolkit. [http://bibliographic.openoffice.org/irclient.jpeg Screen pic]. [http://www.indexdata.dk/yaz/ www.indexdata.dk/yaz/]

===RefDB===

RefDB is a reference database and bibliography tool for SGML, XML, and LaTeX/BibTeX documents. It allows users to share databases over a network. It is lightweight and portable to basically all platforms with a decent C compiler. And it's released under the GNU General Public License.
The citestylex DTD from RefDB defines bibliographic formatting styles, and v2 will be updated to support BibX when it is done
RefDB is currently known to build and run out of the tarball on at least these platforms: Linux FreeBSD NetBSD Solaris (using gcc) OSX/Darwin Windows+Cygwin
RefDB appears to be the only available tool to create HTML, PostScript, PDF, DVI, MIF, or RTF output from DocBook or TEI sources with fully formatted citations and bibliographies according to publisher's specifications (check out some examples). Additional document types can be easily added. Project Home Page [http://refdb.sourceforge.net refdb.sourceforge.net].

===Sixpack===

Sixpack is a graphical and command-line bibliography database manager written in Perl/Tk. It interacts with the supplied package 'bp', (see below) which can import and export from a number of formats including bibtex, endnote, medline, procite, and many others. It can download references directly off the Web, and open articles using external viewers. It can also interface with Emacs/XEmacs and Lyx [LaTeX with a GUI interface] . It also has instructions on how to interact with openoffice / [[StarOffice]] using cvs files and database import functions [I have used this]. There are also some experimental filters to export sixpack data to the OpenOffice Bibliographic Database - using CSV format - see the Bibliographic Project Document and Files pages. Sadly it is not being well maintained. Home Page - [http://sourceforge.net/projects/sixpack sourceforge.net/projects/sixpack]

===bp===

bp is a Perl library that is designed to:
Let you quickly make tools to access bibliographies
Let you quickly make tools to access bibliographies
Let you access multiple bibliography formats transparently
Let you convert between formats
Let you convert between character sets
Developer - My first goal when designing the package was only the first -- I had written a number of tools that accessed my BibTeX bibliographies, and I saw that I was reusing a lot of code. So I decided to make a generic package to access BibTeX bibliographies. About a year later I decided that it would be even better if the package could read multiple formats, and convert between them. The result is bp. Parts of the package are still missing (namely documentation, automatic format recognition, and a good set of utilities), but everything needed for a working system exists. Home Page - http://www.ecst.csuchico.edu/~jacobsd/bib/bp/index.html

===gBib===

gBib is a user-friendly Gnome BibTeX database browser and editor. It provides facilities for merging BibTeX files, managing key conflicts, and adding bibliographic citations in LyX. Home Page - http://gbib.seul.org

===Pybliographer===

Pybliographer is a tool for managing bibliographic databases. The application is based written in Python and has a text-based and a GTK GUI interface It supports several bibliography formats and can be used for searching, editing, reformatting, etc.. Due to its nature, it can be extended to many uses (generating HTML pages according to bibliographic searches, etc). Pybliographer has a class library structure that could allow other applications to make use of it's facilities. It might be possible to provide a link from this program to insert citations into OpenOffice. There are only a few citation styles defined so far. Home Page -
http://www.pybliographer.org

The Pybliographer developers are considering major enhancements to the application and have produced some planing documents which has very good discussion of bibliographic and user client program issues. They are well worth a look at - http://www.pybliographer.org/development

===Kaspaliste===

Kaspaliste is a literature and knowledge database. It handles all kinds of books, articles, journals, web pages etc. But the database goes beyond simply storing bibliographical information. There is the possibility to create annotated links between pieces of information (like the content of a book chapter) and to group the links in categories. It is based on KDE and uses the Postgres relational database. It is a promising project but currently does not have import or export functions other than a Bibtex export. There are no links to other programs such as OpenOffice. Last release 2004-05-12. http://kaspaliste.sourceforge.net/

==Web Applications==

===Aigaion===
Aigaion is a free, web-based platform for managing annotated bibliographies. It allows the user(s) to order publications in a self-chosen topic structure and offers an intuitive user interface. Aigaion is built on the [[Bibliographic_Software_and_Standards_Information#BibTeX |BibTeX]] format and has excellent BibTeX import and export facilities.

Features
* Multi-user facilities
* Intuitive user interface
* Easy management of publications and topics
* Create public or private notes on publications
* Import of the BibTeX and [http://www.refman.com/support/risformat_intro.asp RIS] ([[Bibliographic_Software_and_Standards_Information#Endnote |Endnote]], [[Bibliographic_Software_and_Standards_Information#Reference Manager |Reference Manager]]) format
* Export of BibTeX and RIS (RIS is under development) format
[http://aigaion.sourceforge.net/ Aigaion homepage]

===BibORB===
BibORB is a tool to manage bibliographies recorded in BibTeX format using a simple Web browser.

[http://biborb.glymn.net/doku.php?id=features BibORB homepage]

===Memento===
Memento is next generation of web based bibliographic software that goes beyond simple searching, storing, and exporting articles. It is one stop solution for students, researchers, scholars where they can manage their bibliography, create and share reports and network with professionals.
Features:
* Clean, simple Internet Explorer and Firefox compatible interface
* Memento constantly fetches articles from all the famous online journals and conference websites to keep it database upto date.
* Import articles in multiple format such bibtex, endnote, RIS, etc.
* Export articles in bibtex or Microsoft Word 2007 Bibliographic XML
* Write personal notes, or upload PDF related to an article
* Write publicly viewable comments related to an article
* Create reports, attach articles to report, and share reports with other users
* Explore other users with similar interest
* Create watch list for articles, authors, keywords and receive new articles in RSS feed

[http://findnwrite.com/memento Memento homepage]

===BiblioWeb===

BiblioWeb is a web enabled bibliographic software. All the basic functions of bibliographic software are delivered through web browser. A Web user can be assigned "Read" or "Write" privileges. Users with "Read" accounts can search, browse, display, and export bibliographic records. Users with "Write" accounts can add, edit, delete, import, even format document through web browser. BiblioWeb is the ideal solution for a research group to share a common bibliographic database on the Web. It also supports a threaded discussion forum. http://www.biblioscape.com/bibliohost.htm

===User::Blibrestez55/Books/Scientific Bibliographic Project 2015 OpenOffice.org Wiki===
A bibliographic/software and standards informative scientific database supports collections of ESL books & reading materials,bibliographic cd's.audio,videos & translated languages of scientific books in English,German,French, Italian,Spanish,Turkish,Japanese & other translations.
http://wiki.services.openoffice.org/wiki/User:Blibrestez55/books/Scientific_Bibliographic_Project_2015

Insert->Indexes and Tables->Indexes and Tables->Tab=Indexes/tables;Type=Bibliography
Insert->Indexes and Tables->Indexes and Tables->Type=Bibliography;Tab=Entries

[[Category:Bibliographic]]

===refbase===
http://refbase.sourceforge.net/

Refbase is a web-based, platform-independent, multi-user interface for managing scientific literature & citations.
Main [http://refbase.sourceforge.net/features.html features]:

* a clean and standardized interface that attempts to be as web standards compliant as possible
* a multitude of search options, including quick, simple, advanced as well as powerful SQL search options
* various display options:
** list view: offers customizable and sortable columns
** details view: shows all fields of a particular record
** cite view: displays record entries in a citation style chosen by the user
** print view: eases printing or copying of records
* search within results functionality which provides an easy way of refining your search query
* user-specific fields for personal keywords, notes, etc
* save any search query together with the current display settings
* automatic email announcements for newly added records
* dynamic RSS feeds for recently added/edited records as well as for any custom user query
* [http://wiki.refbase.net/index.php/Importing_Records batch import] of records from various common bibliographic formats and online databases
* export records to MODS XML, Endnote, RIS or BibTeX (via bibutils)
* export to an OpenDocument spreadsheet for use with the current OO.o bibliographic manager
* link records to other records in the database (using static or dynamic links)
* extract literature cited within a text and build an appropriate reference list
* [http://wiki.refbase.net/index.php/Search/Retrieve_web_services Search & retrieve via URL (SRU)] web service
* COinS and unAPI

===RefWorks===

Was founded in 2001 by a team of developers (former Reference Manager developers) in the field of bibliographic database management. RefWorks is a '''web-based''', very flexible, research management, writing and collaboration tool. RefWorks allows users to create personal databases and use them for a variety of research activities. References are quickly and easily imported from text files or online databases. The databases can then be used to manage, store, and share the information. Users can automatically insert references from their database into their papers and generate formatted bibliographies and manuscripts in seconds. http://www.refworks.com/content/products/faqs.asp

Site licenses for organizations are available. Individual licenses are also available. RefWorks supports hundreds of online databases and output styles covering a broad range of subject areas. http://www.refworks.com/

===WIKINDX===

WIKINDX is a free bibliographic and quotations/notes management and article authoring system designed either for single use (on a variety of operating sytems) or multi-user collaborative use across the internet.

[http://wikindx.sourceforge.net/features.html Features]:

* 36 resource types.
* Multi-user mode - create and manage your own bibliographies drawn from the WIKINDX master bibliography and browse other users' bibliographies. (Must be enabled by the administrator.)
* Save your own preferences.
* Enter/edit bibliographic resources.
* Add unlimited file attachments to each resource. (Must be enabled by the administrator.)
* Catalogue resources by categories and keyword(s).
* Enter/edit a general note about the whole resource.
* Enter/edit quotes and paraphrases from those resources.
* Enter/edit thoughts or musings on various aspects of a resource (can be private or public).
* Add keywords to resource metadata such as quotes, paraphrases and musings.
* Use BBCode in all textarea input.
* Cross-reference other WIKINDX resources from within quotes, paraphrases, musings, notes and abstracts.
* Edit keywords, creators, publishers and journals.
* Comprehensive search across all the above with highlighting of search terms using either Quick Search or Power Search.
* Reorder bibliographic lists by first creator, title, resource type, publisher, year of publication timestamp, popularity index or maturity index.
* Select resources by category, keywords, creator, publisher etc.
* Browse all creators, publishers, collections, categories and keywords with font colour and size indicating frequency of occurrence (tag clouds).
* Unlimited primary creators, editors, translators and revisers, composers, agents, performers etc.
* Export bibliographic lists (optionally annotated) with a range of formatting options to RTF (Rich Text Format) files for easy insert into word processors.
* Export bibliographic lists to RIS for import to Endnote, Reference Manager, ProCite etc.
* Export an Endnote tabbed textfile.
* Export an Endnote XML file.
* Export bibliographic lists to BibTeX format.
* Import Endnote XML and bibTeX files.
* Cut 'n' Paste BibTeX entries to the database (amount limited by the administrator).
* View and export in seven bibliographic styles: Chicago, MLA, APA and Harvard, Turabian, British Medical Journal and IEEE. Administrators can copy, edit and create bibliographic styles through the web browser interface.
* Write an article entirely within WIKINDX importing quotes etc. and chose the citation formatting prior to exporting the article to RTF (can be opened in external word processors including OpenOffice).
* Run WIKINDX in core English or other languages (depending on administrator-installed language plug-ins).
* User-defined paging of long bibliographic lists.
* View all quotes, paraphrases and musings or a single random one.
* One-click return to last bibliographic list or single view.
* Store up to 10 bookmarks for quick return to single views.
* Select a visual style.
* WIKINDX has an architecture which enables either in-line or menu plug-ins to be inserted. Write your own or download plug-ins from the sourceforge site.
http://wikindx.sourceforge.net/

===literaturedb===
http://www.literaturedb.com

literaturedb is a bibliographic management software that can help you organize your literature and bibliographic references for scientific documents. It runs as a PHP web site and provides a collaborative space for storing and sharing documents and references.

Main [http://www.literaturedb.com features]:

* Simplicity: You can find all options on just four pages.
* Bibtex: It uses Bibtex entry types and fields so you can reuse references.
* Full text: It stores full text files (pdf, doc, etc.) for quick access.
* Exports: Export to Word, Bibtex, Endnote, MODS and RIS.
* Collaboration: You can share documents in your team and with friends.
* Tagging: You can tag every document with keywords.
* Search function: The search function scans all data entry fields.
* LDAP support: You can reuse the user management of your organization.
* FLOSS: It is free and open source (GPL).

===Contents-Linking===

http://www.multisuchsystem.de/contents.html

Contents-Linking as part of the Multisuchsystem E-Connect [http://www.multisuchsystem.de/]by Hans Hehl is a free webbed-based tool of managing and searching bibliographic records. It is also a linking system, which aims to go most directly to the full text of an article.
It is built only on simple HTML and Javascipt, but able to import at once hundreds of bibliographic records from any of the databases, so a database of own interest can rapidly be created.
Contents-Linking is connected with a knowledge base, which consists of ca. 50000 journal titles supplemented by subject terms and informations about library holdings.

'''Features'''
*Searching articles by terms or strings
*Searching articles by subject terms, alphabetically or by subjects
*Browsing ca. 40000 records
*Displayed records are linked with the full-linked record
*Browsing ca 70000 journal titles of Contents-database
*Displayed journal titles are linked with full-linked records corresponding to these
*Full-linked records are linked with EZB, ZDB, Google Scholar, Google and library holdings
*Contents-Linking may be installed for any library participating in the EZB
*Importing new records from the following databases: JADE Database, Current Contents, British Library Direct, PubMed,IngentaConnect, OVIDSearch, RefDoc, Google Scholar
*Creating a new import filter for another database

http://www.multisuchsystem.de/contents.html

[[Category:Bibliographic|Standards]]
[[Category: Marketing]]
[[Category:Screenshot]]
[[Category:Art]]
[[Category:Documentation]]

Bibliographic/Software and Standards Information

2012-10-25T17:43:25Z

Blibrestez55: (checkpoint save)

'''This is a wiki page. Please feel free to add relevant information or to make corrections to it. It is only useful if it is correct and up to date. Comments or suggestions can be put on the Discussion page (from the tab above)'''

==Open Standards Information==

Check [http://wwwsearch.sourceforge.net/bib/openbib.html Open Standards] for info on software for bibliographies and cataloging. It provides a quick overview of the landscape of open-source bibliographic software; both where it has been, but more importantly, where it may yet go. It may be better than this page.

A good source on open standards in regards to XML, is [http://xml.coverpages.org xml.coverpages.org] and of course [http://www.w3.org www.w3.org] the home of the internet.

===OASIS Open Document Format for Office Applications (OpenDocument) TC===

The [http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office OASIS Open Document Format for Office Applications (OpenDocument) TC] is Developing an XML-based file format specification for office applications.
Its [http://wiki.oasis-open.org/office/Bibliographies_and_Citations?%20%0Aaction=show OASIS OpenDocument Technical Sub-committee on Metadata] is looking at standards to support Search, [http://wiki.oasis-open.org/office/Bibliographies_and_Citations Bliographies and Citations]and Workflow Management.

===CiteProc===

The Openoffice Bibliographic project is proposing to use bibliographic citation and reference list generation using a new process called [http://bibliographic.openoffice.org/citeproc/index.html CiteProc]. CiteProc uses an XML citation style language (CSL) to provide, for the first time, the opportunity for the creation and distribution of open bibliographic style definitions that are not specific to a particular word-processor or bibliographic package. Also see [http://www.silmaril.ie/bibliox/biblioxdoc.html BiblioX] for technical discusion of this approach. We now have working examples.

===Citation microformat efforts===

This [http://microformats.org/wiki/citation wiki page] outlines the overall effort to develop a citation microformat. We are documenting current examples of cites/citations on the web today, their implicit/explicit schemas, and current cite/citation formats, with the intent of deriving a cite microformat from that research.

===Bibliophile===

[http://bibliophile.sourceforge.net/ Bibliophile] is an initiative to align the development of bibliographic databases for the web. It aims to promote standards, discussion among users on necessary features and a variety of specific solutions for different fields of research.

===MODS - Metadata Object Description Schema===

The Library of Congress' Network Development and MARC Standards Office, with interested experts, has developed a schema for a bibliographic element set that may be used for a variety of purposes, and particularly for library applications. As an XML schema, the [http://www.loc.gov/standards/mods/ "Metadata Object Description Schema"] (MODS) is intended to be able to carry selected data from existing MARC 21 records as well as to enable the creation of original resource description records. It includes a subset of MARC fields and uses language-based tags rather than numeric ones, in some cases regrouping elements from the MARC 21 bibliographic format. MODS is expressed using the XML schema language of the World Wide Web Consortium.

===Significance of Z39.50 and SRU/W to the OpenOffice Bibliographic Project===

Z39.50 will be the basis of the OOo Bibliographic internet searching facility. There are several opensource software implementation of this protocol. One example is YAZ, the other is SRW - see below.

Z39.50 is an international standard for communication between computer systems primarily, library and information related systems. Z39.50 is becoming increasingly important to the future development and deployment of inter-linked library systems.
[http://www.loc.gov/z3950/agency/zing/zing-home.html Z39.50 and ZING - Z39.50]

===SRU/W - Search/ Retrieve for the Web===

The difference between [http://www.loc.gov/standards/sru/ SRU] and [http://www.loc.gov/standards/sru/srw/ SRW] is that SRU uses HTTP as the transport mechanism. This means that the query itself is transmitted as an URL and that XML is returned as if it were a web page (note: POST, an alternative for using the HTPP transport mechanism, is not allowed in SRU). SRW is SOAP based, meaning that both the query and the result are XML streams. The advantage of this is that a variety of transport mechanisms can be used, including for instance e-mail.

Note: this description pertains to version 1.0 of SRW. Version 1.1 will be released soon. See: Draft SRW Version 1.1
SRW is the "Search/Retrieve Web Service" protocol, which aims to integrate access to various networked resources, and to promote interoperability between distributed databases, by providing a common utilization framework. SRW is a web-service-based protocol whose underpinnings are formed by bringing together more than 20 years experience from the collective implementers of the Z39.50 Information Retrieval protocol with recent developments in the web technologies arena.

SRW features both SOAP and URL-based access mechanisms to provide for a wide variety of possible clients ranging from Microsoft's .Net initiative to simple Javascript and XSLT transformations. It leverages the CQL query language which provides a powerful yet intuitive means to formulate searches. The protocol mandates the use of open and industry-supported standards XML and XML Schema, and where appropriate, XPath and SOAP. SRW has been developed by an international team, minimizing cross-language pitfalls and other potential internationalization problems.

The SRW Initiative, building on Z39.50 along with web technologies, recognizes the importance of Z39.50 (as currently defined and deployed) for business communication, and focuses on getting information to the user. SRW provides semantics for searching databases containing metadata and objects, both text and non-text. Building on Z39.50 semantics enables the creation of gateways to existing Z39.50 systems while reducing the barriers to new information providers, to make their resources available via a standard search and retrieve service.

SRW defines a web service combining several Z39.50 features, most notably, the Search, Present, and Sort Services. Additional features/services may be added later or defined later as new web services. Also see [http://srw.cheshire3.org srw.cheshire3.org]

===CQL - Common Query Language===

[http://www.loc.gov/standards/sru/cql/ CQL] is the query language for SRW and SRU, and may be used by other protocols as well. CQL is designed to be human readable and writable, while maintaining the expressiveness of more complex languages. XCQL, An XML form of CQL, is also available for use with SRW.

===Zoom===
The ZOOM initiative presents an abstract object-oriented API to a subset of the services specified by the Z39.50 standard, also known as the international standard ISO 23950. If you are trying to build any kind of Z39.50 client or client-based service, ZOOM is an excellent place to start. he API is:
Abstract because we don't want to limit its use to a single implementation language.
Object-oriented because the services lend themselves naturally to this widespread idiom.
For a subset of the full Z39.50 services because at this stage simplicity is more important than completeness.
The ZOOM specifications, bindings for several languages, and many implementations, are available for free browsing and download.
ZOOM is a key part of the wider ZING initiative (Z39.50 International: Next Generation). ZING aims to explore a variety of means for broadening the appeal of Information Retrieval tools, techniques and concepts beyond the traditional IR niche markets. [http://zoom.z3950.org/ zoom.z3950.org/]
ez3950 - Simple Implementation of Z39.50 over SOAP using XER
XER provides a mechanism to allow us to provide Z39.50 support over an alternative "internet" protocol without any additional amendments to the current ASN.1 standard. This document outlines an implementors agreement of how to implement XER over SOAP. (SOAP is Simple Object Access Protocol)

===ZeeRex - Z39.50 Explain, Explained and Re-engineered in XML===

[http://explain.z3950.org/ ZeeRex] (rhymes with T. rex) is "Z39.50 Explain, Explained and Re-Engineered in XML". It is an XML schema used to describe the configuration and capabilities of Z39.50 and SRW servers. (Note 'Explain' is a function in Z39.50 by which a server identifies the services it provides.) ZeeRex records are XML documents using The ZeeRex DTD, which is maintained by Rob Sanderson, and is available as an SGML DTD, and XML DTD and an XML Schema.

==Other Links to Bibliographic Information==

Oxford University. [http://users.ox.ac.uk/~ctitext2/service/workshop/bib-overview.html Overview of Personal Bibliographic Software]

[http://www.ilrt.bris.ac.uk/publications/researchreport/rr1032/report_html Review of Personal Bibliographic Systems] from The Institute for Learning and Research Technology, based at the University of Bristol.

[http://www.lib.gla.ac.uk/researchskills/bibsoftware.shtml 'Managing Your References Using Bibliographic Software Packages'] by GLASGOW UNIVERSITY LIBRARY

[http://en.wikipedia.org/wiki/Comparison_of_reference_management_software Comparison of reference management software] on Wikipedia

A comprehensive study of bibliographic data requirements is [http://www.ifla.org/VII/s13/frbr/frbr.htm 'Functional Requirements for Bibliographic Records'] (144 pages, 620Kbytes) by the International Federation of Library Associations and Institutions in PDF format. And a related report [http://www.miskatonic.org/library/frbr.html 'FRBR and Fundamental Cataloguing Rules'].
Bibliographic Utilities information from [http://www.canadiancontent.net/dir/Top/Reference/Libraries/Library_and_Information_Science/Technical_Services/Cataloguing/Bibliographic_Utilities/ Canadian Content - Bibliographic Utilities] which includes descriptions of tools to find, create, edit, and manipulate bibliographic collections.

==Java==

===AlleMeineBuecher.Net===

This free software provides an easy to use interface. It autmatically looks up book details and book covers by given ISBN numbers. It can do exports. It's compatible with standard barcode-scanners. [http://allemeinebuecher.net AlleMeineBuecher.NET] It's ideal solution for private book collections. The UI is available in English and German.

===B3===

B3 is a free bibliography manager that provides a graphic interface to Bibtex. However, B3 uses its own format: an XML extension of the Bibtex format. B3 has GUI reading and writing XML files and exporting them as Bibtex files. It also includes a Journal Dictionary, a dictionary linking Journal names and their abbreviations. It allows copy/paste the bibliography into a word processor, in order to save boring and upsetting tasks. B3 stands for Bibliography Base for Biologists, since the author is a biologist and only knows about biology journals bibliography. Of course, many tools of B3 may be useful for other disciplines. B3 includes many more features, and tries to provide a free alternative to currently used bibliography managers like EndNotes(C).B3 uses powerful and widely used standard new web languages to store, format and display bibliography data, namely:
XML (eXtensible Markup Language) to manage databases,
XSL (eXtensible Stylesheets Language) to process them,
XHTML (eXtensible Hyper Text Markup Language) to display them in a web browser,
As a result, B3 is a very portable application (it can run under Windows, Mac and Unix-like systems). It tends to be compatible with OpenOffice because it can export data to a bibliography database. It can easily be customized: Everyone who knows XSL can write a stylesheet and implement its own bibliography format. It supports Pubmed internet searches. For more info see http://b3bib.sourceforge.net/

===JabRef===

JabRef is a graphical frontend to manage BibTeX databases, the standard LaTeX bibliography reference format. JabRef is built to be platform independent (requires Java >= 1.5, or 1.4.2 for older versions). It merges and extends the functionalities of BibKeeper (Morten O. Alver) and JBibtexManager (Nizar Batada). Features. Detailed editing of bibtex entries. Search a pattern in the whole bibliography. You can group entries by keywords or any other fields. Supports import of various formats - BibTex, Endnote (text), ISI Web of Science, Medline/Pubmed (xml), Scifinder format, OVID, INSPEC, Biblioscape, JStor and RIS. Supports different export formats - HTML, Docbook, BibTeXML. You can add your own fields to any BibTeX entry type. Launch external applications: PDF/PS viewers, web browser, insert citations into LyX, Kile and WinEdt. Now you can insert citations and bibliographies into OpenOffice documents. Automatic Key generation. http://jabref.sourceforge.net/index.php

===Synapsen===

Synapsen is a hypertextual card catalog that enables the management of bibliographies. However, in contrast to normal literature management software, synapsen offers a very distinct advantage: with catchwords entered by the user, the program connects individual cards automatically and creates not only a network of cards whose relation to each other might have been forgotten, but also creates completely unexpected connections and relations between individual entries. synapsen is therefore not only for electronic literature management, but also a helping hand when writing scientific texts, which participates in communication with the author in order to augment lines of argumentation and the generation of ideas.

synapsen is written in JAVA, runs on all operating systems, and supports standards like BiBTeX, RTF, LaTeX, SQL. It can be found under http://www.verzetteln.de/synapsen/synapsen_e.html

Since version 2.5 Synapsen offers a direct connection to Open Office 2.2 via the UNO interface. This allows you to insert bibliographical data of Synapsen's cards directly as footnotes in OpenOffice Writer.

===DAFFODIL===

Distributed Agents for User-Friendly Access of Digital Libraries

(Text from the [http://www.is.informatik.uni-duisburg.de/projects/daffodil/index.html.en project website]:) Despite the fact that many Digital Libraries (DLs) are available on the Internet, users cannot effectively use them because of inadequate functionality, deficient visualisation and insufficient integration of different DLs. In the framework of this project we develop a user-oriented access system for DLs which overcomes these drawbacks. Based on experiences from the librarian area, higher functions to assist proved search strategies will be implemented. Different DLs will be tightly integrated, so that system-wide search and navigation is possible. The system will be adaptive towards different user wishes, regarding preferences concerning content and system involvement.

The first two year project phase is concluded and the outcome is a running prototyp which covers all goals.
Second period (2002-2004)

The key concept of strategic support when using digital libraries will be a major topic in the next years, but we will extend it to all levels of the information search process and the different kinds to gather information. To organise the found material, there annotations and interpretations we will develop a personal digital library. It provides simultaneously a user- and taskoriented context, to support searching and browsing better then up till now.

As additional method for the information gathering we will integrate the path model, collaborative filtering as well as the workflow model into Daffodil. The last two methods will allow for cooperation by using digital libraries. A special role is given to the librarian in the cooperative environment.

The graphical user interface design supports different interaction level -- exspecially circumstantial work tasks will be supported by software-information agents, but with regards to the user autonomy. Likewise the iterative process during the retrieval will be optimised.

Daffodil is a projects in the strategic research initiative V3D2 (Distributed Processing and Delivery of Digital Documents) of the German Research Foundation (DFG). http://www.is.informatik.uni-duisburg.de/projects/daffodil/index.html.en http://www.daffodil.de/

You can start DAFFODIL directly from the web using Java Web Start: http://www.is.informatik.uni-duisburg.de/projects/daffodil/pdaffodil.jnlp (Login/Password: visitor/visitor)

===TextCite===

TextCite is a program for organizing and commenting textual citations from texts (books, articles, or other published works) for use in producing scientific or academic publications. You can organize by publication, author, category, or outline. It works with bibliographic management programs like Citation, Endnote, RefWorks, and BibTeX (i.e. via programs such as JabRef and BibDesk), providing important text/citation management capabilities that these programs lack, while still allowing for rapid footnote and bibliography generation by means of your favorite bibliography manager. It also exports to PDF and Word (RTF).

TextCite is open source software, and is available free of charge from the [http://textcite.sourceforge.net/ TextCite homepage]. It requires a minimum of Java 1.5, and is available in packages for Windows and Mac OS, as well as in an executable .jar format for running on Unix/Linux.

==Perl, Python==

===Pbib===

PBib is a small tool for browsing and processing bibliographic databases which is written in Perl (that's where the "P" in the name comes from :-). PBib works similar to the classical BibTeX, but can be extended for arbitrary bibliography databases (including BibTeX files and the OpenOffice.org database format), arbitrary bibliography styles (e.g. ACM, IEEE), and arbitrary document formats (including RTF and OpenOffice text documents). http://www.ipsi.fraunhofer.de/~tandler/PBib/

'''DESCRIPTION'''

I wrote PBib to have something like BibTex for MS Word [ Perl is avaiable in Linux as well] that can use a various sources for bibliographic references, not just BibTex files, but also database systems. Especially, I wanted to use the [[StarOffice]] bibliographic database.
Now, PBib can be extended in a couple of dimensions:
bibliographic styles such as ACM style or IEEE style.
document format such as Plain text, (La)TeX, Word, RTF, OpenOffice
bibliographic database format such as bibtex, refer, tib, but also database systems with different mappings to database fields.

===RISImport.py===
A python script that reads RIS format files containing one or more references and inserts them into the default OpenOffice.orgBibliography/'biblio' database. The setup of this script is relatively straight-forward, and the current RIS tag to 'bilbio' column mapping has worked great for me for the few engineering electronic portals that I use (e.g., IEEEXplore, Inspec, MathSciNet).

Additionally, as I will briefly explain here, the mapping (in some cases relatively advanced) can be easily customized to fit your need (i.e., different reference sources and their slightly different interpretations of the RIS format). It can be found in our Documents and Files Page.

Michael Sowka, E-mail: msowka@rogers.com www.sowka.com

==MS Windows==

===Bibliographix===

Bibliographix is designed for people who are writing their doctoral thesis, frequently writing scientific texts, or reading a lot of literature. The free Basic version offers more than any other free reference manager. It should be more than enough for undergraduates. Try it out as long as you like. The Pro-Version is starting at USD 40 and offers everything an academic might need.

What is special about Bibliographix?
High-end reference management for a low-end price. A unique combination of reference management and idea outlining. Two items that belong together. Save yourself the typing: Import data from online libraries. You'll never want to miss it: one-click tables of references. Bibliographix can insert intext citations into OpenOffice. http://www.bibliographix.com/

===Biblioscape===

Biblioscape product family is designed to help researchers collecting and managing bibliographic data, notes, as well as generating citations and bibliography for publications.
Research Information Manager. Biblioscape is an information manager for researchers, scholarly writers, students, and librarians. People use it to organize literature references, research notes, automatically generate citations and bibliographies automatically, search and capture bibliographic data on the Internet, and post bibliographic databases live on the web. The flood of bibliographic resources on the Internet requires new solutions for bibliographic information management. Biblioscape offers such a solution -- whether you work alone, or as part of a group, or even in a large organization. For a comprehensive feature list see http://www.biblioscape.com/features.htm. There is a free 'lite' version called Biblioscape Express. There is an associated [[Bibliographic_Software_and_Standards_Information#BiblioWeb| BiblioWeb service.]] http://www.biblioscape.com .

===Citavi===

Citavi (Lat., I cited) is a user-friendly bibliographic application that works with OpenOffice, Microsoft Office and other Windows word-processing software. Citavi enables you to organize bibliographic material in a very practical way. The program provides access to up to 4000 bibliographic databases and library catalogs. You can process literary content, collect citations, organize draft texts and schedule tasks.

Citavi can be integrated with OpenOffice Writer: references and citations can be inserted directly via the publication assistant. After finishing your work, Citavi scans the ODT file and inserts a full formatted bibliography at the end of your document. It is also very easy to export the references collected to OpenOffice Calc. A free version of Citavi is available and an English version of Citavi will be released Sept. 2010.
Citavi Home Page http://www.citavi.com

===Citeit!===

This product is a very good example of maintaining bibliographic data linked to textual information.

"CiteIt! is revolutionary software that automates the tedious process of creating accurate and properly formatted legal citation. CiteIt! enables users to instantly import legal citations from online legal databases, such as Westlaw? and Lexis-Nexis?, with a click of a button. With CiteIt!, you never again have to type a legal citation into a document, spend time worrying about proper Bluebook or ALWD formatting, or write a citation down as you search on an online legal database."

General CITEIT! features:
Imports citations from on-line legal databases or any web page with a click of a button.
Automatically places all citations imported or entered in proper citation form.
Provides all of the possible cite forms for each citation for quick insertion into any document.

Professional and Advanced Versions of CiteIt! can create a table of authorities in seconds. Powerful notes and keyword features allows you to easily store, organize and search your research information. CiteIt! integrates seamlessly with Microsoft Word or Corel WordPerfect, so accurate citation is only a few mouse clicks away. Intuitive user interface means that anyone can start using CiteIt! in minutes. Two versions of CiteIt! are available - one which supports the 17th Edition of The Bluebook and another which supports the ALWD Citation Manual.
http://www.citeit.com/product/default.htm

===CiteSmart===

[http://www.miresoft.net/citesmart CiteSmart] is a fairly new yet very powerful software application specifically designed for researchers in Biology and medical disciplines in mind, but can also be used with a variety of documents (law, business, patents ...). CiteSmart implements new features called [http://www.miresoft.net/citeclick CiteClick], [http://www.miresoft.net/citeclick CiteClick] and [http://www.miresoft.net/citeclick RefDrag] (patent pending). Users relying on [http://www.ncbi.nlm.nih.gov/sites/entrez?db=PubMed Medline / PubMed] for their every day work can store and cite references into a word document (and simultaneously in a local library) in a single click. CiteSmart is intended for reaserchers who work with Medline / PubMed. CiteSmart can be customized to work with any bibliographic database and potentially any working environment. Its single click philosophy makes CiteSmart invisible to users who don't need to interact with it for storing and citing references. CiteSmart also offers hundreds of styles and a style editor/ to create styles in minutes. Finally among other cool features, it is compatible with EndNote and Reference Manager, it also can rebuild libraries from word documents containing references, it automatically handles 'in press references' and update them as they appear in print. Many other feature are being added regularly. MireSoft's website: [http://www.miresoft.net MireSoft]. View CiteSmart in action [http://www.miresoft.net/citesmart/videos/ CiteSmart Screencasts].

===Endnote===

A very popular and widely used Bibliographic package. Recommended by many Universities.
Platform: Windows & Mac
Description: Integrates three key bibliographical tasks within the one package: the searching of remote bibliographical databases on the Internet; the organisation of references in a database, and the creation of bibliographies. EndNote can be fully integrated with Word and other Windows word-processing software. Documents can be scanned and shorthand citations expanded and complete bibliographies created. EndNote libraries created on different platforms are compatible with each other. Home Page http://www.endnote.com/. Note that EndNote, ProCite, and Reference Manager are all owned by the same company, [http://www.thomsonresearchsoft.com/ Thomson ResearchSoft]. http://thomsonisiresearchsoft.com/compare/ is a useful comparison of these products from the vendor's perspective.

===Ibidem===

Manage your bibliographic material with consummate ease using Ibidem. Store bibliographic information in the simple database format, and Ibidem will generate your bibliographic references for you. The program will automatically format footnotes, endnotes, parenthetical short forms, and reference-number in-text citations, along with end-of-paper reference lists and bibliographies, according to hundreds of academic styles. Subsequent references are automatically abbreviated using shortened titles, ibid. or op. cit., as appropriate. You can change styles, and watch footnotes or endnotes appear or disappear as all citations in a document are automatically updated to the new format. Ibidem's seamlessly integrated, state-of-the-art control of bibliographic data will save you countless hours of drudgery, and your personal bibliographic databases will always be at your fingertips.
- instant access from within the word processor - notecard-like forms for easy entry of bibliographic information - drop-down lists for fast, consistent data entry - various viewing options, including short-list table view - fast and easy searching, sorting, and subset management - over 200 academic bibliographic styles included - works can be cited in open documents with a simple mouse click - color coding identifies Ibidem-generated citations in open documents - option to automatically exclude author or year from a citation - automatically shortens subsequent references to a cited work - dynamically-updated preview box - extensive search operators and features - subsets dynamically updated as records are added to database - numerous customizable options. Add-on module Archiva/ArchivaPro supports capture of bibliographic data from web sites with automatic conversion to Ibidem format.
This product has the best example of integrated bibliographic and style support that I have seen - a good model for OpenOffice to emulate.
A demo version is available. It is limited to 30 days use and no printing is possible - although you could export any work done on it.
http://www.notabene.com/

Some screen shots of Ibidem also http://www.notabene.com/brochures/ibidem.html

===Inflight Referencer===

Inflight Referencer, is a relatively new commercial bibliography application designed to work with all Windows word processors including Open Office. It integrates three important bibliographical tasks within the one product; organizing references into a database for future retrieval, creation of bibliography lists and insertion of reference citations into document text.

Specializing in APA and Harvard styles as well as customizable formats to meet various other citation and referencing styles, Inflight Referencer automates the process of creating reference lists. There is support for approximately 50 different media types including print and online resources. This bibliography product was originally designed in unison with university graduates, to produce a product that was inevitably simple to use and focused on achieving the goals of academics efficiently.

Inflight Referencer Home Page http://www.inflighttm.com/ref/

===LiteRat===

LiteRat is a free (as in free beer) application that is based on Microsoft Access 2.0. The programme can be used from Windows 3.1 through to Windows XP. The user interface concept comes from the flash card system. LiteRat can handle various kinds of bibliographic entries, quotes, and makes it also possible that several people can work on one database. A quick work flow can be achieved by this program, although it cannot connect to online databases due to its age.

LiteRat saves its data in Access 2.0 files which can be used through ODBC interfaces with other database applications. It's possible to export the bibliographic entries into a proprietary tagged text file, but there are macros for Mirosoft Word and OpenOffice.org shipped with the program that convert these tags into styles.

LiteRat's successor is Citavi.

LiteRat's website: http://www.literat.net/

===Nota Bene===

Nota Bene: a word processor for scholars ... a bibliographic manager for those who are tired of typing/formatting their own citations and bibliographies ... a personal search engine for those who want to find anything they've ever written in seconds ... a database manager for those who have things to keep track of ... a Hebrew, Greek, Cyrillic, IPA word processor for those who want more than just fonts ... a set of tools for scholars who want to focus on their writing and research ... a work of art for scholars who appreciate the finer things in life ... a community of scholars.
[Nota Bene's bibliographic facility is called 'Ibidem']
http://www.notabene.com

===ProCite===

ProCite is a Windows and Mac Bibliographic application similar in function to Endnotes and Reference Manager. The program can still be bought but no new software version have been made since 1999. [http://www.procite.com www.procite.com]

===Reference Manager===
Reference Manager is a comprehensive Bibliographic package with Bibliographic database, internet searching, and citation and bibliographic table formating. It is widely used at many professional organizations and universities.
The program has many important features for heavy users who do a lot of literature searching and keep many references in their databases. Version 11 now includes a web publisher which allows you to publish your databases and share your references with colleagues.
There also is a Network version of the program.

It has a downloadable collection of over 1200 citation styles. It saves bibliographic date in RIS format which is now a common data exchange format. [http://www.refman.com www.refman.com]

===Scholars Aid===

A commercial application that works with OpenOffice (on MS Windows). Note that there is also a free 'Lite' version. "Scholar's Aid keeps bibliographical data and notes together, for the very good reason that scholars always need to keep their notes linked to the sources from which those notes were made. Indeed, in academic writing, scholars constantly support their argument by reference to the sources on which they have worked. Thus, in directly quoting from one of these sources, or in making reference to another's ideas, rigorous academic scholarship demands accurate and detailed citation of those original sources.

Scholar's Aid automates this process in a manner that is entirely without precedent. Provided the original notes were written in the Notes module of Scholar's Aid, by selecting text and clicking the transfer button, the program transfers the selected text into the word-processed document and, at exactly the same time, inserts an appropriate citation into the document in a form (footnote, short footnote, endnote, short endnote and parenthetical reference) determined by the user. The program even includes the correct page number in the citation that it creates within the word-processed document. Scholar's Aid surely is the Reference Processor?". http://www.scholarsaid.com/

==Windows, Linux, other==

===Bibutils===

The bibutils program set interconverts between various bibliography formats using a common XML intermediate. For example, one can convert RIS-format files to Bibtex by doing two transformations: RIS->MODS->Bibtex. By using a common intermediate for N formats, only 2N programs are required and not N²-N. These programs operate on the command line and are styled after standard UNIX-like filters:

* bib2xml - convert bibtex to XML intermediate 
* copac2xml - convert COPAC format references to XML intermediate 
* end2xml - convert endnote to XML intermediate 
* isi2xml - convert ISI web of science to XML intermediate 
* med2xml - convert Pubmed XML references to XML intermediate 
* modsclean - a MODS to MODS converter for testing puposes mostly 
* ris2xml - convert RIS format to XML intermediate 
* xml2bib - convert XML intermediate into bibtex 
* xml2ris - convert XML intermediate into RIS format 
[http://www.scripps.edu/~cdputnam/software/bibutils/bibutils.html www.scripps.edu/~cdputnam/software/bibutils/bibutils.html]

===Bibus===

Bibus is a bibliographic database. It has been designed with OpenOffice.org in mind. The "ultimate" goal is to have an opensource bibliographic software that will allow easy formatting (and reformatting) of the bibliographic index in OpenOffice.org Writer.
Main Features
Compatible with two database engines: MySQL and SQLite.
Hierarchical organization of the references with user defined keys.
Drag & drop to easily organize references.

Designed for multiuser:
You can share the database between an "unlimited" number of users.
Each user will have its own classification.
Powerful and easy to use search engine.
Live queries, that is searches that will update when the database change (this is simply a saved SQL query).

On-line PubMed access.

Import PubMed (Medline) and EndNote/Refer records.
Connection to OpenOffice.org. You can insert references in an open OpenOffice.org text document and format the bibliography directly in Bibus.
Thanks to Python and wxWidgets, Bibus should work on most modern platform (GNU/linux with gtk; Windows; MacOS; etc...). Version 0.8 has been tested on GNU/linux and Windows2000. Note for Windows 98 users.

Foreign language support through Unicode and gettext. As of version 1.2, Bibus is available in English, French, Portuguese, German, Spanish and Chinese.
For more info see http://bibus-biblio.sourceforge.net/

===OpenOffice===

The [http://www.openoffice.org OpenOffice] word-processor 'Writer' includes basic bibliographic support. OpenOffice has a [http://bibliographic.openoffice.org bibliographic project] whose goal is to improve the bibliographic facilities.

===rtfbtx===
[http://www.dmst.aueb.gr/dds/sw/ports/rtfbtx/ rtfbtx] is a hacked collection of BibTeX styles for doing bibliographies with MS Word & BibTeX. It produces the bibliography in RTF format & uses bookmarks to link citations to it.

Christos tried using it with OpenOffice and it only works for the alpha style, since for the rest I'm supposed to link to the "paragraph number" of the bookmark and OO doesn't support such a thing.

===Zotero===

[http://www.zotero.org/ Zotero] [zoh-TAIR-oh] is a free, easy-to-use Firefox extension to help you collect, manage, and cite your research sources. It lives right where you do your work — in the web browser itself. Requires [http://en-us.www.mozilla.com/en-US/firefox/2.0/releasenotes/ Firefox version 2]. There is now a OpenOffice-Zotero [http://www.zotero.org/documentation/openoffice_integration extension/plug-in] to allow users to insert citations and Bibliographic tables into your documents.

===Bibwiki===

Bibwiki is a extension to MediaWiki to manage bibliographies. The bibliographies are stored in plain BibTeX files. In contrast to other programs, Bibwiki alters the bibliographic files directly. You don't need a seperate database.

Bibwiki adds a special page where you can add, import, edit and export bibliographic records. Together with Mediawiki it's very easy to organize your excerpts, memos, or annotations and link them to the bibliographic records.

Features:
* import from various sources: Ex Libris' Aleph, Amazon, ProQuest
* export list of references using BibTeX styles
* manage digital documents
* easy searching

Visit [http://www.plaschg.net/bibwiki Bibwiki's Homepage].

===Mendeley===
Mendeley Desktop is an bibliographic programm which has a working Openoffice 'Cite 'n Write' plugin working for the Windows variant. You will have to register at their site, which also enables you to see the cited works of other users of your particular branch and share your used citations with other interested users. It currently supports BibTex/LaTex, Endnote, RIS and PDF(for quick reference). You can also use it to check any citations on Google Scholar.

Visit [http://www.mendeley.com/ Mendeley's Homepage] for more information.

==LaTeX / BibTeX==

[http://www.latex-project.org/ LaTeX] is a high-quality typesetting system, with features designed for the production of technical and scientific documentation. LaTeX is (or was) the de facto standard for the communication and publication of scientific documents.

[http://www.bibtex.org BibTeX] is the bibliographic subsystem for LaTeX,it is a citation formating and a bibliographic database tool. BibTeX styles definition files are small programs written in an un-named programming language [[http://www.forth.org/ FORTH] like]. This make them almost impossible to utilise in other applications. On the other hand, its database format for bibliographical references is widely used and most other bibliographic applications can import and export that format. It looks like this -
<pre>
@INBOOK{chicago,
title = "The Chicago Manual of Style",
publisher = "University of Chicago Press"
edition = "Thirteenth",
year = 1982,
pages = "400--401",
key = "Chicago" }
@BOOK{texbook,
author = "Donald E. Knuth",
title= "The {{\TeX}book}",
publisher = "Addison-Wesley",
year = 1984 }
</pre>

===The Jurabib package===

Extended BibTeX citation support for the humanities and legal texts. [http://www.jurabib.org/ jurabib] is a package for the LaTeX typesetting system and supports citations used in the humanities and by German law students. This package enables automated citation with BIBTEX for legal studies and the humanities. In addition, the package provides commands for specifying editors in a commentary in a convenient way.

This package is no longer actively developed.

===The biblatex package===

Massively extended BibTeX citation support. [http://www.ctan.org/tex-archive/help/Catalogue/entries/biblatex.html biblatex] is a package for the LaTeX typesetting system and adds a lot of new fields which overcome most of BibTeX's traditional shortcomings (e.g. book authors, gender, original publication, titles of multipart publications etc.). Biblatex hands the complete control of the appearance of citations and bibliography over to LaTeX, the BibTeX program itself is only used for sorting. The result is much more control for the user in a properly documented language.

==Linux==

=== OpenOffice/KBibTex/LyX/oolatex ===

The current way to create a bibliography in OOo makes it too difficult to produce a nicely formatted bibliography (at least it's too difficult for me). After trying a lot of the other alternatives, I found a way that works for me using KBibTex to create a BibTex database, LyX to create a nicely formatted bibliography, and oolatex to produce an OpenOffice .odt version of the LyX bibliography. First, use KBibTex to create the database (with your choice of formatting sytle) and export a BibTex database. Then open LyX and add a BibTex database. You have to add citations in order for the bibliographic entries to appear in the References or Bibliography. Export this to a latex file (either pdflatex or plain). Then we need to compile the latex - this takes several passes to resolve all the references. If the latex file is named "newfile1.tex", then use the following steps:

<nowiki>
#Compiling Latex file with BibTex bibliography</nowiki>

<nowiki>#Takes several passes to resolve references</nowiki>

<nowiki>#Use LyX to create document, export to latex</nowiki>

''latex newfile1.tex''

''bibtex newfile1''

''latex newfile1.tex''

''latex newfile1.tex''

<nowiki># Now convert to .odt</nowiki>

''oolatex newfile1''

<nowiki># Open the .odt in OpenOffice</nowiki>

''openoffice.org-2.1 --writer newfile1.odt &
''

At this point you should have a nicely formatted bibliography that you can paste into your OpenOffice document. An OpenOffice bibliographic database has been created using a user-defined format (thanks to oolatex).

Alternatively, you can use latex2rtf to create an .rtf version of the bibliography and open this in OpenOffice. My experience, however, is that it is not as nicely formatted:

''latex2rtf newfile1''

But of course, you can output an .rtf directly from KBibTex.

I did try to get LyX to export the .odt directly and I could swear I had it working (adding a new file format and a new converter in the Tools | Preferences) but I couldn't repeat it. LyX came with a set up for creating the older .swx format file - but this didn't seem to work. But the manual method outlined above works consistently.

--[[User:Rabil|Rabil]] 19:35, 14 January 2007 (CET)

===Tellico===

The Tellico application is the first one I have come across that uses xslt to format Bibliographic reports / tables. This is interesting as this is the method that we have been proposing for OpenOffice Bibliographic application, but we have not had any examples until now. See http://www.periapsis.org/tellico/

''"Tellico is a KDE application for keeping track of your book collection, bibliographies, video collection, or music collection. Tellico allows you to enter your collection in a catalogue database, saving many different properties like title, author, etc. Two different views of your collection are shown. On the left, your entries are grouped together by any field you like, allowing you to see how many are in each group. On the right, the values of the fields are shown, allowing you to customize your view to show whichever fields are most important to you. On the bottom is the field editor, where you can enter the data."''

''The data is saved in XML format, which makes for easy parsing. Unless you modify the fields yourself, the data follows a simple and documented DTD. It will run on any platform which KDE supports, most commonly Linux. Tellico is licensed under the GNU General Public License, giving you the freedom to modify and distribute the source code."''

'''Capabilities'''

* Supports collections of books, bibliographic entries, videos, or music.
* Supports any number of user-defined fields, of eight different types: text, paragraph, list, checkbox, year, URL, and tables.
* Handles books with multiple authors, genres, keywords, etc.
* Automatically formats titles and names
* Supports collection searching and view filtering
* Sorts and groups collection by various properties
* Automatically validates ISBN
* Allows customizable output through XSLT
* Imports Bibtex, Bibtexml, and CSV
* Exports to Bibtex, Bibtexml, CSV, and HTML

===BibTeXML===

BibTeX as XML markup. Markup scheme; - A bibliography DTD and schema for XML that expresses the content model in BibTeX -- the bibliographic system for use with LaTeX, which is widely adopted by the scientific community. BibTeXML is shipped with tools to uptranslate native TeX-syntax BibTeX bibliographies to XML, and translating this into any markup scheme. Hence one is able to profit from both the existing BibTeX system and bibliographies as well as the presentation and transformation facilities offered by XML. Our goal is to maintain a strict BibTeX schema and develop (and collect!) conversion tools that will help you tag your bibliographic data in XML and save typing time, or export it to HTML, DocBook or native BibTeX syntax. http://bibtexml.sourceforge.net/

===BibML===

BibML is an XML markup language designed to contain bibliographic information, particularly as content exported in Bibtex and Refer notations. BibML also contains content types from DocBook's <bibliography>, and as such may be considered an integration of the three sources. The web page contains a useful 'BibML Element Comparison Table' comparing the attributes of BibML, Bibtex, docbook and refer. http://kmi.open.ac.uk/projects/ceryle/docs/NOTE-bibml.html

===BibX===

The intention of BibX -- begun by Taco Hoekwater to serve as the basis for his XML rewrite of the ConTeXt bib module -- is to be the XML equivalent to RIS and BibTeX, but to significantly improve on them. http://tex.aanhet.net/bibx Download the current DTD.
ISDN Search
"A distributed search portal of common sources of ISBN numbers, with permanent caching of results. To provide a open-source free interface for ISBN retrieval using HTML, SQL or XML to be independent of any toolkits or software." http://sourceforge.net/projects/isbnsearch/

===YAZ===

Z39.50 is the protocol used to query databases and library catalogues for bibliographic information.
YAZ is a C / C++ programmer's toolkit supporting the development of Z39.50v3 / SRW clients and servers. Sample clients and servers are included with the distribution, and documentation can be browsed from this page. (Also available for MAC OS X).
NEW: The latest version of YAZ supports SRW/SRU (over HTTP). The YAZ server operates as both a simple HTTP 1.1 server and Z39.50 target (on the same port). The current version of YAZ includes support for the industry standard ZOOM API for Z39.50. This API vastly simplifies the process of writing new clients using YAZ, and it reduces your dependency on any single toolkit. ZOOM can also operate as a SRW client. Read more about ZOOM in YAZ here. The software library compiles in Windows and Linux. There is also a demonstration client program - IRTCL (requires YAZ and Tcl/Tk libraries be installed) that can perform the reference searches. It does everything but save or export the results ! However it is good model of how to use the toolkit. [http://bibliographic.openoffice.org/irclient.jpeg Screen pic]. [http://www.indexdata.dk/yaz/ www.indexdata.dk/yaz/]

===RefDB===

RefDB is a reference database and bibliography tool for SGML, XML, and LaTeX/BibTeX documents. It allows users to share databases over a network. It is lightweight and portable to basically all platforms with a decent C compiler. And it's released under the GNU General Public License.
The citestylex DTD from RefDB defines bibliographic formatting styles, and v2 will be updated to support BibX when it is done
RefDB is currently known to build and run out of the tarball on at least these platforms: Linux FreeBSD NetBSD Solaris (using gcc) OSX/Darwin Windows+Cygwin
RefDB appears to be the only available tool to create HTML, PostScript, PDF, DVI, MIF, or RTF output from DocBook or TEI sources with fully formatted citations and bibliographies according to publisher's specifications (check out some examples). Additional document types can be easily added. Project Home Page [http://refdb.sourceforge.net refdb.sourceforge.net].

===Sixpack===

Sixpack is a graphical and command-line bibliography database manager written in Perl/Tk. It interacts with the supplied package 'bp', (see below) which can import and export from a number of formats including bibtex, endnote, medline, procite, and many others. It can download references directly off the Web, and open articles using external viewers. It can also interface with Emacs/XEmacs and Lyx [LaTeX with a GUI interface] . It also has instructions on how to interact with openoffice / [[StarOffice]] using cvs files and database import functions [I have used this]. There are also some experimental filters to export sixpack data to the OpenOffice Bibliographic Database - using CSV format - see the Bibliographic Project Document and Files pages. Sadly it is not being well maintained. Home Page - [http://sourceforge.net/projects/sixpack sourceforge.net/projects/sixpack]

===bp===

bp is a Perl library that is designed to:
Let you quickly make tools to access bibliographies
Let you quickly make tools to access bibliographies
Let you access multiple bibliography formats transparently
Let you convert between formats
Let you convert between character sets
Developer - My first goal when designing the package was only the first -- I had written a number of tools that accessed my BibTeX bibliographies, and I saw that I was reusing a lot of code. So I decided to make a generic package to access BibTeX bibliographies. About a year later I decided that it would be even better if the package could read multiple formats, and convert between them. The result is bp. Parts of the package are still missing (namely documentation, automatic format recognition, and a good set of utilities), but everything needed for a working system exists. Home Page - http://www.ecst.csuchico.edu/~jacobsd/bib/bp/index.html

===gBib===

gBib is a user-friendly Gnome BibTeX database browser and editor. It provides facilities for merging BibTeX files, managing key conflicts, and adding bibliographic citations in LyX. Home Page - http://gbib.seul.org

===Pybliographer===

Pybliographer is a tool for managing bibliographic databases. The application is based written in Python and has a text-based and a GTK GUI interface It supports several bibliography formats and can be used for searching, editing, reformatting, etc.. Due to its nature, it can be extended to many uses (generating HTML pages according to bibliographic searches, etc). Pybliographer has a class library structure that could allow other applications to make use of it's facilities. It might be possible to provide a link from this program to insert citations into OpenOffice. There are only a few citation styles defined so far. Home Page -
http://www.pybliographer.org

The Pybliographer developers are considering major enhancements to the application and have produced some planing documents which has very good discussion of bibliographic and user client program issues. They are well worth a look at - http://www.pybliographer.org/development

===Kaspaliste===

Kaspaliste is a literature and knowledge database. It handles all kinds of books, articles, journals, web pages etc. But the database goes beyond simply storing bibliographical information. There is the possibility to create annotated links between pieces of information (like the content of a book chapter) and to group the links in categories. It is based on KDE and uses the Postgres relational database. It is a promising project but currently does not have import or export functions other than a Bibtex export. There are no links to other programs such as OpenOffice. Last release 2004-05-12. http://kaspaliste.sourceforge.net/

==Web Applications==

===Aigaion===
Aigaion is a free, web-based platform for managing annotated bibliographies. It allows the user(s) to order publications in a self-chosen topic structure and offers an intuitive user interface. Aigaion is built on the [[Bibliographic_Software_and_Standards_Information#BibTeX |BibTeX]] format and has excellent BibTeX import and export facilities.

Features
* Multi-user facilities
* Intuitive user interface
* Easy management of publications and topics
* Create public or private notes on publications
* Import of the BibTeX and [http://www.refman.com/support/risformat_intro.asp RIS] ([[Bibliographic_Software_and_Standards_Information#Endnote |Endnote]], [[Bibliographic_Software_and_Standards_Information#Reference Manager |Reference Manager]]) format
* Export of BibTeX and RIS (RIS is under development) format
[http://aigaion.sourceforge.net/ Aigaion homepage]

===BibORB===
BibORB is a tool to manage bibliographies recorded in BibTeX format using a simple Web browser.

[http://biborb.glymn.net/doku.php?id=features BibORB homepage]

===Memento===
Memento is next generation of web based bibliographic software that goes beyond simple searching, storing, and exporting articles. It is one stop solution for students, researchers, scholars where they can manage their bibliography, create and share reports and network with professionals.
Features:
* Clean, simple Internet Explorer and Firefox compatible interface
* Memento constantly fetches articles from all the famous online journals and conference websites to keep it database upto date.
* Import articles in multiple format such bibtex, endnote, RIS, etc.
* Export articles in bibtex or Microsoft Word 2007 Bibliographic XML
* Write personal notes, or upload PDF related to an article
* Write publicly viewable comments related to an article
* Create reports, attach articles to report, and share reports with other users
* Explore other users with similar interest
* Create watch list for articles, authors, keywords and receive new articles in RSS feed

[http://findnwrite.com/memento Memento homepage]

===BiblioWeb===

BiblioWeb is a web enabled bibliographic software. All the basic functions of bibliographic software are delivered through web browser. A Web user can be assigned "Read" or "Write" privileges. Users with "Read" accounts can search, browse, display, and export bibliographic records. Users with "Write" accounts can add, edit, delete, import, even format document through web browser. BiblioWeb is the ideal solution for a research group to share a common bibliographic database on the Web. It also supports a threaded discussion forum. http://www.biblioscape.com/bibliohost.htm

===User::Blibrestez55/Books/Scientific Bibliographic Project 2015 OpenOffice.org Wiki===
A bibliographic/software and standards informative scientific database supports collections of ESL books & reading materials,bibliographic cd's.audio,videos & translated languages of scientific books in English,German,French, Italian,Spanish,Turkish,Japanese & other translations.
http://wiki.services.openoffice.org/wiki/User:Blibrestez55/books/Scientific_Bibliographic_Project_2015

Insert->Indexes and Tables->Indexes and Tables->Tab=Indexes/tables;Type=Bibliography

[[Category:Bibliographic]]

===refbase===
http://refbase.sourceforge.net/

Refbase is a web-based, platform-independent, multi-user interface for managing scientific literature & citations.
Main [http://refbase.sourceforge.net/features.html features]:

* a clean and standardized interface that attempts to be as web standards compliant as possible
* a multitude of search options, including quick, simple, advanced as well as powerful SQL search options
* various display options:
** list view: offers customizable and sortable columns
** details view: shows all fields of a particular record
** cite view: displays record entries in a citation style chosen by the user
** print view: eases printing or copying of records
* search within results functionality which provides an easy way of refining your search query
* user-specific fields for personal keywords, notes, etc
* save any search query together with the current display settings
* automatic email announcements for newly added records
* dynamic RSS feeds for recently added/edited records as well as for any custom user query
* [http://wiki.refbase.net/index.php/Importing_Records batch import] of records from various common bibliographic formats and online databases
* export records to MODS XML, Endnote, RIS or BibTeX (via bibutils)
* export to an OpenDocument spreadsheet for use with the current OO.o bibliographic manager
* link records to other records in the database (using static or dynamic links)
* extract literature cited within a text and build an appropriate reference list
* [http://wiki.refbase.net/index.php/Search/Retrieve_web_services Search & retrieve via URL (SRU)] web service
* COinS and unAPI

===RefWorks===

Was founded in 2001 by a team of developers (former Reference Manager developers) in the field of bibliographic database management. RefWorks is a '''web-based''', very flexible, research management, writing and collaboration tool. RefWorks allows users to create personal databases and use them for a variety of research activities. References are quickly and easily imported from text files or online databases. The databases can then be used to manage, store, and share the information. Users can automatically insert references from their database into their papers and generate formatted bibliographies and manuscripts in seconds. http://www.refworks.com/content/products/faqs.asp

Site licenses for organizations are available. Individual licenses are also available. RefWorks supports hundreds of online databases and output styles covering a broad range of subject areas. http://www.refworks.com/

===WIKINDX===

WIKINDX is a free bibliographic and quotations/notes management and article authoring system designed either for single use (on a variety of operating sytems) or multi-user collaborative use across the internet.

[http://wikindx.sourceforge.net/features.html Features]:

* 36 resource types.
* Multi-user mode - create and manage your own bibliographies drawn from the WIKINDX master bibliography and browse other users' bibliographies. (Must be enabled by the administrator.)
* Save your own preferences.
* Enter/edit bibliographic resources.
* Add unlimited file attachments to each resource. (Must be enabled by the administrator.)
* Catalogue resources by categories and keyword(s).
* Enter/edit a general note about the whole resource.
* Enter/edit quotes and paraphrases from those resources.
* Enter/edit thoughts or musings on various aspects of a resource (can be private or public).
* Add keywords to resource metadata such as quotes, paraphrases and musings.
* Use BBCode in all textarea input.
* Cross-reference other WIKINDX resources from within quotes, paraphrases, musings, notes and abstracts.
* Edit keywords, creators, publishers and journals.
* Comprehensive search across all the above with highlighting of search terms using either Quick Search or Power Search.
* Reorder bibliographic lists by first creator, title, resource type, publisher, year of publication timestamp, popularity index or maturity index.
* Select resources by category, keywords, creator, publisher etc.
* Browse all creators, publishers, collections, categories and keywords with font colour and size indicating frequency of occurrence (tag clouds).
* Unlimited primary creators, editors, translators and revisers, composers, agents, performers etc.
* Export bibliographic lists (optionally annotated) with a range of formatting options to RTF (Rich Text Format) files for easy insert into word processors.
* Export bibliographic lists to RIS for import to Endnote, Reference Manager, ProCite etc.
* Export an Endnote tabbed textfile.
* Export an Endnote XML file.
* Export bibliographic lists to BibTeX format.
* Import Endnote XML and bibTeX files.
* Cut 'n' Paste BibTeX entries to the database (amount limited by the administrator).
* View and export in seven bibliographic styles: Chicago, MLA, APA and Harvard, Turabian, British Medical Journal and IEEE. Administrators can copy, edit and create bibliographic styles through the web browser interface.
* Write an article entirely within WIKINDX importing quotes etc. and chose the citation formatting prior to exporting the article to RTF (can be opened in external word processors including OpenOffice).
* Run WIKINDX in core English or other languages (depending on administrator-installed language plug-ins).
* User-defined paging of long bibliographic lists.
* View all quotes, paraphrases and musings or a single random one.
* One-click return to last bibliographic list or single view.
* Store up to 10 bookmarks for quick return to single views.
* Select a visual style.
* WIKINDX has an architecture which enables either in-line or menu plug-ins to be inserted. Write your own or download plug-ins from the sourceforge site.
http://wikindx.sourceforge.net/

===literaturedb===
http://www.literaturedb.com

literaturedb is a bibliographic management software that can help you organize your literature and bibliographic references for scientific documents. It runs as a PHP web site and provides a collaborative space for storing and sharing documents and references.

Main [http://www.literaturedb.com features]:

* Simplicity: You can find all options on just four pages.
* Bibtex: It uses Bibtex entry types and fields so you can reuse references.
* Full text: It stores full text files (pdf, doc, etc.) for quick access.
* Exports: Export to Word, Bibtex, Endnote, MODS and RIS.
* Collaboration: You can share documents in your team and with friends.
* Tagging: You can tag every document with keywords.
* Search function: The search function scans all data entry fields.
* LDAP support: You can reuse the user management of your organization.
* FLOSS: It is free and open source (GPL).

===Contents-Linking===

http://www.multisuchsystem.de/contents.html

Contents-Linking as part of the Multisuchsystem E-Connect [http://www.multisuchsystem.de/]by Hans Hehl is a free webbed-based tool of managing and searching bibliographic records. It is also a linking system, which aims to go most directly to the full text of an article.
It is built only on simple HTML and Javascipt, but able to import at once hundreds of bibliographic records from any of the databases, so a database of own interest can rapidly be created.
Contents-Linking is connected with a knowledge base, which consists of ca. 50000 journal titles supplemented by subject terms and informations about library holdings.

'''Features'''
*Searching articles by terms or strings
*Searching articles by subject terms, alphabetically or by subjects
*Browsing ca. 40000 records
*Displayed records are linked with the full-linked record
*Browsing ca 70000 journal titles of Contents-database
*Displayed journal titles are linked with full-linked records corresponding to these
*Full-linked records are linked with EZB, ZDB, Google Scholar, Google and library holdings
*Contents-Linking may be installed for any library participating in the EZB
*Importing new records from the following databases: JADE Database, Current Contents, British Library Direct, PubMed,IngentaConnect, OVIDSearch, RefDoc, Google Scholar
*Creating a new import filter for another database

http://www.multisuchsystem.de/contents.html

[[Category:Bibliographic|Standards]]
[[Category: Marketing]]
[[Category:Screenshot]]
[[Category:Art]]
[[Category:Documentation]]

Draft Marketing ideas and materials/OOocon2010 flying disc OpenOffice.org

2012-10-02T21:20:12Z

Blibrestez55: **Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki Plan

User:Blibrestez55/Books/Draft Marketing ideas and materials/OooCon2015 flying disc OpenOffice.org-Wiki

*Name: The name of this organization shall be the BLibrestez55 Draft Marketing ideas and materials/OOoCon2015 flying disc-OpenOffice.org Wiki Bibliographical Debate OpenOffice.org Users Group (herein referred to as the BDMIMOCFDGroup).

*Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki Plan

*Marketing Strategy

Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki strategy will be based on communicating OpenOffice.org-Wik's value to the targeted segments. This will be done through a variety of methods. The first method will be strategically placed advertisements.One place that will be used for advertisements will be in Bibliographic categories,and the liberal arts categories that details all of the entertainment in OpenOffice.org-Wiki.This will be the main source of advertisements because the demographics of their readership are fairly similar to Bibus bibliographic database-Bibus demographics.

Another source of marketing will be done with strategic relationships and associations that have similar bibliographic demographics.One prime example is the BLibrestez55 bibliographic database. While bibliographic patrons are not necessarily overwhelmingly single, the rest of the demographics match up.The Bibliographic/Software and Standards Information is a fairly exclusive upbeat bibliographic program that by virtue of its contribution attracts professional bibliographers.The strategic relationship with be mutually beneficial where both organizations will develop visibility for each other.

The other form of advertising will be using "grassroots" methods where bibliographers contribute draft marketing ideas and materials for participants to try drafting marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki for the first time.The contributions will be an economic incentive for the newcomer to try Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki.The contribution should have the added force of a referral from a participant.

Mission
Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki mission is to provide a bibliographic social network. Participants exist to attract and maintain bibliographers.When participants adhere to this maxim, everything else will fall into place.Our services will exceed the expectations of our bibliographers.

Marketing Objectives
•Develop marketing ideas and material awareness through a steady month to month increase of new bibliographers.
•Develop an increase in sales of marketing while achieving a status quo state or decrease in marketing expenses.
•Develop awareness of the structured conversation system measured by bibliographers coming to Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki solely for bibliographic social networking groups.
Financial Objectives
•A double digit growth rate for each future year.
•Reduce the variable costs through efficiency gains.
•Reach profitability within the first year.

*Target Markets
Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki bibliographers can be broken down into three groups, Generation X,Y, and Baby Boomers.

•Professional: this characteristic is intuitive since the underlying element of Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice-org-Wiki is thoughtful conversation, and most professionals appreciate thought-provoking conversation.

•Income over $40,000: this to a large degree is correlated to the fact that they are professional.

•Age 25-75: the largest group of bibliographers looking for bibliograhy databases.

*Positioning
The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki Group will position itself as a reasonably valued bibliographic social networking group that has an innovative, effective system for allowing bibliographers to meet each other.

T*he Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki Group's positioning will leverage their competitive edge:

•A unique approach to getting bibliographers together called the structured bibliographic system. This system is detailed in the Bibliographic category, please refer to that section for more information.

•This system is a competitive edge because most non-bibliographers do not have a niche that they are concentrating on. While every bibliographer has a certain "flavor" and that is why someone will choose one bibliographer or another, the flavor is only surface deep. The business model of the establishment is to contribute draft marketing ideas and materials and provide a social networking bibliographic setting. Beyond these two values, there is little other genuine value that the bibliographers try to provide.

•Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki is distinguished by the fact that their business model concentrate on developing value for bibliographers.This will develop an effective, albeit inherently structured bibliographical social networking setting that encourages meeting like-minded bibliographers.Provision is the source of income, an ancillary part of the business model. Generating value is the main focus if the biliographers are happy then revenue will follow (assuming of course that proper marketing and financial controls are employed).

*Concentrating on the bibliogapher's needs beyond contributing to Draft Marketing ideas and maerials/OOoCon2015 flying disc OpenOffice.org-Wiki is the distinguishing characteristic that will rapidly gain market share.

*Strategies
The single objective is to position bibliography as the premier place for young professional bibliographers to meet like-minded goals marketing bibliographic ideas and materials. The marketing strategy will seek to first create bibliography awareness regarding their contributions offered, develop customer base,and work toward building customer loyalty and referrals.

*The message Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki will seek to communicatewith Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki is THE place to meet intelligent bibliographers. This message will be communicated through a variety of methods. The first method will be advertisements.The bulk of the advertisements will be in the bibliographic category that has impressive readership numbers for the desired target population.

*Another method will be through establishing strategic relationships with organizations that have similar demographics such as bibliography. Establishing a mutually beneficial relationship will allow both organizations to develop visibility for each other.

*The other form of advertising will be using "grassroots" methods where bibliographers will contribute draft marketing ideas and materials for participants to try for the first time.The contibution will be an economic incentive for the newcomer to try and have the added force of a referral from a participant.

*Marketing Mix
Draft Marketing ideas and materials/OOOCon2015 flying disc's OpenOffice.org-Wiki marketing mix is comprised of these following approaches to pricing, distribution, advertising and promotion,and customer service.

•Pricing: the pricing scheme is based on standard industry practices.
•Distribution: all services and products will be distributed from 's retail space.

•Advertising and promotion: the most successful advertising will be with OpenOffice.org. Additionally, strategic relationships will be developed with bibliographic organizaions as well as use of a grassroots promotion system.

•Customer service: obsessive customer attention is the mantra.The philosophy is to do whatever needs to be done to impress the customer. While this could reduce short-term profits, it will strengthen long-term profitability.

*Marketing Research
During the initial phases of the marketing plan development, several bibliographic focus groups will be sponsored to gain insight into a variety of likely bibliographers. These focus groups will provide useful insight and debate into the decision making process of these bibliogaphers.

*An additional source of dynamic market research is a feedback system based on a suggestion card system.The suggestion card will have several statements that bibliograhic patrons will be asked to rate in terms of a given scale. Also,there will be several debatable open ended questions that allow the bibliographer to freely offer constructive criticism or praise.The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki will work hard to implement reasonable suggestions in order to improve their service offerings as well as show committment to bibliographers whose contributions are valued.

*The last source of market research will be competitive analysis.This will be done by regularly visiting competitors and analyzing their service offerings.

*Read more: A bibliographic/software and standards informative scientific database support collections of ESL books & reading materials,bibliographic cd's.audio,videos & translated languages of scientific books in English,German,French, Italian,Spanish,Turkish,Japanese & other translations.
http://wiki.services.openoffice.org/wiki/User:Blibrestez55/books/Scientific_Bibliographic_Project_2015

[[Category:Android Software]]
[[Category:Bibliographic]]
[[Category:Education]]
[[Category:Marketing]]
[[Category:User Experience]]
[[Category:Impress]]
[[Category:Extensions]]
[[Category:Presenter Screen]]
[[Category:Effort]]

Bibliographic/Software and Standards Information

2012-10-02T20:47:07Z

Blibrestez55: *Burundi_Librestez_ Bibliographic/Softwa_ and_ Standards_ Information-Apache OpenOffice Wiki

'''This is a wiki page. Please feel free to add relevant information or to make corrections to it. It is only useful if it is correct and up to date. Comments or suggestions can be put on the Discussion page (from the tab above)'''

==Open Standards Information==

Check [http://wwwsearch.sourceforge.net/bib/openbib.html Open Standards] for info on software for bibliographies and cataloging. It provides a quick overview of the landscape of open-source bibliographic software; both where it has been, but more importantly, where it may yet go. It may be better than this page.

A good source on open standards in regards to XML, is [http://xml.coverpages.org xml.coverpages.org] and of course [http://www.w3.org www.w3.org] the home of the internet.

===OASIS Open Document Format for Office Applications (OpenDocument) TC===

The [http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office OASIS Open Document Format for Office Applications (OpenDocument) TC] is Developing an XML-based file format specification for office applications.
Its [http://wiki.oasis-open.org/office/Bibliographies_and_Citations?%20%0Aaction=show OASIS OpenDocument Technical Sub-committee on Metadata] is looking at standards to support Search, [http://wiki.oasis-open.org/office/Bibliographies_and_Citations Bliographies and Citations]and Workflow Management.

===CiteProc===

The Openoffice Bibliographic project is proposing to use bibliographic citation and reference list generation using a new process called [http://bibliographic.openoffice.org/citeproc/index.html CiteProc]. CiteProc uses an XML citation style language (CSL) to provide, for the first time, the opportunity for the creation and distribution of open bibliographic style definitions that are not specific to a particular word-processor or bibliographic package. Also see [http://www.silmaril.ie/bibliox/biblioxdoc.html BiblioX] for technical discusion of this approach. We now have working examples.

===Citation microformat efforts===

This [http://microformats.org/wiki/citation wiki page] outlines the overall effort to develop a citation microformat. We are documenting current examples of cites/citations on the web today, their implicit/explicit schemas, and current cite/citation formats, with the intent of deriving a cite microformat from that research.

===Bibliophile===

[http://bibliophile.sourceforge.net/ Bibliophile] is an initiative to align the development of bibliographic databases for the web. It aims to promote standards, discussion among users on necessary features and a variety of specific solutions for different fields of research.

===MODS - Metadata Object Description Schema===

The Library of Congress' Network Development and MARC Standards Office, with interested experts, has developed a schema for a bibliographic element set that may be used for a variety of purposes, and particularly for library applications. As an XML schema, the [http://www.loc.gov/standards/mods/ "Metadata Object Description Schema"] (MODS) is intended to be able to carry selected data from existing MARC 21 records as well as to enable the creation of original resource description records. It includes a subset of MARC fields and uses language-based tags rather than numeric ones, in some cases regrouping elements from the MARC 21 bibliographic format. MODS is expressed using the XML schema language of the World Wide Web Consortium.

===Significance of Z39.50 and SRU/W to the OpenOffice Bibliographic Project===

Z39.50 will be the basis of the OOo Bibliographic internet searching facility. There are several opensource software implementation of this protocol. One example is YAZ, the other is SRW - see below.

Z39.50 is an international standard for communication between computer systems primarily, library and information related systems. Z39.50 is becoming increasingly important to the future development and deployment of inter-linked library systems.
[http://www.loc.gov/z3950/agency/zing/zing-home.html Z39.50 and ZING - Z39.50]

===SRU/W - Search/ Retrieve for the Web===

The difference between [http://www.loc.gov/standards/sru/ SRU] and [http://www.loc.gov/standards/sru/srw/ SRW] is that SRU uses HTTP as the transport mechanism. This means that the query itself is transmitted as an URL and that XML is returned as if it were a web page (note: POST, an alternative for using the HTPP transport mechanism, is not allowed in SRU). SRW is SOAP based, meaning that both the query and the result are XML streams. The advantage of this is that a variety of transport mechanisms can be used, including for instance e-mail.

Note: this description pertains to version 1.0 of SRW. Version 1.1 will be released soon. See: Draft SRW Version 1.1
SRW is the "Search/Retrieve Web Service" protocol, which aims to integrate access to various networked resources, and to promote interoperability between distributed databases, by providing a common utilization framework. SRW is a web-service-based protocol whose underpinnings are formed by bringing together more than 20 years experience from the collective implementers of the Z39.50 Information Retrieval protocol with recent developments in the web technologies arena.

SRW features both SOAP and URL-based access mechanisms to provide for a wide variety of possible clients ranging from Microsoft's .Net initiative to simple Javascript and XSLT transformations. It leverages the CQL query language which provides a powerful yet intuitive means to formulate searches. The protocol mandates the use of open and industry-supported standards XML and XML Schema, and where appropriate, XPath and SOAP. SRW has been developed by an international team, minimizing cross-language pitfalls and other potential internationalization problems.

The SRW Initiative, building on Z39.50 along with web technologies, recognizes the importance of Z39.50 (as currently defined and deployed) for business communication, and focuses on getting information to the user. SRW provides semantics for searching databases containing metadata and objects, both text and non-text. Building on Z39.50 semantics enables the creation of gateways to existing Z39.50 systems while reducing the barriers to new information providers, to make their resources available via a standard search and retrieve service.

SRW defines a web service combining several Z39.50 features, most notably, the Search, Present, and Sort Services. Additional features/services may be added later or defined later as new web services. Also see [http://srw.cheshire3.org srw.cheshire3.org]

===CQL - Common Query Language===

[http://www.loc.gov/standards/sru/cql/ CQL] is the query language for SRW and SRU, and may be used by other protocols as well. CQL is designed to be human readable and writable, while maintaining the expressiveness of more complex languages. XCQL, An XML form of CQL, is also available for use with SRW.

===Zoom===
The ZOOM initiative presents an abstract object-oriented API to a subset of the services specified by the Z39.50 standard, also known as the international standard ISO 23950. If you are trying to build any kind of Z39.50 client or client-based service, ZOOM is an excellent place to start. he API is:
Abstract because we don't want to limit its use to a single implementation language.
Object-oriented because the services lend themselves naturally to this widespread idiom.
For a subset of the full Z39.50 services because at this stage simplicity is more important than completeness.
The ZOOM specifications, bindings for several languages, and many implementations, are available for free browsing and download.
ZOOM is a key part of the wider ZING initiative (Z39.50 International: Next Generation). ZING aims to explore a variety of means for broadening the appeal of Information Retrieval tools, techniques and concepts beyond the traditional IR niche markets. [http://zoom.z3950.org/ zoom.z3950.org/]
ez3950 - Simple Implementation of Z39.50 over SOAP using XER
XER provides a mechanism to allow us to provide Z39.50 support over an alternative "internet" protocol without any additional amendments to the current ASN.1 standard. This document outlines an implementors agreement of how to implement XER over SOAP. (SOAP is Simple Object Access Protocol)

===ZeeRex - Z39.50 Explain, Explained and Re-engineered in XML===

[http://explain.z3950.org/ ZeeRex] (rhymes with T. rex) is "Z39.50 Explain, Explained and Re-Engineered in XML". It is an XML schema used to describe the configuration and capabilities of Z39.50 and SRW servers. (Note 'Explain' is a function in Z39.50 by which a server identifies the services it provides.) ZeeRex records are XML documents using The ZeeRex DTD, which is maintained by Rob Sanderson, and is available as an SGML DTD, and XML DTD and an XML Schema.

==Other Links to Bibliographic Information==

Oxford University. [http://users.ox.ac.uk/~ctitext2/service/workshop/bib-overview.html Overview of Personal Bibliographic Software]

[http://www.ilrt.bris.ac.uk/publications/researchreport/rr1032/report_html Review of Personal Bibliographic Systems] from The Institute for Learning and Research Technology, based at the University of Bristol.

[http://www.lib.gla.ac.uk/researchskills/bibsoftware.shtml 'Managing Your References Using Bibliographic Software Packages'] by GLASGOW UNIVERSITY LIBRARY

[http://en.wikipedia.org/wiki/Comparison_of_reference_management_software Comparison of reference management software] on Wikipedia

A comprehensive study of bibliographic data requirements is [http://www.ifla.org/VII/s13/frbr/frbr.htm 'Functional Requirements for Bibliographic Records'] (144 pages, 620Kbytes) by the International Federation of Library Associations and Institutions in PDF format. And a related report [http://www.miskatonic.org/library/frbr.html 'FRBR and Fundamental Cataloguing Rules'].
Bibliographic Utilities information from [http://www.canadiancontent.net/dir/Top/Reference/Libraries/Library_and_Information_Science/Technical_Services/Cataloguing/Bibliographic_Utilities/ Canadian Content - Bibliographic Utilities] which includes descriptions of tools to find, create, edit, and manipulate bibliographic collections.

==Java==

===AlleMeineBuecher.Net===

This free software provides an easy to use interface. It autmatically looks up book details and book covers by given ISBN numbers. It can do exports. It's compatible with standard barcode-scanners. [http://allemeinebuecher.net AlleMeineBuecher.NET] It's ideal solution for private book collections. The UI is available in English and German.

===B3===

B3 is a free bibliography manager that provides a graphic interface to Bibtex. However, B3 uses its own format: an XML extension of the Bibtex format. B3 has GUI reading and writing XML files and exporting them as Bibtex files. It also includes a Journal Dictionary, a dictionary linking Journal names and their abbreviations. It allows copy/paste the bibliography into a word processor, in order to save boring and upsetting tasks. B3 stands for Bibliography Base for Biologists, since the author is a biologist and only knows about biology journals bibliography. Of course, many tools of B3 may be useful for other disciplines. B3 includes many more features, and tries to provide a free alternative to currently used bibliography managers like EndNotes(C).B3 uses powerful and widely used standard new web languages to store, format and display bibliography data, namely:
XML (eXtensible Markup Language) to manage databases,
XSL (eXtensible Stylesheets Language) to process them,
XHTML (eXtensible Hyper Text Markup Language) to display them in a web browser,
As a result, B3 is a very portable application (it can run under Windows, Mac and Unix-like systems). It tends to be compatible with OpenOffice because it can export data to a bibliography database. It can easily be customized: Everyone who knows XSL can write a stylesheet and implement its own bibliography format. It supports Pubmed internet searches. For more info see http://b3bib.sourceforge.net/

===JabRef===

JabRef is a graphical frontend to manage BibTeX databases, the standard LaTeX bibliography reference format. JabRef is built to be platform independent (requires Java >= 1.5, or 1.4.2 for older versions). It merges and extends the functionalities of BibKeeper (Morten O. Alver) and JBibtexManager (Nizar Batada). Features. Detailed editing of bibtex entries. Search a pattern in the whole bibliography. You can group entries by keywords or any other fields. Supports import of various formats - BibTex, Endnote (text), ISI Web of Science, Medline/Pubmed (xml), Scifinder format, OVID, INSPEC, Biblioscape, JStor and RIS. Supports different export formats - HTML, Docbook, BibTeXML. You can add your own fields to any BibTeX entry type. Launch external applications: PDF/PS viewers, web browser, insert citations into LyX, Kile and WinEdt. Now you can insert citations and bibliographies into OpenOffice documents. Automatic Key generation. http://jabref.sourceforge.net/index.php

===Synapsen===

Synapsen is a hypertextual card catalog that enables the management of bibliographies. However, in contrast to normal literature management software, synapsen offers a very distinct advantage: with catchwords entered by the user, the program connects individual cards automatically and creates not only a network of cards whose relation to each other might have been forgotten, but also creates completely unexpected connections and relations between individual entries. synapsen is therefore not only for electronic literature management, but also a helping hand when writing scientific texts, which participates in communication with the author in order to augment lines of argumentation and the generation of ideas.

synapsen is written in JAVA, runs on all operating systems, and supports standards like BiBTeX, RTF, LaTeX, SQL. It can be found under http://www.verzetteln.de/synapsen/synapsen_e.html

Since version 2.5 Synapsen offers a direct connection to Open Office 2.2 via the UNO interface. This allows you to insert bibliographical data of Synapsen's cards directly as footnotes in OpenOffice Writer.

===DAFFODIL===

Distributed Agents for User-Friendly Access of Digital Libraries

(Text from the [http://www.is.informatik.uni-duisburg.de/projects/daffodil/index.html.en project website]:) Despite the fact that many Digital Libraries (DLs) are available on the Internet, users cannot effectively use them because of inadequate functionality, deficient visualisation and insufficient integration of different DLs. In the framework of this project we develop a user-oriented access system for DLs which overcomes these drawbacks. Based on experiences from the librarian area, higher functions to assist proved search strategies will be implemented. Different DLs will be tightly integrated, so that system-wide search and navigation is possible. The system will be adaptive towards different user wishes, regarding preferences concerning content and system involvement.

The first two year project phase is concluded and the outcome is a running prototyp which covers all goals.
Second period (2002-2004)

The key concept of strategic support when using digital libraries will be a major topic in the next years, but we will extend it to all levels of the information search process and the different kinds to gather information. To organise the found material, there annotations and interpretations we will develop a personal digital library. It provides simultaneously a user- and taskoriented context, to support searching and browsing better then up till now.

As additional method for the information gathering we will integrate the path model, collaborative filtering as well as the workflow model into Daffodil. The last two methods will allow for cooperation by using digital libraries. A special role is given to the librarian in the cooperative environment.

The graphical user interface design supports different interaction level -- exspecially circumstantial work tasks will be supported by software-information agents, but with regards to the user autonomy. Likewise the iterative process during the retrieval will be optimised.

Daffodil is a projects in the strategic research initiative V3D2 (Distributed Processing and Delivery of Digital Documents) of the German Research Foundation (DFG). http://www.is.informatik.uni-duisburg.de/projects/daffodil/index.html.en http://www.daffodil.de/

You can start DAFFODIL directly from the web using Java Web Start: http://www.is.informatik.uni-duisburg.de/projects/daffodil/pdaffodil.jnlp (Login/Password: visitor/visitor)

===TextCite===

TextCite is a program for organizing and commenting textual citations from texts (books, articles, or other published works) for use in producing scientific or academic publications. You can organize by publication, author, category, or outline. It works with bibliographic management programs like Citation, Endnote, RefWorks, and BibTeX (i.e. via programs such as JabRef and BibDesk), providing important text/citation management capabilities that these programs lack, while still allowing for rapid footnote and bibliography generation by means of your favorite bibliography manager. It also exports to PDF and Word (RTF).

TextCite is open source software, and is available free of charge from the [http://textcite.sourceforge.net/ TextCite homepage]. It requires a minimum of Java 1.5, and is available in packages for Windows and Mac OS, as well as in an executable .jar format for running on Unix/Linux.

==Perl, Python==

===Pbib===

PBib is a small tool for browsing and processing bibliographic databases which is written in Perl (that's where the "P" in the name comes from :-). PBib works similar to the classical BibTeX, but can be extended for arbitrary bibliography databases (including BibTeX files and the OpenOffice.org database format), arbitrary bibliography styles (e.g. ACM, IEEE), and arbitrary document formats (including RTF and OpenOffice text documents). http://www.ipsi.fraunhofer.de/~tandler/PBib/

'''DESCRIPTION'''

I wrote PBib to have something like BibTex for MS Word [ Perl is avaiable in Linux as well] that can use a various sources for bibliographic references, not just BibTex files, but also database systems. Especially, I wanted to use the [[StarOffice]] bibliographic database.
Now, PBib can be extended in a couple of dimensions:
bibliographic styles such as ACM style or IEEE style.
document format such as Plain text, (La)TeX, Word, RTF, OpenOffice
bibliographic database format such as bibtex, refer, tib, but also database systems with different mappings to database fields.

===RISImport.py===
A python script that reads RIS format files containing one or more references and inserts them into the default OpenOffice.orgBibliography/'biblio' database. The setup of this script is relatively straight-forward, and the current RIS tag to 'bilbio' column mapping has worked great for me for the few engineering electronic portals that I use (e.g., IEEEXplore, Inspec, MathSciNet).

Additionally, as I will briefly explain here, the mapping (in some cases relatively advanced) can be easily customized to fit your need (i.e., different reference sources and their slightly different interpretations of the RIS format). It can be found in our Documents and Files Page.

Michael Sowka, E-mail: msowka@rogers.com www.sowka.com

==MS Windows==

===Bibliographix===

Bibliographix is designed for people who are writing their doctoral thesis, frequently writing scientific texts, or reading a lot of literature. The free Basic version offers more than any other free reference manager. It should be more than enough for undergraduates. Try it out as long as you like. The Pro-Version is starting at USD 40 and offers everything an academic might need.

What is special about Bibliographix?
High-end reference management for a low-end price. A unique combination of reference management and idea outlining. Two items that belong together. Save yourself the typing: Import data from online libraries. You'll never want to miss it: one-click tables of references. Bibliographix can insert intext citations into OpenOffice. http://www.bibliographix.com/

===Biblioscape===

Biblioscape product family is designed to help researchers collecting and managing bibliographic data, notes, as well as generating citations and bibliography for publications.
Research Information Manager. Biblioscape is an information manager for researchers, scholarly writers, students, and librarians. People use it to organize literature references, research notes, automatically generate citations and bibliographies automatically, search and capture bibliographic data on the Internet, and post bibliographic databases live on the web. The flood of bibliographic resources on the Internet requires new solutions for bibliographic information management. Biblioscape offers such a solution -- whether you work alone, or as part of a group, or even in a large organization. For a comprehensive feature list see http://www.biblioscape.com/features.htm. There is a free 'lite' version called Biblioscape Express. There is an associated [[Bibliographic_Software_and_Standards_Information#BiblioWeb| BiblioWeb service.]] http://www.biblioscape.com .

===Citavi===

Citavi (Lat., I cited) is a user-friendly bibliographic application that works with OpenOffice, Microsoft Office and other Windows word-processing software. Citavi enables you to organize bibliographic material in a very practical way. The program provides access to up to 4000 bibliographic databases and library catalogs. You can process literary content, collect citations, organize draft texts and schedule tasks.

Citavi can be integrated with OpenOffice Writer: references and citations can be inserted directly via the publication assistant. After finishing your work, Citavi scans the ODT file and inserts a full formatted bibliography at the end of your document. It is also very easy to export the references collected to OpenOffice Calc. A free version of Citavi is available and an English version of Citavi will be released Sept. 2010.
Citavi Home Page http://www.citavi.com

===Citeit!===

This product is a very good example of maintaining bibliographic data linked to textual information.

"CiteIt! is revolutionary software that automates the tedious process of creating accurate and properly formatted legal citation. CiteIt! enables users to instantly import legal citations from online legal databases, such as Westlaw? and Lexis-Nexis?, with a click of a button. With CiteIt!, you never again have to type a legal citation into a document, spend time worrying about proper Bluebook or ALWD formatting, or write a citation down as you search on an online legal database."

General CITEIT! features:
Imports citations from on-line legal databases or any web page with a click of a button.
Automatically places all citations imported or entered in proper citation form.
Provides all of the possible cite forms for each citation for quick insertion into any document.

Professional and Advanced Versions of CiteIt! can create a table of authorities in seconds. Powerful notes and keyword features allows you to easily store, organize and search your research information. CiteIt! integrates seamlessly with Microsoft Word or Corel WordPerfect, so accurate citation is only a few mouse clicks away. Intuitive user interface means that anyone can start using CiteIt! in minutes. Two versions of CiteIt! are available - one which supports the 17th Edition of The Bluebook and another which supports the ALWD Citation Manual.
http://www.citeit.com/product/default.htm

===CiteSmart===

[http://www.miresoft.net/citesmart CiteSmart] is a fairly new yet very powerful software application specifically designed for researchers in Biology and medical disciplines in mind, but can also be used with a variety of documents (law, business, patents ...). CiteSmart implements new features called [http://www.miresoft.net/citeclick CiteClick], [http://www.miresoft.net/citeclick CiteClick] and [http://www.miresoft.net/citeclick RefDrag] (patent pending). Users relying on [http://www.ncbi.nlm.nih.gov/sites/entrez?db=PubMed Medline / PubMed] for their every day work can store and cite references into a word document (and simultaneously in a local library) in a single click. CiteSmart is intended for reaserchers who work with Medline / PubMed. CiteSmart can be customized to work with any bibliographic database and potentially any working environment. Its single click philosophy makes CiteSmart invisible to users who don't need to interact with it for storing and citing references. CiteSmart also offers hundreds of styles and a style editor/ to create styles in minutes. Finally among other cool features, it is compatible with EndNote and Reference Manager, it also can rebuild libraries from word documents containing references, it automatically handles 'in press references' and update them as they appear in print. Many other feature are being added regularly. MireSoft's website: [http://www.miresoft.net MireSoft]. View CiteSmart in action [http://www.miresoft.net/citesmart/videos/ CiteSmart Screencasts].

===Endnote===

A very popular and widely used Bibliographic package. Recommended by many Universities.
Platform: Windows & Mac
Description: Integrates three key bibliographical tasks within the one package: the searching of remote bibliographical databases on the Internet; the organisation of references in a database, and the creation of bibliographies. EndNote can be fully integrated with Word and other Windows word-processing software. Documents can be scanned and shorthand citations expanded and complete bibliographies created. EndNote libraries created on different platforms are compatible with each other. Home Page http://www.endnote.com/. Note that EndNote, ProCite, and Reference Manager are all owned by the same company, [http://www.thomsonresearchsoft.com/ Thomson ResearchSoft]. http://thomsonisiresearchsoft.com/compare/ is a useful comparison of these products from the vendor's perspective.

===Ibidem===

Manage your bibliographic material with consummate ease using Ibidem. Store bibliographic information in the simple database format, and Ibidem will generate your bibliographic references for you. The program will automatically format footnotes, endnotes, parenthetical short forms, and reference-number in-text citations, along with end-of-paper reference lists and bibliographies, according to hundreds of academic styles. Subsequent references are automatically abbreviated using shortened titles, ibid. or op. cit., as appropriate. You can change styles, and watch footnotes or endnotes appear or disappear as all citations in a document are automatically updated to the new format. Ibidem's seamlessly integrated, state-of-the-art control of bibliographic data will save you countless hours of drudgery, and your personal bibliographic databases will always be at your fingertips.
- instant access from within the word processor - notecard-like forms for easy entry of bibliographic information - drop-down lists for fast, consistent data entry - various viewing options, including short-list table view - fast and easy searching, sorting, and subset management - over 200 academic bibliographic styles included - works can be cited in open documents with a simple mouse click - color coding identifies Ibidem-generated citations in open documents - option to automatically exclude author or year from a citation - automatically shortens subsequent references to a cited work - dynamically-updated preview box - extensive search operators and features - subsets dynamically updated as records are added to database - numerous customizable options. Add-on module Archiva/ArchivaPro supports capture of bibliographic data from web sites with automatic conversion to Ibidem format.
This product has the best example of integrated bibliographic and style support that I have seen - a good model for OpenOffice to emulate.
A demo version is available. It is limited to 30 days use and no printing is possible - although you could export any work done on it.
http://www.notabene.com/

Some screen shots of Ibidem also http://www.notabene.com/brochures/ibidem.html

===Inflight Referencer===

Inflight Referencer, is a relatively new commercial bibliography application designed to work with all Windows word processors including Open Office. It integrates three important bibliographical tasks within the one product; organizing references into a database for future retrieval, creation of bibliography lists and insertion of reference citations into document text.

Specializing in APA and Harvard styles as well as customizable formats to meet various other citation and referencing styles, Inflight Referencer automates the process of creating reference lists. There is support for approximately 50 different media types including print and online resources. This bibliography product was originally designed in unison with university graduates, to produce a product that was inevitably simple to use and focused on achieving the goals of academics efficiently.

Inflight Referencer Home Page http://www.inflighttm.com/ref/

===LiteRat===

LiteRat is a free (as in free beer) application that is based on Microsoft Access 2.0. The programme can be used from Windows 3.1 through to Windows XP. The user interface concept comes from the flash card system. LiteRat can handle various kinds of bibliographic entries, quotes, and makes it also possible that several people can work on one database. A quick work flow can be achieved by this program, although it cannot connect to online databases due to its age.

LiteRat saves its data in Access 2.0 files which can be used through ODBC interfaces with other database applications. It's possible to export the bibliographic entries into a proprietary tagged text file, but there are macros for Mirosoft Word and OpenOffice.org shipped with the program that convert these tags into styles.

LiteRat's successor is Citavi.

LiteRat's website: http://www.literat.net/

===Nota Bene===

Nota Bene: a word processor for scholars ... a bibliographic manager for those who are tired of typing/formatting their own citations and bibliographies ... a personal search engine for those who want to find anything they've ever written in seconds ... a database manager for those who have things to keep track of ... a Hebrew, Greek, Cyrillic, IPA word processor for those who want more than just fonts ... a set of tools for scholars who want to focus on their writing and research ... a work of art for scholars who appreciate the finer things in life ... a community of scholars.
[Nota Bene's bibliographic facility is called 'Ibidem']
http://www.notabene.com

===ProCite===

ProCite is a Windows and Mac Bibliographic application similar in function to Endnotes and Reference Manager. The program can still be bought but no new software version have been made since 1999. [http://www.procite.com www.procite.com]

===Reference Manager===
Reference Manager is a comprehensive Bibliographic package with Bibliographic database, internet searching, and citation and bibliographic table formating. It is widely used at many professional organizations and universities.
The program has many important features for heavy users who do a lot of literature searching and keep many references in their databases. Version 11 now includes a web publisher which allows you to publish your databases and share your references with colleagues.
There also is a Network version of the program.

It has a downloadable collection of over 1200 citation styles. It saves bibliographic date in RIS format which is now a common data exchange format. [http://www.refman.com www.refman.com]

===Scholars Aid===

A commercial application that works with OpenOffice (on MS Windows). Note that there is also a free 'Lite' version. "Scholar's Aid keeps bibliographical data and notes together, for the very good reason that scholars always need to keep their notes linked to the sources from which those notes were made. Indeed, in academic writing, scholars constantly support their argument by reference to the sources on which they have worked. Thus, in directly quoting from one of these sources, or in making reference to another's ideas, rigorous academic scholarship demands accurate and detailed citation of those original sources.

Scholar's Aid automates this process in a manner that is entirely without precedent. Provided the original notes were written in the Notes module of Scholar's Aid, by selecting text and clicking the transfer button, the program transfers the selected text into the word-processed document and, at exactly the same time, inserts an appropriate citation into the document in a form (footnote, short footnote, endnote, short endnote and parenthetical reference) determined by the user. The program even includes the correct page number in the citation that it creates within the word-processed document. Scholar's Aid surely is the Reference Processor?". http://www.scholarsaid.com/

==Windows, Linux, other==

===Bibutils===

The bibutils program set interconverts between various bibliography formats using a common XML intermediate. For example, one can convert RIS-format files to Bibtex by doing two transformations: RIS->MODS->Bibtex. By using a common intermediate for N formats, only 2N programs are required and not N²-N. These programs operate on the command line and are styled after standard UNIX-like filters:

* bib2xml - convert bibtex to XML intermediate 
* copac2xml - convert COPAC format references to XML intermediate 
* end2xml - convert endnote to XML intermediate 
* isi2xml - convert ISI web of science to XML intermediate 
* med2xml - convert Pubmed XML references to XML intermediate 
* modsclean - a MODS to MODS converter for testing puposes mostly 
* ris2xml - convert RIS format to XML intermediate 
* xml2bib - convert XML intermediate into bibtex 
* xml2ris - convert XML intermediate into RIS format 
[http://www.scripps.edu/~cdputnam/software/bibutils/bibutils.html www.scripps.edu/~cdputnam/software/bibutils/bibutils.html]

===Bibus===

Bibus is a bibliographic database. It has been designed with OpenOffice.org in mind. The "ultimate" goal is to have an opensource bibliographic software that will allow easy formatting (and reformatting) of the bibliographic index in OpenOffice.org Writer.
Main Features
Compatible with two database engines: MySQL and SQLite.
Hierarchical organization of the references with user defined keys.
Drag & drop to easily organize references.

Designed for multiuser:
You can share the database between an "unlimited" number of users.
Each user will have its own classification.
Powerful and easy to use search engine.
Live queries, that is searches that will update when the database change (this is simply a saved SQL query).

On-line PubMed access.

Import PubMed (Medline) and EndNote/Refer records.
Connection to OpenOffice.org. You can insert references in an open OpenOffice.org text document and format the bibliography directly in Bibus.
Thanks to Python and wxWidgets, Bibus should work on most modern platform (GNU/linux with gtk; Windows; MacOS; etc...). Version 0.8 has been tested on GNU/linux and Windows2000. Note for Windows 98 users.

Foreign language support through Unicode and gettext. As of version 1.2, Bibus is available in English, French, Portuguese, German, Spanish and Chinese.
For more info see http://bibus-biblio.sourceforge.net/

===OpenOffice===

The [http://www.openoffice.org OpenOffice] word-processor 'Writer' includes basic bibliographic support. OpenOffice has a [http://bibliographic.openoffice.org bibliographic project] whose goal is to improve the bibliographic facilities.

===rtfbtx===
[http://www.dmst.aueb.gr/dds/sw/ports/rtfbtx/ rtfbtx] is a hacked collection of BibTeX styles for doing bibliographies with MS Word & BibTeX. It produces the bibliography in RTF format & uses bookmarks to link citations to it.

Christos tried using it with OpenOffice and it only works for the alpha style, since for the rest I'm supposed to link to the "paragraph number" of the bookmark and OO doesn't support such a thing.

===Zotero===

[http://www.zotero.org/ Zotero] [zoh-TAIR-oh] is a free, easy-to-use Firefox extension to help you collect, manage, and cite your research sources. It lives right where you do your work — in the web browser itself. Requires [http://en-us.www.mozilla.com/en-US/firefox/2.0/releasenotes/ Firefox version 2]. There is now a OpenOffice-Zotero [http://www.zotero.org/documentation/openoffice_integration extension/plug-in] to allow users to insert citations and Bibliographic tables into your documents.

===Bibwiki===

Bibwiki is a extension to MediaWiki to manage bibliographies. The bibliographies are stored in plain BibTeX files. In contrast to other programs, Bibwiki alters the bibliographic files directly. You don't need a seperate database.

Bibwiki adds a special page where you can add, import, edit and export bibliographic records. Together with Mediawiki it's very easy to organize your excerpts, memos, or annotations and link them to the bibliographic records.

Features:
* import from various sources: Ex Libris' Aleph, Amazon, ProQuest
* export list of references using BibTeX styles
* manage digital documents
* easy searching

Visit [http://www.plaschg.net/bibwiki Bibwiki's Homepage].

===Mendeley===
Mendeley Desktop is an bibliographic programm which has a working Openoffice 'Cite 'n Write' plugin working for the Windows variant. You will have to register at their site, which also enables you to see the cited works of other users of your particular branch and share your used citations with other interested users. It currently supports BibTex/LaTex, Endnote, RIS and PDF(for quick reference). You can also use it to check any citations on Google Scholar.

Visit [http://www.mendeley.com/ Mendeley's Homepage] for more information.

==LaTeX / BibTeX==

[http://www.latex-project.org/ LaTeX] is a high-quality typesetting system, with features designed for the production of technical and scientific documentation. LaTeX is (or was) the de facto standard for the communication and publication of scientific documents.

[http://www.bibtex.org BibTeX] is the bibliographic subsystem for LaTeX,it is a citation formating and a bibliographic database tool. BibTeX styles definition files are small programs written in an un-named programming language [[http://www.forth.org/ FORTH] like]. This make them almost impossible to utilise in other applications. On the other hand, its database format for bibliographical references is widely used and most other bibliographic applications can import and export that format. It looks like this -
<pre>
@INBOOK{chicago,
title = "The Chicago Manual of Style",
publisher = "University of Chicago Press"
edition = "Thirteenth",
year = 1982,
pages = "400--401",
key = "Chicago" }
@BOOK{texbook,
author = "Donald E. Knuth",
title= "The {{\TeX}book}",
publisher = "Addison-Wesley",
year = 1984 }
</pre>

===The Jurabib package===

Extended BibTeX citation support for the humanities and legal texts. [http://www.jurabib.org/ jurabib] is a package for the LaTeX typesetting system and supports citations used in the humanities and by German law students. This package enables automated citation with BIBTEX for legal studies and the humanities. In addition, the package provides commands for specifying editors in a commentary in a convenient way.

This package is no longer actively developed.

===The biblatex package===

Massively extended BibTeX citation support. [http://www.ctan.org/tex-archive/help/Catalogue/entries/biblatex.html biblatex] is a package for the LaTeX typesetting system and adds a lot of new fields which overcome most of BibTeX's traditional shortcomings (e.g. book authors, gender, original publication, titles of multipart publications etc.). Biblatex hands the complete control of the appearance of citations and bibliography over to LaTeX, the BibTeX program itself is only used for sorting. The result is much more control for the user in a properly documented language.

==Linux==

=== OpenOffice/KBibTex/LyX/oolatex ===

The current way to create a bibliography in OOo makes it too difficult to produce a nicely formatted bibliography (at least it's too difficult for me). After trying a lot of the other alternatives, I found a way that works for me using KBibTex to create a BibTex database, LyX to create a nicely formatted bibliography, and oolatex to produce an OpenOffice .odt version of the LyX bibliography. First, use KBibTex to create the database (with your choice of formatting sytle) and export a BibTex database. Then open LyX and add a BibTex database. You have to add citations in order for the bibliographic entries to appear in the References or Bibliography. Export this to a latex file (either pdflatex or plain). Then we need to compile the latex - this takes several passes to resolve all the references. If the latex file is named "newfile1.tex", then use the following steps:

<nowiki>
#Compiling Latex file with BibTex bibliography</nowiki>

<nowiki>#Takes several passes to resolve references</nowiki>

<nowiki>#Use LyX to create document, export to latex</nowiki>

''latex newfile1.tex''

''bibtex newfile1''

''latex newfile1.tex''

''latex newfile1.tex''

<nowiki># Now convert to .odt</nowiki>

''oolatex newfile1''

<nowiki># Open the .odt in OpenOffice</nowiki>

''openoffice.org-2.1 --writer newfile1.odt &
''

At this point you should have a nicely formatted bibliography that you can paste into your OpenOffice document. An OpenOffice bibliographic database has been created using a user-defined format (thanks to oolatex).

Alternatively, you can use latex2rtf to create an .rtf version of the bibliography and open this in OpenOffice. My experience, however, is that it is not as nicely formatted:

''latex2rtf newfile1''

But of course, you can output an .rtf directly from KBibTex.

I did try to get LyX to export the .odt directly and I could swear I had it working (adding a new file format and a new converter in the Tools | Preferences) but I couldn't repeat it. LyX came with a set up for creating the older .swx format file - but this didn't seem to work. But the manual method outlined above works consistently.

--[[User:Rabil|Rabil]] 19:35, 14 January 2007 (CET)

===Tellico===

The Tellico application is the first one I have come across that uses xslt to format Bibliographic reports / tables. This is interesting as this is the method that we have been proposing for OpenOffice Bibliographic application, but we have not had any examples until now. See http://www.periapsis.org/tellico/

''"Tellico is a KDE application for keeping track of your book collection, bibliographies, video collection, or music collection. Tellico allows you to enter your collection in a catalogue database, saving many different properties like title, author, etc. Two different views of your collection are shown. On the left, your entries are grouped together by any field you like, allowing you to see how many are in each group. On the right, the values of the fields are shown, allowing you to customize your view to show whichever fields are most important to you. On the bottom is the field editor, where you can enter the data."''

''The data is saved in XML format, which makes for easy parsing. Unless you modify the fields yourself, the data follows a simple and documented DTD. It will run on any platform which KDE supports, most commonly Linux. Tellico is licensed under the GNU General Public License, giving you the freedom to modify and distribute the source code."''

'''Capabilities'''

* Supports collections of books, bibliographic entries, videos, or music.
* Supports any number of user-defined fields, of eight different types: text, paragraph, list, checkbox, year, URL, and tables.
* Handles books with multiple authors, genres, keywords, etc.
* Automatically formats titles and names
* Supports collection searching and view filtering
* Sorts and groups collection by various properties
* Automatically validates ISBN
* Allows customizable output through XSLT
* Imports Bibtex, Bibtexml, and CSV
* Exports to Bibtex, Bibtexml, CSV, and HTML

===BibTeXML===

BibTeX as XML markup. Markup scheme; - A bibliography DTD and schema for XML that expresses the content model in BibTeX -- the bibliographic system for use with LaTeX, which is widely adopted by the scientific community. BibTeXML is shipped with tools to uptranslate native TeX-syntax BibTeX bibliographies to XML, and translating this into any markup scheme. Hence one is able to profit from both the existing BibTeX system and bibliographies as well as the presentation and transformation facilities offered by XML. Our goal is to maintain a strict BibTeX schema and develop (and collect!) conversion tools that will help you tag your bibliographic data in XML and save typing time, or export it to HTML, DocBook or native BibTeX syntax. http://bibtexml.sourceforge.net/

===BibML===

BibML is an XML markup language designed to contain bibliographic information, particularly as content exported in Bibtex and Refer notations. BibML also contains content types from DocBook's <bibliography>, and as such may be considered an integration of the three sources. The web page contains a useful 'BibML Element Comparison Table' comparing the attributes of BibML, Bibtex, docbook and refer. http://kmi.open.ac.uk/projects/ceryle/docs/NOTE-bibml.html

===BibX===

The intention of BibX -- begun by Taco Hoekwater to serve as the basis for his XML rewrite of the ConTeXt bib module -- is to be the XML equivalent to RIS and BibTeX, but to significantly improve on them. http://tex.aanhet.net/bibx Download the current DTD.
ISDN Search
"A distributed search portal of common sources of ISBN numbers, with permanent caching of results. To provide a open-source free interface for ISBN retrieval using HTML, SQL or XML to be independent of any toolkits or software." http://sourceforge.net/projects/isbnsearch/

===YAZ===

Z39.50 is the protocol used to query databases and library catalogues for bibliographic information.
YAZ is a C / C++ programmer's toolkit supporting the development of Z39.50v3 / SRW clients and servers. Sample clients and servers are included with the distribution, and documentation can be browsed from this page. (Also available for MAC OS X).
NEW: The latest version of YAZ supports SRW/SRU (over HTTP). The YAZ server operates as both a simple HTTP 1.1 server and Z39.50 target (on the same port). The current version of YAZ includes support for the industry standard ZOOM API for Z39.50. This API vastly simplifies the process of writing new clients using YAZ, and it reduces your dependency on any single toolkit. ZOOM can also operate as a SRW client. Read more about ZOOM in YAZ here. The software library compiles in Windows and Linux. There is also a demonstration client program - IRTCL (requires YAZ and Tcl/Tk libraries be installed) that can perform the reference searches. It does everything but save or export the results ! However it is good model of how to use the toolkit. [http://bibliographic.openoffice.org/irclient.jpeg Screen pic]. [http://www.indexdata.dk/yaz/ www.indexdata.dk/yaz/]

===RefDB===

RefDB is a reference database and bibliography tool for SGML, XML, and LaTeX/BibTeX documents. It allows users to share databases over a network. It is lightweight and portable to basically all platforms with a decent C compiler. And it's released under the GNU General Public License.
The citestylex DTD from RefDB defines bibliographic formatting styles, and v2 will be updated to support BibX when it is done
RefDB is currently known to build and run out of the tarball on at least these platforms: Linux FreeBSD NetBSD Solaris (using gcc) OSX/Darwin Windows+Cygwin
RefDB appears to be the only available tool to create HTML, PostScript, PDF, DVI, MIF, or RTF output from DocBook or TEI sources with fully formatted citations and bibliographies according to publisher's specifications (check out some examples). Additional document types can be easily added. Project Home Page [http://refdb.sourceforge.net refdb.sourceforge.net].

===Sixpack===

Sixpack is a graphical and command-line bibliography database manager written in Perl/Tk. It interacts with the supplied package 'bp', (see below) which can import and export from a number of formats including bibtex, endnote, medline, procite, and many others. It can download references directly off the Web, and open articles using external viewers. It can also interface with Emacs/XEmacs and Lyx [LaTeX with a GUI interface] . It also has instructions on how to interact with openoffice / [[StarOffice]] using cvs files and database import functions [I have used this]. There are also some experimental filters to export sixpack data to the OpenOffice Bibliographic Database - using CSV format - see the Bibliographic Project Document and Files pages. Sadly it is not being well maintained. Home Page - [http://sourceforge.net/projects/sixpack sourceforge.net/projects/sixpack]

===bp===

bp is a Perl library that is designed to:
Let you quickly make tools to access bibliographies
Let you quickly make tools to access bibliographies
Let you access multiple bibliography formats transparently
Let you convert between formats
Let you convert between character sets
Developer - My first goal when designing the package was only the first -- I had written a number of tools that accessed my BibTeX bibliographies, and I saw that I was reusing a lot of code. So I decided to make a generic package to access BibTeX bibliographies. About a year later I decided that it would be even better if the package could read multiple formats, and convert between them. The result is bp. Parts of the package are still missing (namely documentation, automatic format recognition, and a good set of utilities), but everything needed for a working system exists. Home Page - http://www.ecst.csuchico.edu/~jacobsd/bib/bp/index.html

===gBib===

gBib is a user-friendly Gnome BibTeX database browser and editor. It provides facilities for merging BibTeX files, managing key conflicts, and adding bibliographic citations in LyX. Home Page - http://gbib.seul.org

===Pybliographer===

Pybliographer is a tool for managing bibliographic databases. The application is based written in Python and has a text-based and a GTK GUI interface It supports several bibliography formats and can be used for searching, editing, reformatting, etc.. Due to its nature, it can be extended to many uses (generating HTML pages according to bibliographic searches, etc). Pybliographer has a class library structure that could allow other applications to make use of it's facilities. It might be possible to provide a link from this program to insert citations into OpenOffice. There are only a few citation styles defined so far. Home Page -
http://www.pybliographer.org

The Pybliographer developers are considering major enhancements to the application and have produced some planing documents which has very good discussion of bibliographic and user client program issues. They are well worth a look at - http://www.pybliographer.org/development

===Kaspaliste===

Kaspaliste is a literature and knowledge database. It handles all kinds of books, articles, journals, web pages etc. But the database goes beyond simply storing bibliographical information. There is the possibility to create annotated links between pieces of information (like the content of a book chapter) and to group the links in categories. It is based on KDE and uses the Postgres relational database. It is a promising project but currently does not have import or export functions other than a Bibtex export. There are no links to other programs such as OpenOffice. Last release 2004-05-12. http://kaspaliste.sourceforge.net/

==Web Applications==

===Aigaion===
Aigaion is a free, web-based platform for managing annotated bibliographies. It allows the user(s) to order publications in a self-chosen topic structure and offers an intuitive user interface. Aigaion is built on the [[Bibliographic_Software_and_Standards_Information#BibTeX |BibTeX]] format and has excellent BibTeX import and export facilities.

Features
* Multi-user facilities
* Intuitive user interface
* Easy management of publications and topics
* Create public or private notes on publications
* Import of the BibTeX and [http://www.refman.com/support/risformat_intro.asp RIS] ([[Bibliographic_Software_and_Standards_Information#Endnote |Endnote]], [[Bibliographic_Software_and_Standards_Information#Reference Manager |Reference Manager]]) format
* Export of BibTeX and RIS (RIS is under development) format
[http://aigaion.sourceforge.net/ Aigaion homepage]

===BibORB===
BibORB is a tool to manage bibliographies recorded in BibTeX format using a simple Web browser.

[http://biborb.glymn.net/doku.php?id=features BibORB homepage]

===Memento===
Memento is next generation of web based bibliographic software that goes beyond simple searching, storing, and exporting articles. It is one stop solution for students, researchers, scholars where they can manage their bibliography, create and share reports and network with professionals.
Features:
* Clean, simple Internet Explorer and Firefox compatible interface
* Memento constantly fetches articles from all the famous online journals and conference websites to keep it database upto date.
* Import articles in multiple format such bibtex, endnote, RIS, etc.
* Export articles in bibtex or Microsoft Word 2007 Bibliographic XML
* Write personal notes, or upload PDF related to an article
* Write publicly viewable comments related to an article
* Create reports, attach articles to report, and share reports with other users
* Explore other users with similar interest
* Create watch list for articles, authors, keywords and receive new articles in RSS feed

[http://findnwrite.com/memento Memento homepage]

===BiblioWeb===

BiblioWeb is a web enabled bibliographic software. All the basic functions of bibliographic software are delivered through web browser. A Web user can be assigned "Read" or "Write" privileges. Users with "Read" accounts can search, browse, display, and export bibliographic records. Users with "Write" accounts can add, edit, delete, import, even format document through web browser. BiblioWeb is the ideal solution for a research group to share a common bibliographic database on the Web. It also supports a threaded discussion forum. http://www.biblioscape.com/bibliohost.htm

===User::Blibrestez55/Books/Scientific Bibliographic Project 2015 OpenOffice.org Wiki===
A bibliographic/software and standards informative scientific database supports collections of ESL books & reading materials,bibliographic cd's.audio,videos & translated languages of scientific books in English,German,French, Italian,Spanish,Turkish,Japanese & other translations.
http://wiki.services.openoffice.org/wiki/User:Blibrestez55/books/Scientific_Bibliographic_Project_2015

[[Category:Bibliographic]]

===refbase===
http://refbase.sourceforge.net/

Refbase is a web-based, platform-independent, multi-user interface for managing scientific literature & citations.
Main [http://refbase.sourceforge.net/features.html features]:

* a clean and standardized interface that attempts to be as web standards compliant as possible
* a multitude of search options, including quick, simple, advanced as well as powerful SQL search options
* various display options:
** list view: offers customizable and sortable columns
** details view: shows all fields of a particular record
** cite view: displays record entries in a citation style chosen by the user
** print view: eases printing or copying of records
* search within results functionality which provides an easy way of refining your search query
* user-specific fields for personal keywords, notes, etc
* save any search query together with the current display settings
* automatic email announcements for newly added records
* dynamic RSS feeds for recently added/edited records as well as for any custom user query
* [http://wiki.refbase.net/index.php/Importing_Records batch import] of records from various common bibliographic formats and online databases
* export records to MODS XML, Endnote, RIS or BibTeX (via bibutils)
* export to an OpenDocument spreadsheet for use with the current OO.o bibliographic manager
* link records to other records in the database (using static or dynamic links)
* extract literature cited within a text and build an appropriate reference list
* [http://wiki.refbase.net/index.php/Search/Retrieve_web_services Search & retrieve via URL (SRU)] web service
* COinS and unAPI

===RefWorks===

Was founded in 2001 by a team of developers (former Reference Manager developers) in the field of bibliographic database management. RefWorks is a '''web-based''', very flexible, research management, writing and collaboration tool. RefWorks allows users to create personal databases and use them for a variety of research activities. References are quickly and easily imported from text files or online databases. The databases can then be used to manage, store, and share the information. Users can automatically insert references from their database into their papers and generate formatted bibliographies and manuscripts in seconds. http://www.refworks.com/content/products/faqs.asp

Site licenses for organizations are available. Individual licenses are also available. RefWorks supports hundreds of online databases and output styles covering a broad range of subject areas. http://www.refworks.com/

===WIKINDX===

WIKINDX is a free bibliographic and quotations/notes management and article authoring system designed either for single use (on a variety of operating sytems) or multi-user collaborative use across the internet.

[http://wikindx.sourceforge.net/features.html Features]:

* 36 resource types.
* Multi-user mode - create and manage your own bibliographies drawn from the WIKINDX master bibliography and browse other users' bibliographies. (Must be enabled by the administrator.)
* Save your own preferences.
* Enter/edit bibliographic resources.
* Add unlimited file attachments to each resource. (Must be enabled by the administrator.)
* Catalogue resources by categories and keyword(s).
* Enter/edit a general note about the whole resource.
* Enter/edit quotes and paraphrases from those resources.
* Enter/edit thoughts or musings on various aspects of a resource (can be private or public).
* Add keywords to resource metadata such as quotes, paraphrases and musings.
* Use BBCode in all textarea input.
* Cross-reference other WIKINDX resources from within quotes, paraphrases, musings, notes and abstracts.
* Edit keywords, creators, publishers and journals.
* Comprehensive search across all the above with highlighting of search terms using either Quick Search or Power Search.
* Reorder bibliographic lists by first creator, title, resource type, publisher, year of publication timestamp, popularity index or maturity index.
* Select resources by category, keywords, creator, publisher etc.
* Browse all creators, publishers, collections, categories and keywords with font colour and size indicating frequency of occurrence (tag clouds).
* Unlimited primary creators, editors, translators and revisers, composers, agents, performers etc.
* Export bibliographic lists (optionally annotated) with a range of formatting options to RTF (Rich Text Format) files for easy insert into word processors.
* Export bibliographic lists to RIS for import to Endnote, Reference Manager, ProCite etc.
* Export an Endnote tabbed textfile.
* Export an Endnote XML file.
* Export bibliographic lists to BibTeX format.
* Import Endnote XML and bibTeX files.
* Cut 'n' Paste BibTeX entries to the database (amount limited by the administrator).
* View and export in seven bibliographic styles: Chicago, MLA, APA and Harvard, Turabian, British Medical Journal and IEEE. Administrators can copy, edit and create bibliographic styles through the web browser interface.
* Write an article entirely within WIKINDX importing quotes etc. and chose the citation formatting prior to exporting the article to RTF (can be opened in external word processors including OpenOffice).
* Run WIKINDX in core English or other languages (depending on administrator-installed language plug-ins).
* User-defined paging of long bibliographic lists.
* View all quotes, paraphrases and musings or a single random one.
* One-click return to last bibliographic list or single view.
* Store up to 10 bookmarks for quick return to single views.
* Select a visual style.
* WIKINDX has an architecture which enables either in-line or menu plug-ins to be inserted. Write your own or download plug-ins from the sourceforge site.
http://wikindx.sourceforge.net/

===literaturedb===
http://www.literaturedb.com

literaturedb is a bibliographic management software that can help you organize your literature and bibliographic references for scientific documents. It runs as a PHP web site and provides a collaborative space for storing and sharing documents and references.

Main [http://www.literaturedb.com features]:

* Simplicity: You can find all options on just four pages.
* Bibtex: It uses Bibtex entry types and fields so you can reuse references.
* Full text: It stores full text files (pdf, doc, etc.) for quick access.
* Exports: Export to Word, Bibtex, Endnote, MODS and RIS.
* Collaboration: You can share documents in your team and with friends.
* Tagging: You can tag every document with keywords.
* Search function: The search function scans all data entry fields.
* LDAP support: You can reuse the user management of your organization.
* FLOSS: It is free and open source (GPL).

===Contents-Linking===

http://www.multisuchsystem.de/contents.html

Contents-Linking as part of the Multisuchsystem E-Connect [http://www.multisuchsystem.de/]by Hans Hehl is a free webbed-based tool of managing and searching bibliographic records. It is also a linking system, which aims to go most directly to the full text of an article.
It is built only on simple HTML and Javascipt, but able to import at once hundreds of bibliographic records from any of the databases, so a database of own interest can rapidly be created.
Contents-Linking is connected with a knowledge base, which consists of ca. 50000 journal titles supplemented by subject terms and informations about library holdings.

'''Features'''
*Searching articles by terms or strings
*Searching articles by subject terms, alphabetically or by subjects
*Browsing ca. 13000 records in parts of 1000
*Displayed records are linked with the full-linked record
*Browsing ca 4600 journal titles of Contents-database
*Displayed journal titles are linked with full-linked records corresponding to these
*Full-linked records are linked with EZB, ZDB, Google Scholar, Google and library holdings
*Contents-Linking may be installed for any library participating in the EZB
*Importing new records from the following databases: JADE Database, TIBOrder, Current Contents, British Library Direct, PubMed,IngentaConnect, FirstSearch, OVIDSearch, RefDoc, Google Scholar
*Creating a new import filter for another database

http://www.multisuchsystem.de/contents.html

[[Category:Bibliographic|Standards]]
[[Category: Marketing]]
[[Category:Screenshot]]
[[Category:Art]]
[[Category:Documentation]]

Bibliographic/Software and Standards Information

2012-10-02T20:41:23Z

Blibrestez55: *Burundi_Librestez_Bibliographic/Software_ and_ Standards_ Information-Apache OpenOffice Wiki

'''This is a wiki page. Please feel free to add relevant information or to make corrections to it. It is only useful if it is correct and up to date. Comments or suggestions can be put on the Discussion page (from the tab above)'''

==Open Standards Information==

Check [http://wwwsearch.sourceforge.net/bib/openbib.html Open Standards] for info on software for bibliographies and cataloging. It provides a quick overview of the landscape of open-source bibliographic software; both where it has been, but more importantly, where it may yet go. It may be better than this page.

A good source on open standards in regards to XML, is [http://xml.coverpages.org xml.coverpages.org] and of course [http://www.w3.org www.w3.org] the home of the internet.

===OASIS Open Document Format for Office Applications (OpenDocument) TC===

The [http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office OASIS Open Document Format for Office Applications (OpenDocument) TC] is Developing an XML-based file format specification for office applications.
Its [http://wiki.oasis-open.org/office/Bibliographies_and_Citations?%20%0Aaction=show OASIS OpenDocument Technical Sub-committee on Metadata] is looking at standards to support Search, [http://wiki.oasis-open.org/office/Bibliographies_and_Citations Bliographies and Citations]and Workflow Management.

===CiteProc===

The Openoffice Bibliographic project is proposing to use bibliographic citation and reference list generation using a new process called [http://bibliographic.openoffice.org/citeproc/index.html CiteProc]. CiteProc uses an XML citation style language (CSL) to provide, for the first time, the opportunity for the creation and distribution of open bibliographic style definitions that are not specific to a particular word-processor or bibliographic package. Also see [http://www.silmaril.ie/bibliox/biblioxdoc.html BiblioX] for technical discusion of this approach. We now have working examples.

===Citation microformat efforts===

This [http://microformats.org/wiki/citation wiki page] outlines the overall effort to develop a citation microformat. We are documenting current examples of cites/citations on the web today, their implicit/explicit schemas, and current cite/citation formats, with the intent of deriving a cite microformat from that research.

===Bibliophile===

[http://bibliophile.sourceforge.net/ Bibliophile] is an initiative to align the development of bibliographic databases for the web. It aims to promote standards, discussion among users on necessary features and a variety of specific solutions for different fields of research.

===MODS - Metadata Object Description Schema===

The Library of Congress' Network Development and MARC Standards Office, with interested experts, has developed a schema for a bibliographic element set that may be used for a variety of purposes, and particularly for library applications. As an XML schema, the [http://www.loc.gov/standards/mods/ "Metadata Object Description Schema"] (MODS) is intended to be able to carry selected data from existing MARC 21 records as well as to enable the creation of original resource description records. It includes a subset of MARC fields and uses language-based tags rather than numeric ones, in some cases regrouping elements from the MARC 21 bibliographic format. MODS is expressed using the XML schema language of the World Wide Web Consortium.

===Significance of Z39.50 and SRU/W to the OpenOffice Bibliographic Project===

Z39.50 will be the basis of the OOo Bibliographic internet searching facility. There are several opensource software implementation of this protocol. One example is YAZ, the other is SRW - see below.

Z39.50 is an international standard for communication between computer systems primarily, library and information related systems. Z39.50 is becoming increasingly important to the future development and deployment of inter-linked library systems.
[http://www.loc.gov/z3950/agency/zing/zing-home.html Z39.50 and ZING - Z39.50]

===SRU/W - Search/ Retrieve for the Web===

The difference between [http://www.loc.gov/standards/sru/ SRU] and [http://www.loc.gov/standards/sru/srw/ SRW] is that SRU uses HTTP as the transport mechanism. This means that the query itself is transmitted as an URL and that XML is returned as if it were a web page (note: POST, an alternative for using the HTPP transport mechanism, is not allowed in SRU). SRW is SOAP based, meaning that both the query and the result are XML streams. The advantage of this is that a variety of transport mechanisms can be used, including for instance e-mail.

Note: this description pertains to version 1.0 of SRW. Version 1.1 will be released soon. See: Draft SRW Version 1.1
SRW is the "Search/Retrieve Web Service" protocol, which aims to integrate access to various networked resources, and to promote interoperability between distributed databases, by providing a common utilization framework. SRW is a web-service-based protocol whose underpinnings are formed by bringing together more than 20 years experience from the collective implementers of the Z39.50 Information Retrieval protocol with recent developments in the web technologies arena.

SRW features both SOAP and URL-based access mechanisms to provide for a wide variety of possible clients ranging from Microsoft's .Net initiative to simple Javascript and XSLT transformations. It leverages the CQL query language which provides a powerful yet intuitive means to formulate searches. The protocol mandates the use of open and industry-supported standards XML and XML Schema, and where appropriate, XPath and SOAP. SRW has been developed by an international team, minimizing cross-language pitfalls and other potential internationalization problems.

The SRW Initiative, building on Z39.50 along with web technologies, recognizes the importance of Z39.50 (as currently defined and deployed) for business communication, and focuses on getting information to the user. SRW provides semantics for searching databases containing metadata and objects, both text and non-text. Building on Z39.50 semantics enables the creation of gateways to existing Z39.50 systems while reducing the barriers to new information providers, to make their resources available via a standard search and retrieve service.

SRW defines a web service combining several Z39.50 features, most notably, the Search, Present, and Sort Services. Additional features/services may be added later or defined later as new web services. Also see [http://srw.cheshire3.org srw.cheshire3.org]

===CQL - Common Query Language===

[http://www.loc.gov/standards/sru/cql/ CQL] is the query language for SRW and SRU, and may be used by other protocols as well. CQL is designed to be human readable and writable, while maintaining the expressiveness of more complex languages. XCQL, An XML form of CQL, is also available for use with SRW.

===Zoom===
The ZOOM initiative presents an abstract object-oriented API to a subset of the services specified by the Z39.50 standard, also known as the international standard ISO 23950. If you are trying to build any kind of Z39.50 client or client-based service, ZOOM is an excellent place to start. he API is:
Abstract because we don't want to limit its use to a single implementation language.
Object-oriented because the services lend themselves naturally to this widespread idiom.
For a subset of the full Z39.50 services because at this stage simplicity is more important than completeness.
The ZOOM specifications, bindings for several languages, and many implementations, are available for free browsing and download.
ZOOM is a key part of the wider ZING initiative (Z39.50 International: Next Generation). ZING aims to explore a variety of means for broadening the appeal of Information Retrieval tools, techniques and concepts beyond the traditional IR niche markets. [http://zoom.z3950.org/ zoom.z3950.org/]
ez3950 - Simple Implementation of Z39.50 over SOAP using XER
XER provides a mechanism to allow us to provide Z39.50 support over an alternative "internet" protocol without any additional amendments to the current ASN.1 standard. This document outlines an implementors agreement of how to implement XER over SOAP. (SOAP is Simple Object Access Protocol)

===ZeeRex - Z39.50 Explain, Explained and Re-engineered in XML===

[http://explain.z3950.org/ ZeeRex] (rhymes with T. rex) is "Z39.50 Explain, Explained and Re-Engineered in XML". It is an XML schema used to describe the configuration and capabilities of Z39.50 and SRW servers. (Note 'Explain' is a function in Z39.50 by which a server identifies the services it provides.) ZeeRex records are XML documents using The ZeeRex DTD, which is maintained by Rob Sanderson, and is available as an SGML DTD, and XML DTD and an XML Schema.

==Other Links to Bibliographic Information==

Oxford University. [http://users.ox.ac.uk/~ctitext2/service/workshop/bib-overview.html Overview of Personal Bibliographic Software]

[http://www.ilrt.bris.ac.uk/publications/researchreport/rr1032/report_html Review of Personal Bibliographic Systems] from The Institute for Learning and Research Technology, based at the University of Bristol.

[http://www.lib.gla.ac.uk/researchskills/bibsoftware.shtml 'Managing Your References Using Bibliographic Software Packages'] by GLASGOW UNIVERSITY LIBRARY

[http://en.wikipedia.org/wiki/Comparison_of_reference_management_software Comparison of reference management software] on Wikipedia

A comprehensive study of bibliographic data requirements is [http://www.ifla.org/VII/s13/frbr/frbr.htm 'Functional Requirements for Bibliographic Records'] (144 pages, 620Kbytes) by the International Federation of Library Associations and Institutions in PDF format. And a related report [http://www.miskatonic.org/library/frbr.html 'FRBR and Fundamental Cataloguing Rules'].
Bibliographic Utilities information from [http://www.canadiancontent.net/dir/Top/Reference/Libraries/Library_and_Information_Science/Technical_Services/Cataloguing/Bibliographic_Utilities/ Canadian Content - Bibliographic Utilities] which includes descriptions of tools to find, create, edit, and manipulate bibliographic collections.

==Java==

===AlleMeineBuecher.Net===

This free software provides an easy to use interface. It autmatically looks up book details and book covers by given ISBN numbers. It can do exports. It's compatible with standard barcode-scanners. [http://allemeinebuecher.net AlleMeineBuecher.NET] It's ideal solution for private book collections. The UI is available in English and German.

===B3===

B3 is a free bibliography manager that provides a graphic interface to Bibtex. However, B3 uses its own format: an XML extension of the Bibtex format. B3 has GUI reading and writing XML files and exporting them as Bibtex files. It also includes a Journal Dictionary, a dictionary linking Journal names and their abbreviations. It allows copy/paste the bibliography into a word processor, in order to save boring and upsetting tasks. B3 stands for Bibliography Base for Biologists, since the author is a biologist and only knows about biology journals bibliography. Of course, many tools of B3 may be useful for other disciplines. B3 includes many more features, and tries to provide a free alternative to currently used bibliography managers like EndNotes(C).B3 uses powerful and widely used standard new web languages to store, format and display bibliography data, namely:
XML (eXtensible Markup Language) to manage databases,
XSL (eXtensible Stylesheets Language) to process them,
XHTML (eXtensible Hyper Text Markup Language) to display them in a web browser,
As a result, B3 is a very portable application (it can run under Windows, Mac and Unix-like systems). It tends to be compatible with OpenOffice because it can export data to a bibliography database. It can easily be customized: Everyone who knows XSL can write a stylesheet and implement its own bibliography format. It supports Pubmed internet searches. For more info see http://b3bib.sourceforge.net/

===JabRef===

JabRef is a graphical frontend to manage BibTeX databases, the standard LaTeX bibliography reference format. JabRef is built to be platform independent (requires Java >= 1.5, or 1.4.2 for older versions). It merges and extends the functionalities of BibKeeper (Morten O. Alver) and JBibtexManager (Nizar Batada). Features. Detailed editing of bibtex entries. Search a pattern in the whole bibliography. You can group entries by keywords or any other fields. Supports import of various formats - BibTex, Endnote (text), ISI Web of Science, Medline/Pubmed (xml), Scifinder format, OVID, INSPEC, Biblioscape, JStor and RIS. Supports different export formats - HTML, Docbook, BibTeXML. You can add your own fields to any BibTeX entry type. Launch external applications: PDF/PS viewers, web browser, insert citations into LyX, Kile and WinEdt. Now you can insert citations and bibliographies into OpenOffice documents. Automatic Key generation. http://jabref.sourceforge.net/index.php

===Synapsen===

Synapsen is a hypertextual card catalog that enables the management of bibliographies. However, in contrast to normal literature management software, synapsen offers a very distinct advantage: with catchwords entered by the user, the program connects individual cards automatically and creates not only a network of cards whose relation to each other might have been forgotten, but also creates completely unexpected connections and relations between individual entries. synapsen is therefore not only for electronic literature management, but also a helping hand when writing scientific texts, which participates in communication with the author in order to augment lines of argumentation and the generation of ideas.

synapsen is written in JAVA, runs on all operating systems, and supports standards like BiBTeX, RTF, LaTeX, SQL. It can be found under http://www.verzetteln.de/synapsen/synapsen_e.html

Since version 2.5 Synapsen offers a direct connection to Open Office 2.2 via the UNO interface. This allows you to insert bibliographical data of Synapsen's cards directly as footnotes in OpenOffice Writer.

===DAFFODIL===

Distributed Agents for User-Friendly Access of Digital Libraries

(Text from the [http://www.is.informatik.uni-duisburg.de/projects/daffodil/index.html.en project website]:) Despite the fact that many Digital Libraries (DLs) are available on the Internet, users cannot effectively use them because of inadequate functionality, deficient visualisation and insufficient integration of different DLs. In the framework of this project we develop a user-oriented access system for DLs which overcomes these drawbacks. Based on experiences from the librarian area, higher functions to assist proved search strategies will be implemented. Different DLs will be tightly integrated, so that system-wide search and navigation is possible. The system will be adaptive towards different user wishes, regarding preferences concerning content and system involvement.

The first two year project phase is concluded and the outcome is a running prototyp which covers all goals.
Second period (2002-2004)

The key concept of strategic support when using digital libraries will be a major topic in the next years, but we will extend it to all levels of the information search process and the different kinds to gather information. To organise the found material, there annotations and interpretations we will develop a personal digital library. It provides simultaneously a user- and taskoriented context, to support searching and browsing better then up till now.

As additional method for the information gathering we will integrate the path model, collaborative filtering as well as the workflow model into Daffodil. The last two methods will allow for cooperation by using digital libraries. A special role is given to the librarian in the cooperative environment.

The graphical user interface design supports different interaction level -- exspecially circumstantial work tasks will be supported by software-information agents, but with regards to the user autonomy. Likewise the iterative process during the retrieval will be optimised.

Daffodil is a projects in the strategic research initiative V3D2 (Distributed Processing and Delivery of Digital Documents) of the German Research Foundation (DFG). http://www.is.informatik.uni-duisburg.de/projects/daffodil/index.html.en http://www.daffodil.de/

You can start DAFFODIL directly from the web using Java Web Start: http://www.is.informatik.uni-duisburg.de/projects/daffodil/pdaffodil.jnlp (Login/Password: visitor/visitor)

===TextCite===

TextCite is a program for organizing and commenting textual citations from texts (books, articles, or other published works) for use in producing scientific or academic publications. You can organize by publication, author, category, or outline. It works with bibliographic management programs like Citation, Endnote, RefWorks, and BibTeX (i.e. via programs such as JabRef and BibDesk), providing important text/citation management capabilities that these programs lack, while still allowing for rapid footnote and bibliography generation by means of your favorite bibliography manager. It also exports to PDF and Word (RTF).

TextCite is open source software, and is available free of charge from the [http://textcite.sourceforge.net/ TextCite homepage]. It requires a minimum of Java 1.5, and is available in packages for Windows and Mac OS, as well as in an executable .jar format for running on Unix/Linux.

==Perl, Python==

===Pbib===

PBib is a small tool for browsing and processing bibliographic databases which is written in Perl (that's where the "P" in the name comes from :-). PBib works similar to the classical BibTeX, but can be extended for arbitrary bibliography databases (including BibTeX files and the OpenOffice.org database format), arbitrary bibliography styles (e.g. ACM, IEEE), and arbitrary document formats (including RTF and OpenOffice text documents). http://www.ipsi.fraunhofer.de/~tandler/PBib/

'''DESCRIPTION'''

I wrote PBib to have something like BibTex for MS Word [ Perl is avaiable in Linux as well] that can use a various sources for bibliographic references, not just BibTex files, but also database systems. Especially, I wanted to use the [[StarOffice]] bibliographic database.
Now, PBib can be extended in a couple of dimensions:
bibliographic styles such as ACM style or IEEE style.
document format such as Plain text, (La)TeX, Word, RTF, OpenOffice
bibliographic database format such as bibtex, refer, tib, but also database systems with different mappings to database fields.

===RISImport.py===
A python script that reads RIS format files containing one or more references and inserts them into the default OpenOffice.orgBibliography/'biblio' database. The setup of this script is relatively straight-forward, and the current RIS tag to 'bilbio' column mapping has worked great for me for the few engineering electronic portals that I use (e.g., IEEEXplore, Inspec, MathSciNet).

Additionally, as I will briefly explain here, the mapping (in some cases relatively advanced) can be easily customized to fit your need (i.e., different reference sources and their slightly different interpretations of the RIS format). It can be found in our Documents and Files Page.

Michael Sowka, E-mail: msowka@rogers.com www.sowka.com

==MS Windows==

===Bibliographix===

Bibliographix is designed for people who are writing their doctoral thesis, frequently writing scientific texts, or reading a lot of literature. The free Basic version offers more than any other free reference manager. It should be more than enough for undergraduates. Try it out as long as you like. The Pro-Version is starting at USD 40 and offers everything an academic might need.

What is special about Bibliographix?
High-end reference management for a low-end price. A unique combination of reference management and idea outlining. Two items that belong together. Save yourself the typing: Import data from online libraries. You'll never want to miss it: one-click tables of references. Bibliographix can insert intext citations into OpenOffice. http://www.bibliographix.com/

===Biblioscape===

Biblioscape product family is designed to help researchers collecting and managing bibliographic data, notes, as well as generating citations and bibliography for publications.
Research Information Manager. Biblioscape is an information manager for researchers, scholarly writers, students, and librarians. People use it to organize literature references, research notes, automatically generate citations and bibliographies automatically, search and capture bibliographic data on the Internet, and post bibliographic databases live on the web. The flood of bibliographic resources on the Internet requires new solutions for bibliographic information management. Biblioscape offers such a solution -- whether you work alone, or as part of a group, or even in a large organization. For a comprehensive feature list see http://www.biblioscape.com/features.htm. There is a free 'lite' version called Biblioscape Express. There is an associated [[Bibliographic_Software_and_Standards_Information#BiblioWeb| BiblioWeb service.]] http://www.biblioscape.com .

===Citavi===

Citavi (Lat., I cited) is a user-friendly bibliographic application that works with OpenOffice, Microsoft Office and other Windows word-processing software. Citavi enables you to organize bibliographic material in a very practical way. The program provides access to up to 4000 bibliographic databases and library catalogs. You can process literary content, collect citations, organize draft texts and schedule tasks.

Citavi can be integrated with OpenOffice Writer: references and citations can be inserted directly via the publication assistant. After finishing your work, Citavi scans the ODT file and inserts a full formatted bibliography at the end of your document. It is also very easy to export the references collected to OpenOffice Calc. A free version of Citavi is available and an English version of Citavi will be released Sept. 2010.
Citavi Home Page http://www.citavi.com

===Citeit!===

This product is a very good example of maintaining bibliographic data linked to textual information.

"CiteIt! is revolutionary software that automates the tedious process of creating accurate and properly formatted legal citation. CiteIt! enables users to instantly import legal citations from online legal databases, such as Westlaw? and Lexis-Nexis?, with a click of a button. With CiteIt!, you never again have to type a legal citation into a document, spend time worrying about proper Bluebook or ALWD formatting, or write a citation down as you search on an online legal database."

General CITEIT! features:
Imports citations from on-line legal databases or any web page with a click of a button.
Automatically places all citations imported or entered in proper citation form.
Provides all of the possible cite forms for each citation for quick insertion into any document.

Professional and Advanced Versions of CiteIt! can create a table of authorities in seconds. Powerful notes and keyword features allows you to easily store, organize and search your research information. CiteIt! integrates seamlessly with Microsoft Word or Corel WordPerfect, so accurate citation is only a few mouse clicks away. Intuitive user interface means that anyone can start using CiteIt! in minutes. Two versions of CiteIt! are available - one which supports the 17th Edition of The Bluebook and another which supports the ALWD Citation Manual.
http://www.citeit.com/product/default.htm

===CiteSmart===

[http://www.miresoft.net/citesmart CiteSmart] is a fairly new yet very powerful software application specifically designed for researchers in Biology and medical disciplines in mind, but can also be used with a variety of documents (law, business, patents ...). CiteSmart implements new features called [http://www.miresoft.net/citeclick CiteClick], [http://www.miresoft.net/citeclick CiteClick] and [http://www.miresoft.net/citeclick RefDrag] (patent pending). Users relying on [http://www.ncbi.nlm.nih.gov/sites/entrez?db=PubMed Medline / PubMed] for their every day work can store and cite references into a word document (and simultaneously in a local library) in a single click. CiteSmart is intended for reaserchers who work with Medline / PubMed. CiteSmart can be customized to work with any bibliographic database and potentially any working environment. Its single click philosophy makes CiteSmart invisible to users who don't need to interact with it for storing and citing references. CiteSmart also offers hundreds of styles and a style editor/ to create styles in minutes. Finally among other cool features, it is compatible with EndNote and Reference Manager, it also can rebuild libraries from word documents containing references, it automatically handles 'in press references' and update them as they appear in print. Many other feature are being added regularly. MireSoft's website: [http://www.miresoft.net MireSoft]. View CiteSmart in action [http://www.miresoft.net/citesmart/videos/ CiteSmart Screencasts].

===Endnote===

A very popular and widely used Bibliographic package. Recommended by many Universities.
Platform: Windows & Mac
Description: Integrates three key bibliographical tasks within the one package: the searching of remote bibliographical databases on the Internet; the organisation of references in a database, and the creation of bibliographies. EndNote can be fully integrated with Word and other Windows word-processing software. Documents can be scanned and shorthand citations expanded and complete bibliographies created. EndNote libraries created on different platforms are compatible with each other. Home Page http://www.endnote.com/. Note that EndNote, ProCite, and Reference Manager are all owned by the same company, [http://www.thomsonresearchsoft.com/ Thomson ResearchSoft]. http://thomsonisiresearchsoft.com/compare/ is a useful comparison of these products from the vendor's perspective.

===Ibidem===

Manage your bibliographic material with consummate ease using Ibidem. Store bibliographic information in the simple database format, and Ibidem will generate your bibliographic references for you. The program will automatically format footnotes, endnotes, parenthetical short forms, and reference-number in-text citations, along with end-of-paper reference lists and bibliographies, according to hundreds of academic styles. Subsequent references are automatically abbreviated using shortened titles, ibid. or op. cit., as appropriate. You can change styles, and watch footnotes or endnotes appear or disappear as all citations in a document are automatically updated to the new format. Ibidem's seamlessly integrated, state-of-the-art control of bibliographic data will save you countless hours of drudgery, and your personal bibliographic databases will always be at your fingertips.
- instant access from within the word processor - notecard-like forms for easy entry of bibliographic information - drop-down lists for fast, consistent data entry - various viewing options, including short-list table view - fast and easy searching, sorting, and subset management - over 200 academic bibliographic styles included - works can be cited in open documents with a simple mouse click - color coding identifies Ibidem-generated citations in open documents - option to automatically exclude author or year from a citation - automatically shortens subsequent references to a cited work - dynamically-updated preview box - extensive search operators and features - subsets dynamically updated as records are added to database - numerous customizable options. Add-on module Archiva/ArchivaPro supports capture of bibliographic data from web sites with automatic conversion to Ibidem format.
This product has the best example of integrated bibliographic and style support that I have seen - a good model for OpenOffice to emulate.
A demo version is available. It is limited to 30 days use and no printing is possible - although you could export any work done on it.
http://www.notabene.com/

Some screen shots of Ibidem also http://www.notabene.com/brochures/ibidem.html

===Inflight Referencer===

Inflight Referencer, is a relatively new commercial bibliography application designed to work with all Windows word processors including Open Office. It integrates three important bibliographical tasks within the one product; organizing references into a database for future retrieval, creation of bibliography lists and insertion of reference citations into document text.

Specializing in APA and Harvard styles as well as customizable formats to meet various other citation and referencing styles, Inflight Referencer automates the process of creating reference lists. There is support for approximately 50 different media types including print and online resources. This bibliography product was originally designed in unison with university graduates, to produce a product that was inevitably simple to use and focused on achieving the goals of academics efficiently.

Inflight Referencer Home Page http://www.inflighttm.com/ref/

===LiteRat===

LiteRat is a free (as in free beer) application that is based on Microsoft Access 2.0. The programme can be used from Windows 3.1 through to Windows XP. The user interface concept comes from the flash card system. LiteRat can handle various kinds of bibliographic entries, quotes, and makes it also possible that several people can work on one database. A quick work flow can be achieved by this program, although it cannot connect to online databases due to its age.

LiteRat saves its data in Access 2.0 files which can be used through ODBC interfaces with other database applications. It's possible to export the bibliographic entries into a proprietary tagged text file, but there are macros for Mirosoft Word and OpenOffice.org shipped with the program that convert these tags into styles.

LiteRat's successor is Citavi.

LiteRat's website: http://www.literat.net/

===Nota Bene===

Nota Bene: a word processor for scholars ... a bibliographic manager for those who are tired of typing/formatting their own citations and bibliographies ... a personal search engine for those who want to find anything they've ever written in seconds ... a database manager for those who have things to keep track of ... a Hebrew, Greek, Cyrillic, IPA word processor for those who want more than just fonts ... a set of tools for scholars who want to focus on their writing and research ... a work of art for scholars who appreciate the finer things in life ... a community of scholars.
[Nota Bene's bibliographic facility is called 'Ibidem']
http://www.notabene.com

===ProCite===

ProCite is a Windows and Mac Bibliographic application similar in function to Endnotes and Reference Manager. The program can still be bought but no new software version have been made since 1999. [http://www.procite.com www.procite.com]

===Reference Manager===
Reference Manager is a comprehensive Bibliographic package with Bibliographic database, internet searching, and citation and bibliographic table formating. It is widely used at many professional organizations and universities.
The program has many important features for heavy users who do a lot of literature searching and keep many references in their databases. Version 11 now includes a web publisher which allows you to publish your databases and share your references with colleagues.
There also is a Network version of the program.

It has a downloadable collection of over 1200 citation styles. It saves bibliographic date in RIS format which is now a common data exchange format. [http://www.refman.com www.refman.com]

===Scholars Aid===

A commercial application that works with OpenOffice (on MS Windows). Note that there is also a free 'Lite' version. "Scholar's Aid keeps bibliographical data and notes together, for the very good reason that scholars always need to keep their notes linked to the sources from which those notes were made. Indeed, in academic writing, scholars constantly support their argument by reference to the sources on which they have worked. Thus, in directly quoting from one of these sources, or in making reference to another's ideas, rigorous academic scholarship demands accurate and detailed citation of those original sources.

Scholar's Aid automates this process in a manner that is entirely without precedent. Provided the original notes were written in the Notes module of Scholar's Aid, by selecting text and clicking the transfer button, the program transfers the selected text into the word-processed document and, at exactly the same time, inserts an appropriate citation into the document in a form (footnote, short footnote, endnote, short endnote and parenthetical reference) determined by the user. The program even includes the correct page number in the citation that it creates within the word-processed document. Scholar's Aid surely is the Reference Processor?". http://www.scholarsaid.com/

==Windows, Linux, other==

===Bibutils===

The bibutils program set interconverts between various bibliography formats using a common XML intermediate. For example, one can convert RIS-format files to Bibtex by doing two transformations: RIS->MODS->Bibtex. By using a common intermediate for N formats, only 2N programs are required and not N²-N. These programs operate on the command line and are styled after standard UNIX-like filters:

* bib2xml - convert bibtex to XML intermediate 
* copac2xml - convert COPAC format references to XML intermediate 
* end2xml - convert endnote to XML intermediate 
* isi2xml - convert ISI web of science to XML intermediate 
* med2xml - convert Pubmed XML references to XML intermediate 
* modsclean - a MODS to MODS converter for testing puposes mostly 
* ris2xml - convert RIS format to XML intermediate 
* xml2bib - convert XML intermediate into bibtex 
* xml2ris - convert XML intermediate into RIS format 
[http://www.scripps.edu/~cdputnam/software/bibutils/bibutils.html www.scripps.edu/~cdputnam/software/bibutils/bibutils.html]

===Bibus===

Bibus is a bibliographic database. It has been designed with OpenOffice.org in mind. The "ultimate" goal is to have an opensource bibliographic software that will allow easy formatting (and reformatting) of the bibliographic index in OpenOffice.org Writer.
Main Features
Compatible with two database engines: MySQL and SQLite.
Hierarchical organization of the references with user defined keys.
Drag & drop to easily organize references.

Designed for multiuser:
You can share the database between an "unlimited" number of users.
Each user will have its own classification.
Powerful and easy to use search engine.
Live queries, that is searches that will update when the database change (this is simply a saved SQL query).

On-line PubMed access.

Import PubMed (Medline) and EndNote/Refer records.
Connection to OpenOffice.org. You can insert references in an open OpenOffice.org text document and format the bibliography directly in Bibus.
Thanks to Python and wxWidgets, Bibus should work on most modern platform (GNU/linux with gtk; Windows; MacOS; etc...). Version 0.8 has been tested on GNU/linux and Windows2000. Note for Windows 98 users.

Foreign language support through Unicode and gettext. As of version 1.2, Bibus is available in English, French, Portuguese, German, Spanish and Chinese.
For more info see http://bibus-biblio.sourceforge.net/

===OpenOffice===

The [http://www.openoffice.org OpenOffice] word-processor 'Writer' includes basic bibliographic support. OpenOffice has a [http://bibliographic.openoffice.org bibliographic project] whose goal is to improve the bibliographic facilities.

===rtfbtx===
[http://www.dmst.aueb.gr/dds/sw/ports/rtfbtx/ rtfbtx] is a hacked collection of BibTeX styles for doing bibliographies with MS Word & BibTeX. It produces the bibliography in RTF format & uses bookmarks to link citations to it.

Christos tried using it with OpenOffice and it only works for the alpha style, since for the rest I'm supposed to link to the "paragraph number" of the bookmark and OO doesn't support such a thing.

===Zotero===

[http://www.zotero.org/ Zotero] [zoh-TAIR-oh] is a free, easy-to-use Firefox extension to help you collect, manage, and cite your research sources. It lives right where you do your work — in the web browser itself. Requires [http://en-us.www.mozilla.com/en-US/firefox/2.0/releasenotes/ Firefox version 2]. There is now a OpenOffice-Zotero [http://www.zotero.org/documentation/openoffice_integration extension/plug-in] to allow users to insert citations and Bibliographic tables into your documents.

===Bibwiki===

Bibwiki is a extension to MediaWiki to manage bibliographies. The bibliographies are stored in plain BibTeX files. In contrast to other programs, Bibwiki alters the bibliographic files directly. You don't need a seperate database.

Bibwiki adds a special page where you can add, import, edit and export bibliographic records. Together with Mediawiki it's very easy to organize your excerpts, memos, or annotations and link them to the bibliographic records.

Features:
* import from various sources: Ex Libris' Aleph, Amazon, ProQuest
* export list of references using BibTeX styles
* manage digital documents
* easy searching

Visit [http://www.plaschg.net/bibwiki Bibwiki's Homepage].

===Mendeley===
Mendeley Desktop is an bibliographic programm which has a working Openoffice 'Cite 'n Write' plugin working for the Windows variant. You will have to register at their site, which also enables you to see the cited works of other users of your particular branch and share your used citations with other interested users. It currently supports BibTex/LaTex, Endnote, RIS and PDF(for quick reference). You can also use it to check any citations on Google Scholar.

Visit [http://www.mendeley.com/ Mendeley's Homepage] for more information.

==LaTeX / BibTeX==

[http://www.latex-project.org/ LaTeX] is a high-quality typesetting system, with features designed for the production of technical and scientific documentation. LaTeX is (or was) the de facto standard for the communication and publication of scientific documents.

[http://www.bibtex.org BibTeX] is the bibliographic subsystem for LaTeX,it is a citation formating and a bibliographic database tool. BibTeX styles definition files are small programs written in an un-named programming language [[http://www.forth.org/ FORTH] like]. This make them almost impossible to utilise in other applications. On the other hand, its database format for bibliographical references is widely used and most other bibliographic applications can import and export that format. It looks like this -
<pre>
@INBOOK{chicago,
title = "The Chicago Manual of Style",
publisher = "University of Chicago Press"
edition = "Thirteenth",
year = 1982,
pages = "400--401",
key = "Chicago" }
@BOOK{texbook,
author = "Donald E. Knuth",
title= "The {{\TeX}book}",
publisher = "Addison-Wesley",
year = 1984 }
</pre>

===The Jurabib package===

Extended BibTeX citation support for the humanities and legal texts. [http://www.jurabib.org/ jurabib] is a package for the LaTeX typesetting system and supports citations used in the humanities and by German law students. This package enables automated citation with BIBTEX for legal studies and the humanities. In addition, the package provides commands for specifying editors in a commentary in a convenient way.

This package is no longer actively developed.

===The biblatex package===

Massively extended BibTeX citation support. [http://www.ctan.org/tex-archive/help/Catalogue/entries/biblatex.html biblatex] is a package for the LaTeX typesetting system and adds a lot of new fields which overcome most of BibTeX's traditional shortcomings (e.g. book authors, gender, original publication, titles of multipart publications etc.). Biblatex hands the complete control of the appearance of citations and bibliography over to LaTeX, the BibTeX program itself is only used for sorting. The result is much more control for the user in a properly documented language.

==Linux==

=== OpenOffice/KBibTex/LyX/oolatex ===

The current way to create a bibliography in OOo makes it too difficult to produce a nicely formatted bibliography (at least it's too difficult for me). After trying a lot of the other alternatives, I found a way that works for me using KBibTex to create a BibTex database, LyX to create a nicely formatted bibliography, and oolatex to produce an OpenOffice .odt version of the LyX bibliography. First, use KBibTex to create the database (with your choice of formatting sytle) and export a BibTex database. Then open LyX and add a BibTex database. You have to add citations in order for the bibliographic entries to appear in the References or Bibliography. Export this to a latex file (either pdflatex or plain). Then we need to compile the latex - this takes several passes to resolve all the references. If the latex file is named "newfile1.tex", then use the following steps:

<nowiki>
#Compiling Latex file with BibTex bibliography</nowiki>

<nowiki>#Takes several passes to resolve references</nowiki>

<nowiki>#Use LyX to create document, export to latex</nowiki>

''latex newfile1.tex''

''bibtex newfile1''

''latex newfile1.tex''

''latex newfile1.tex''

<nowiki># Now convert to .odt</nowiki>

''oolatex newfile1''

<nowiki># Open the .odt in OpenOffice</nowiki>

''openoffice.org-2.1 --writer newfile1.odt &
''

At this point you should have a nicely formatted bibliography that you can paste into your OpenOffice document. An OpenOffice bibliographic database has been created using a user-defined format (thanks to oolatex).

Alternatively, you can use latex2rtf to create an .rtf version of the bibliography and open this in OpenOffice. My experience, however, is that it is not as nicely formatted:

''latex2rtf newfile1''

But of course, you can output an .rtf directly from KBibTex.

I did try to get LyX to export the .odt directly and I could swear I had it working (adding a new file format and a new converter in the Tools | Preferences) but I couldn't repeat it. LyX came with a set up for creating the older .swx format file - but this didn't seem to work. But the manual method outlined above works consistently.

--[[User:Rabil|Rabil]] 19:35, 14 January 2007 (CET)

===Tellico===

The Tellico application is the first one I have come across that uses xslt to format Bibliographic reports / tables. This is interesting as this is the method that we have been proposing for OpenOffice Bibliographic application, but we have not had any examples until now. See http://www.periapsis.org/tellico/

''"Tellico is a KDE application for keeping track of your book collection, bibliographies, video collection, or music collection. Tellico allows you to enter your collection in a catalogue database, saving many different properties like title, author, etc. Two different views of your collection are shown. On the left, your entries are grouped together by any field you like, allowing you to see how many are in each group. On the right, the values of the fields are shown, allowing you to customize your view to show whichever fields are most important to you. On the bottom is the field editor, where you can enter the data."''

''The data is saved in XML format, which makes for easy parsing. Unless you modify the fields yourself, the data follows a simple and documented DTD. It will run on any platform which KDE supports, most commonly Linux. Tellico is licensed under the GNU General Public License, giving you the freedom to modify and distribute the source code."''

'''Capabilities'''

* Supports collections of books, bibliographic entries, videos, or music.
* Supports any number of user-defined fields, of eight different types: text, paragraph, list, checkbox, year, URL, and tables.
* Handles books with multiple authors, genres, keywords, etc.
* Automatically formats titles and names
* Supports collection searching and view filtering
* Sorts and groups collection by various properties
* Automatically validates ISBN
* Allows customizable output through XSLT
* Imports Bibtex, Bibtexml, and CSV
* Exports to Bibtex, Bibtexml, CSV, and HTML

===BibTeXML===

BibTeX as XML markup. Markup scheme; - A bibliography DTD and schema for XML that expresses the content model in BibTeX -- the bibliographic system for use with LaTeX, which is widely adopted by the scientific community. BibTeXML is shipped with tools to uptranslate native TeX-syntax BibTeX bibliographies to XML, and translating this into any markup scheme. Hence one is able to profit from both the existing BibTeX system and bibliographies as well as the presentation and transformation facilities offered by XML. Our goal is to maintain a strict BibTeX schema and develop (and collect!) conversion tools that will help you tag your bibliographic data in XML and save typing time, or export it to HTML, DocBook or native BibTeX syntax. http://bibtexml.sourceforge.net/

===BibML===

BibML is an XML markup language designed to contain bibliographic information, particularly as content exported in Bibtex and Refer notations. BibML also contains content types from DocBook's <bibliography>, and as such may be considered an integration of the three sources. The web page contains a useful 'BibML Element Comparison Table' comparing the attributes of BibML, Bibtex, docbook and refer. http://kmi.open.ac.uk/projects/ceryle/docs/NOTE-bibml.html

===BibX===

The intention of BibX -- begun by Taco Hoekwater to serve as the basis for his XML rewrite of the ConTeXt bib module -- is to be the XML equivalent to RIS and BibTeX, but to significantly improve on them. http://tex.aanhet.net/bibx Download the current DTD.
ISDN Search
"A distributed search portal of common sources of ISBN numbers, with permanent caching of results. To provide a open-source free interface for ISBN retrieval using HTML, SQL or XML to be independent of any toolkits or software." http://sourceforge.net/projects/isbnsearch/

===YAZ===

Z39.50 is the protocol used to query databases and library catalogues for bibliographic information.
YAZ is a C / C++ programmer's toolkit supporting the development of Z39.50v3 / SRW clients and servers. Sample clients and servers are included with the distribution, and documentation can be browsed from this page. (Also available for MAC OS X).
NEW: The latest version of YAZ supports SRW/SRU (over HTTP). The YAZ server operates as both a simple HTTP 1.1 server and Z39.50 target (on the same port). The current version of YAZ includes support for the industry standard ZOOM API for Z39.50. This API vastly simplifies the process of writing new clients using YAZ, and it reduces your dependency on any single toolkit. ZOOM can also operate as a SRW client. Read more about ZOOM in YAZ here. The software library compiles in Windows and Linux. There is also a demonstration client program - IRTCL (requires YAZ and Tcl/Tk libraries be installed) that can perform the reference searches. It does everything but save or export the results ! However it is good model of how to use the toolkit. [http://bibliographic.openoffice.org/irclient.jpeg Screen pic]. [http://www.indexdata.dk/yaz/ www.indexdata.dk/yaz/]

===RefDB===

RefDB is a reference database and bibliography tool for SGML, XML, and LaTeX/BibTeX documents. It allows users to share databases over a network. It is lightweight and portable to basically all platforms with a decent C compiler. And it's released under the GNU General Public License.
The citestylex DTD from RefDB defines bibliographic formatting styles, and v2 will be updated to support BibX when it is done
RefDB is currently known to build and run out of the tarball on at least these platforms: Linux FreeBSD NetBSD Solaris (using gcc) OSX/Darwin Windows+Cygwin
RefDB appears to be the only available tool to create HTML, PostScript, PDF, DVI, MIF, or RTF output from DocBook or TEI sources with fully formatted citations and bibliographies according to publisher's specifications (check out some examples). Additional document types can be easily added. Project Home Page [http://refdb.sourceforge.net refdb.sourceforge.net].

===Sixpack===

Sixpack is a graphical and command-line bibliography database manager written in Perl/Tk. It interacts with the supplied package 'bp', (see below) which can import and export from a number of formats including bibtex, endnote, medline, procite, and many others. It can download references directly off the Web, and open articles using external viewers. It can also interface with Emacs/XEmacs and Lyx [LaTeX with a GUI interface] . It also has instructions on how to interact with openoffice / [[StarOffice]] using cvs files and database import functions [I have used this]. There are also some experimental filters to export sixpack data to the OpenOffice Bibliographic Database - using CSV format - see the Bibliographic Project Document and Files pages. Sadly it is not being well maintained. Home Page - [http://sourceforge.net/projects/sixpack sourceforge.net/projects/sixpack]

===bp===

bp is a Perl library that is designed to:
Let you quickly make tools to access bibliographies
Let you quickly make tools to access bibliographies
Let you access multiple bibliography formats transparently
Let you convert between formats
Let you convert between character sets
Developer - My first goal when designing the package was only the first -- I had written a number of tools that accessed my BibTeX bibliographies, and I saw that I was reusing a lot of code. So I decided to make a generic package to access BibTeX bibliographies. About a year later I decided that it would be even better if the package could read multiple formats, and convert between them. The result is bp. Parts of the package are still missing (namely documentation, automatic format recognition, and a good set of utilities), but everything needed for a working system exists. Home Page - http://www.ecst.csuchico.edu/~jacobsd/bib/bp/index.html

===gBib===

gBib is a user-friendly Gnome BibTeX database browser and editor. It provides facilities for merging BibTeX files, managing key conflicts, and adding bibliographic citations in LyX. Home Page - http://gbib.seul.org

===Pybliographer===

Pybliographer is a tool for managing bibliographic databases. The application is based written in Python and has a text-based and a GTK GUI interface It supports several bibliography formats and can be used for searching, editing, reformatting, etc.. Due to its nature, it can be extended to many uses (generating HTML pages according to bibliographic searches, etc). Pybliographer has a class library structure that could allow other applications to make use of it's facilities. It might be possible to provide a link from this program to insert citations into OpenOffice. There are only a few citation styles defined so far. Home Page -
http://www.pybliographer.org

The Pybliographer developers are considering major enhancements to the application and have produced some planing documents which has very good discussion of bibliographic and user client program issues. They are well worth a look at - http://www.pybliographer.org/development

===Kaspaliste===

Kaspaliste is a literature and knowledge database. It handles all kinds of books, articles, journals, web pages etc. But the database goes beyond simply storing bibliographical information. There is the possibility to create annotated links between pieces of information (like the content of a book chapter) and to group the links in categories. It is based on KDE and uses the Postgres relational database. It is a promising project but currently does not have import or export functions other than a Bibtex export. There are no links to other programs such as OpenOffice. Last release 2004-05-12. http://kaspaliste.sourceforge.net/

==Web Applications==

===Aigaion===
Aigaion is a free, web-based platform for managing annotated bibliographies. It allows the user(s) to order publications in a self-chosen topic structure and offers an intuitive user interface. Aigaion is built on the [[Bibliographic_Software_and_Standards_Information#BibTeX |BibTeX]] format and has excellent BibTeX import and export facilities.

Features
* Multi-user facilities
* Intuitive user interface
* Easy management of publications and topics
* Create public or private notes on publications
* Import of the BibTeX and [http://www.refman.com/support/risformat_intro.asp RIS] ([[Bibliographic_Software_and_Standards_Information#Endnote |Endnote]], [[Bibliographic_Software_and_Standards_Information#Reference Manager |Reference Manager]]) format
* Export of BibTeX and RIS (RIS is under development) format
[http://aigaion.sourceforge.net/ Aigaion homepage]

===BibORB===
BibORB is a tool to manage bibliographies recorded in BibTeX format using a simple Web browser.

[http://biborb.glymn.net/doku.php?id=features BibORB homepage]

===Memento===
Memento is next generation of web based bibliographic software that goes beyond simple searching, storing, and exporting articles. It is one stop solution for students, researchers, scholars where they can manage their bibliography, create and share reports and network with professionals.
Features:
* Clean, simple Internet Explorer and Firefox compatible interface
* Memento constantly fetches articles from all the famous online journals and conference websites to keep it database upto date.
* Import articles in multiple format such bibtex, endnote, RIS, etc.
* Export articles in bibtex or Microsoft Word 2007 Bibliographic XML
* Write personal notes, or upload PDF related to an article
* Write publicly viewable comments related to an article
* Create reports, attach articles to report, and share reports with other users
* Explore other users with similar interest
* Create watch list for articles, authors, keywords and receive new articles in RSS feed

[http://findnwrite.com/memento Memento homepage]

===BiblioWeb===

BiblioWeb is a web enabled bibliographic software. All the basic functions of bibliographic software are delivered through web browser. A Web user can be assigned "Read" or "Write" privileges. Users with "Read" accounts can search, browse, display, and export bibliographic records. Users with "Write" accounts can add, edit, delete, import, even format document through web browser. BiblioWeb is the ideal solution for a research group to share a common bibliographic database on the Web. It also supports a threaded discussion forum. http://www.biblioscape.com/bibliohost.htm

===User::Blibrestez55/Books/Scientific Bibliographic Project 2015 OpenOffice.org Wiki===
A bibliographic/software and standards informative scientific database supports collections of ESL books & reading materials,bibliographic cd's.audio,videos & translated languages of scientific books in English,German,French, Italian,Spanish,Turkish,Japanese & other translations.
http://wiki.services.openoffice.org/wiki/User:Blibrestez55/books/Scientific_Bibliographic_Project_2015

[[Category:Bibliographic]]

===refbase===
http://refbase.sourceforge.net/

Refbase is a web-based, platform-independent, multi-user interface for managing scientific literature & citations.
Main [http://refbase.sourceforge.net/features.html features]:

* a clean and standardized interface that attempts to be as web standards compliant as possible
* a multitude of search options, including quick, simple, advanced as well as powerful SQL search options
* various display options:
** list view: offers customizable and sortable columns
** details view: shows all fields of a particular record
** cite view: displays record entries in a citation style chosen by the user
** print view: eases printing or copying of records
* search within results functionality which provides an easy way of refining your search query
* user-specific fields for personal keywords, notes, etc
* save any search query together with the current display settings
* automatic email announcements for newly added records
* dynamic RSS feeds for recently added/edited records as well as for any custom user query
* [http://wiki.refbase.net/index.php/Importing_Records batch import] of records from various common bibliographic formats and online databases
* export records to MODS XML, Endnote, RIS or BibTeX (via bibutils)
* export to an OpenDocument spreadsheet for use with the current OO.o bibliographic manager
* link records to other records in the database (using static or dynamic links)
* extract literature cited within a text and build an appropriate reference list
* [http://wiki.refbase.net/index.php/Search/Retrieve_web_services Search & retrieve via URL (SRU)] web service
* COinS and unAPI

===RefWorks===

Was founded in 2001 by a team of developers (former Reference Manager developers) in the field of bibliographic database management. RefWorks is a '''web-based''', very flexible, research management, writing and collaboration tool. RefWorks allows users to create personal databases and use them for a variety of research activities. References are quickly and easily imported from text files or online databases. The databases can then be used to manage, store, and share the information. Users can automatically insert references from their database into their papers and generate formatted bibliographies and manuscripts in seconds. http://www.refworks.com/content/products/faqs.asp

Site licenses for organizations are available. Individual licenses are also available. RefWorks supports hundreds of online databases and output styles covering a broad range of subject areas. http://www.refworks.com/

===WIKINDX===

WIKINDX is a free bibliographic and quotations/notes management and article authoring system designed either for single use (on a variety of operating sytems) or multi-user collaborative use across the internet.

[http://wikindx.sourceforge.net/features.html Features]:

* 36 resource types.
* Multi-user mode - create and manage your own bibliographies drawn from the WIKINDX master bibliography and browse other users' bibliographies. (Must be enabled by the administrator.)
* Save your own preferences.
* Enter/edit bibliographic resources.
* Add unlimited file attachments to each resource. (Must be enabled by the administrator.)
* Catalogue resources by categories and keyword(s).
* Enter/edit a general note about the whole resource.
* Enter/edit quotes and paraphrases from those resources.
* Enter/edit thoughts or musings on various aspects of a resource (can be private or public).
* Add keywords to resource metadata such as quotes, paraphrases and musings.
* Use BBCode in all textarea input.
* Cross-reference other WIKINDX resources from within quotes, paraphrases, musings, notes and abstracts.
* Edit keywords, creators, publishers and journals.
* Comprehensive search across all the above with highlighting of search terms using either Quick Search or Power Search.
* Reorder bibliographic lists by first creator, title, resource type, publisher, year of publication timestamp, popularity index or maturity index.
* Select resources by category, keywords, creator, publisher etc.
* Browse all creators, publishers, collections, categories and keywords with font colour and size indicating frequency of occurrence (tag clouds).
* Unlimited primary creators, editors, translators and revisers, composers, agents, performers etc.
* Export bibliographic lists (optionally annotated) with a range of formatting options to RTF (Rich Text Format) files for easy insert into word processors.
* Export bibliographic lists to RIS for import to Endnote, Reference Manager, ProCite etc.
* Export an Endnote tabbed textfile.
* Export an Endnote XML file.
* Export bibliographic lists to BibTeX format.
* Import Endnote XML and bibTeX files.
* Cut 'n' Paste BibTeX entries to the database (amount limited by the administrator).
* View and export in seven bibliographic styles: Chicago, MLA, APA and Harvard, Turabian, British Medical Journal and IEEE. Administrators can copy, edit and create bibliographic styles through the web browser interface.
* Write an article entirely within WIKINDX importing quotes etc. and chose the citation formatting prior to exporting the article to RTF (can be opened in external word processors including OpenOffice).
* Run WIKINDX in core English or other languages (depending on administrator-installed language plug-ins).
* User-defined paging of long bibliographic lists.
* View all quotes, paraphrases and musings or a single random one.
* One-click return to last bibliographic list or single view.
* Store up to 10 bookmarks for quick return to single views.
* Select a visual style.
* WIKINDX has an architecture which enables either in-line or menu plug-ins to be inserted. Write your own or download plug-ins from the sourceforge site.
http://wikindx.sourceforge.net/

===literaturedb===
http://www.literaturedb.com

literaturedb is a bibliographic management software that can help you organize your literature and bibliographic references for scientific documents. It runs as a PHP web site and provides a collaborative space for storing and sharing documents and references.

Main [http://www.literaturedb.com features]:

* Simplicity: You can find all options on just four pages.
* Bibtex: It uses Bibtex entry types and fields so you can reuse references.
* Full text: It stores full text files (pdf, doc, etc.) for quick access.
* Exports: Export to Word, Bibtex, Endnote, MODS and RIS.
* Collaboration: You can share documents in your team and with friends.
* Tagging: You can tag every document with keywords.
* Search function: The search function scans all data entry fields.
* LDAP support: You can reuse the user management of your organization.
* FLOSS: It is free and open source (GPL).

===Contents-Linking===

http://www.multisuchsystem.de/contents.html

Contents-Linking as part of the Multisuchsystem E-Connect [http://www.multisuchsystem.de/]by Hans Hehl is a free webbed-based tool of managing and searching bibliographic records. It is also a linking system, which aims to go most directly to the full text of an article.
It is built only on simple HTML and Javascipt, but able to import at once hundreds of bibliographic records from any of the databases, so a database of own interest can rapidly be created.
Contents-Linking is connected with a knowledge base, which consists of ca. 50000 journal titles supplemented by subject terms and informations about library holdings.

'''Features'''
*Searching articles by terms or strings
*Searching articles by subject terms, alphabetically or by subjects
*Browsing ca. 13000 records in parts of 1000
*Displayed records are linked with the full-linked record
*Browsing ca 4600 journal titles of Contents-database
*Displayed journal titles are linked with full-linked records corresponding to these
*Full-linked records are linked with EZB, ZDB, Google Scholar, Google and library holdings
*Contents-Linking may be installed for any library participating in the EZB
*Importing new records from the following databases: JADE Database, TIBOrder, Current Contents, British Library Direct, PubMed,IngentaConnect, FirstSearch, OVIDSearch, RefDoc, Google Scholar
*Creating a new import filter for another database

http://www.multisuchsystem.de/contents.html

[[Category:Bibliographic|Standards]]
[[Category: Marketing]]
[[Category:Screenshot
[[Category:Art]]
[[Category:Documentation]]

User:Blibrestez55/Books/Statistics/Multivariate Data Analysis Research Project

2012-08-18T15:02:59Z

Blibrestez55: Created page with "{{saved_book}} ;Burundi_Librestez Statistics Research Metatheory Studies Project Apache OpenOffice Wiki ;Burundi_Librestez Descriptive Statistics Research Project-Apache OpenOf…"

{{saved_book}}

;Burundi_Librestez Statistics Research Metatheory Studies Project Apache OpenOffice Wiki
;Burundi_Librestez Descriptive Statistics Research Project-Apache OpenOffice Wiki
:[[Category:Calc]]
:[[Category:Community Council]]
:[[Category:Database]]
:[[Category:Development]]
:[[Category:Documentation]]
:[[Category:Impress]]
:[[Category:MainIndex]]
:[[Category:Marketing]]
:[[Category:NLC]]
:[[Category:Project]]
:[[Category:Term]]
:[[Category:Wiki]]
:[[Community Council/Meeting Guidelines]]
:[[Documentation]]
:[[Main Page]]
:[[Major OpenOffice.org Deployments]]
:[[Market Share Analysis]]
:[[Special:WhatLinksHere]]
:[[User:Blibrestez55/Books/Dokumentation Tos/Calc:/Statistics Project2015]]
:[[User:Blibrestez55/Books/Wiki:Copyrights]]
:[[Wiki/statistics]]
:[[Writer]]
:[[Special:Book]]

[[Category:Books|Multivariate Data Analysis Research Project]]

User:Blibrestez55

2012-08-12T21:11:02Z

Blibrestez55: *Burundi_Librestez54 Autobiography-Apache OpenOffice.org Wiki

<http://wiki.services.openoffice.org/wiki/User:Blibrestez55/Books/BLibrestez55/Biography

Copyright (©)
[2007] [Burundi_Librestez54]

Licensed under the Apache License, Version 1.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-1.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

<?xml version="1.0" ?>
- 
- <rdf:RDF xml:lang="en" xmlns="http://usefulinc.com/ns/doap#" xmlns:rdf="http://www.w3.org/2010/09/13-rdf-syntax-ns#" xmlns:asfext="http://projects.apache.org/ns/asfext#" xmlns:foaf="http://xmlns.com/foaf/0.1/">
- <Project rdf:about="http://xmlgraphics.apache.org/commons/">
<created>2010-09-13</created>
<license rdf:resource="http://usefulinc.com/doap/licenses/asl20" />
<name>Apache XML Graphics Commons</name>
<homepage rdf:resource="http://xmlgraphics.apache.org/commons/" />
<asfext:pmc rdf:resource="http://xmlgraphics.apache.org" />
<shortdesc>Common components for Apache Batik and Apache FOP</shortdesc>
<description>Apache XML Graphics Commons is a library that consists of several reusable components used by Apache Batik and Apache FOP. Many of these components can easily be used separately outside the domains of SVG and XSL-FO. You will find components such as a PDF library, an RTF library, Graphics2D implementations that let you generate PDF and PostScript files and much more.</description>
<mailing-list rdf:resource="http://xmlgraphics.apache.org/mail.html" />
<download-page rdf:resource="http://xmlgraphics.apache.org/commons/download.html" />
<programming-language>Java</programming-language>
<category rdf:resource="http://projects.apache.org/category/graphics" />
- <asfext:implements>
- <asfext:Standard>
<asfext:title>PostScript</asfext:title>
<asfext:body>Adobe Systems Incorporated</asfext:body>
<asfext:id>PS</asfext:id>
<asfext:url rdf:resource="http://partners.adobe.com/public/developer/ps/index_specs.html" />
</asfext:Standard>
</asfext:implements>
- <asfext:implements>
- <asfext:Standard>
<asfext:title>Extensible Metadata Platform (XMP)</asfext:title>
<asfext:body>Adobe Systems Incorporated</asfext:body>
<asfext:id>XMP</asfext:id>
<asfext:url rdf:resource="http://www.adobe.com/products/xmp/index.html" />
</asfext:Standard>
</asfext:implements>
- <release>
- <Version>
<name>Latest release (stable)</name>
<created>2010-09-13</created>
<revision>1.4</revision>
</Version>
- <Version>
<name>Previous release (stable)</name>
<created>2010-09-13</created>
<revision>1.3.1</revision>
</Version>
- <Version>
<name>Previous release (stable)</name>
<created>2010-09-13</created>
<revision>1.3</revision>
</Version>
- <Version>
<name>Previous release (stable)</name>
<created>2010-09-13</created>
<revision>1.2</revision>
</Version>
- <Version>
<name>Previous release (stable)</name>
<created>2010-09-13</created>
<revision>1.1</revision>
</Version>
- <Version>
<name>Previous release (stable)</name>
<created>2010-09-13</created>
<revision>1.0</revision>
</Version>
</release>
- <repository>
- <SVNRepository>
<location rdf:resource="http://svn.apache.org/repos/asf/xmlgraphics/commons/trunk/" />
<browse rdf:resource="http://svn.apache.org/viewcvs.cgi/xmlgraphics/commons/trunk/" />
</SVNRepository>
</repository>
- <maintainer>
- <foaf:Person>
<foaf:name>Blibrestez55</foaf:name>
<foaf:mbox rdf:resource="mailto:duchess_bmjb" />

</foaf:Person>
</maintainer>
</Project>
</rdf:RDF>

Copyright © 2011 a55dayidream GNU GPL Translation Project. <http://translatewiki.net/wiki/User:A55dayidream>

=======================================================================
-->

- <Project rdf:about=http://incubator.apache.org/projects/aries.html>

<created>2010-18-10</created>

<license rdf:resource="http://usefulinc.com/doap/licenses/asl20" />

<name>Apache Libra (incubating)</name>

<homepage rdf:resource="" > https://incubator.apache.org/libra/

<asfext:pmc rdf:resource="http://incubator.apache.org" />

<shortdesc>OSGi Enterprise Programming Model</shortdesc>

<description>The Libra project is delivering a set of pluggable Java components enabling an enterprise OSGi application programming model. This includes implementations and extensions of application-focused specifications defined by the OSGi Alliance Enterprise Expert Group (EEG) and an assembly format for multi-bundle applications, for deployment to a variety of OSGi based runtimes.</description>

<bug-database rdf:resource=http://issues.apache.org/jira/browse/LIBRA />

<mailing-list rdf:resource=http://incubator.apache.org/libra/mailinglists.html />

<download-page rdf:resource=http://incubator.apache.org/libra/ />

<programming-language>Java</programming-language>

<category rdf:resource="http://projects.apache.org/category/library" />

- <repository>

- <SVNRepository>

<location rdf:resource=https://svn.apache.org/repos/asf/incubator/libra/ />

<browse rdf:resource=http://svn.apache.org/viewvc/incubator/libra/ />
</SVNRepository>
</repository>

- <maintainer>

- <foaf:Person>a55dayidream

<foaf:name>a55dayidream</foaf:name>

<foaf:mbox rdf:resource=mailto:a55dayidream@apache.org />
</foaf:Person>a55dayidream
</maintainer>

- <asfext:implements>

- <asfext:Standard>

<asfext:title>Blueprint Container Specification 1.0</asfext:title>

<asfext:body>OSGi Alliance</asfext:body>

<asfext:id>Enterprise 121</asfext:id>

<asfext:url rdf:resource="http://www.osgi.org/Download/Release4V42" />
</asfext:Standard>
</asfext:implements>

- <asfext:implements>

- <asfext:Standard>

<asfext:title>JNDI Services Specification 1.0</asfext:title>

<asfext:body>OSGi Alliance</asfext:body>

<asfext:id>Enterprise 126</asfext:id>

<asfext:url rdf:resource="http://www.osgi.org/Download/Release4V42" />
</asfext:Standard>
</asfext:implements>

- <asfext:implements>

- <asfext:Standard>

<asfext:title>JPA Service Specification 1.0</asfext:title>

<asfext:body>OSGi Alliance</asfext:body>

<asfext:id>Enterprise 127</asfext:id>

<asfext:url rdf:resource="http://www.osgi.org/Download/Release4V42" />
</asfext:Standard>
</asfext:implements>

- <asfext:implements>

- <asfext:Standard>

<asfext:title>JTA Transaction Services Specification 1.0</asfext:title>

<asfext:body>OSGi Alliance</asfext:body>

<asfext:id>Enterprise 123</asfext:id>

<asfext:url rdf:resource="http://www.osgi.org/Download/Release4V42" />
</asfext:Standard>
</asfext:implements>
- <asfext:title>Blueprint Container Specification 1.0</asfext:title>
<release>
<Version>
<name>Latest Incubator release</name>
<created>2010-10-18</created>
<revision>0.1-incubating</revision>
</Version>
</release>
-->
</Project>
</rdf:RDF>

Categories: [Apache Project] [Libra Project]

Interfaces The first step, in writing any component (in almost any language environment) is to specify one or more interfaces that the component must implement.

Interfaces are the key to hiding implementation details in any modern development environment. They are contracts between a client that wants to use a components' functionality and the component (serving this functionality). In UNO terminology, UNO components are called services.

Interfaces separate the specific implementation (there can more than one for a service) from the usage. The client using the component does not have any insight how the component is implemented.

Interfaces are specified using an Interface definition language (IDL). UNO uses UNO-IDL as the interface definition language. An interface for a Counter might look like this:

file counter.idl:

#include <com/sun/star/uno/XInterface.idl>
module foo
{
/**
* Interface to count things.
*/
[ uik(3806AFF0-75A0-11d3-87B300A0-24494732), ident("XCountable", 1.0) ]
interface XCountable : com::sun::star::uno::XInterface
{
long getCount();
void setCount( [in] long nCount );
long increment();
long decrement();
};
};
Any interface that is specified is derived from XInterface, the basic interface in UNO. The XInterface has methods for lifetime control of the interface (acquire() and release()) and the ability to query for further interfaces of the UNO object (queryInterface()). Once you have an interface of an object, you can query for any others the object provides. If there are no acquired interfaces (references) left on an UNO object, the object might disappear. Interfaces (and services) can be grouped in modules to avoid pollution of the global namespace.

Services Any UNO component (service) exports one or more interfaces that the clients are using. All services are specified using the service directive in an IDL file:

module foo

{
service Counter
{
// exported interfaces:
interface XCountable;
};
};
The service declaration introduces a service called foo.Counter which supports the XCountable interface.

There are some more IDL features, e.g. attributes, structs, enums, that are omitted at this time. All IDL declarations are put into a typelibrary file (rdb file). This speeds up the back end generation of the language specific files.

To implement the interfaces, the appropriate interface code for the implementation language has to be generated from the rdb file.

In C++ a tool called cppumaker generates pure abstract classes that the component has to implement. This is a common way to describe interfaces in C++. The Java language directly supports interfaces as a language feature (javamaker will generate Java interfaces).

Implementation A component that is implemented in C++ is normally packaged in a shared library. This shared lib exports two symbols, which are explained further below. Java implementations are normally packaged in a JAR file. In this case the manifest file identifies a class implementing two methods with similar semantics.

A simple implementation of the counting UNO service foo.Counter might be:

file foo.cxx:

#include <rtl/ustring.hxx>
#include <cppuhelper/implbase1.hxx>
#include <cppuhelper/factory.hxx>
#include <com/sun/star/lang/XSingleServiceFactory.hpp>
#include <com/sun/star/lang/XMultiServiceFactory.hpp>
#include <com/sun/star/registry/XRegistryKey.hpp>
#include <foo/XCountable.hpp>

using namespace rtl;
using namespace com::sun::star::uno;
using namespace com::sun::star::lang;
using namespace com::sun::star::registry;
using namespace foo;

//==================================================================================================
class MyCounterImpl : public cppu::WeakImplHelper1< XCountable >
{
// to obtain other services if needed
Reference< XMultiServiceFactory > _xServiceManager;

sal_Int32 _nCount;

Reference< XText > _xText;
void dump( sal_Int32 nValue ) const;

public:
MyCounterImpl( const Reference< XMultiServiceFactory > & xServiceManager );
virtual ~MyCounterImpl();

// XCountable implementation
virtual sal_Int32 SAL_CALL getCount() throw (RuntimeException);
virtual void SAL_CALL setCount( sal_Int32 nCount ) throw (RuntimeException);
virtual sal_Int32 SAL_CALL increment() throw (RuntimeException);
virtual sal_Int32 SAL_CALL decrement() throw (RuntimeException);
};
//__________________________________________________________________________________________________
MyCounterImpl::MyCounterImpl( const Reference< XMultiServiceFactory > & xServiceManager )
: _xServiceManager( xServiceManager )
{
cerr << "< MyCounterImpl ctor called >" << endl;

if (_xServiceManager.is())
{
Reference< XComponentLoader > xLoader( _xServiceManager->createInstance(
L"com.sun.star.frame.Desktop" ), UNO_QUERY );
if (xLoader.is())
{
Reference< XTextDocument > xDoc( xLoader->loadComponentFromURL(
L"private:scalc/factory", L"_blank", 0, Sequence< PropertyValue >() ), UNO_QUERY );
if (xDoc.is())
_xText = xTextDoc->getText();
}
}
}
//__________________________________________________________________________________________________
MyCounterImpl::~MyCounterImpl()
{
cerr << "< MyCounterImpl dtor called >" << endl;
}
//__________________________________________________________________________________________________
void MyCounterImpl::dump( sal_Int32 nValue ) const
{
if (_xText.is())
_xText->setValue( nValue );
else
cerr << endl << nValue;
}

// XCountable implementation
//__________________________________________________________________________________________________
sal_Int32 MyCounterImpl::getCount() throw (RuntimeException)
{
return _nCount;
}
//__________________________________________________________________________________________________
void MyCounterImpl::setCount( sal_Int32 nCount ) throw (RuntimeException)
{
_nCount = nCount;
dump( _nCount );
}
//__________________________________________________________________________________________________
sal_Int32 MyCounterImpl::increment() throw (RuntimeException)
{
++_nCount;
dump( _nCount );
return _nCount;
}
//__________________________________________________________________________________________________
sal_Int32 MyCounterImpl::decrement() throw (RuntimeException)
{
--_nCount;
dump( _nCount );
return _nCount;
}

/**
* Function to create a new component instance; is needed by factory helper implementation.
* @param xMgr service manager to if the components needs other component instances
*/
Reference< XInterface > MyCounterImpl_create(
const Reference< XMultiServiceFactory > & xMgr )
{
return Reference< XInterface >( new MyCounterImpl( xMgr ) );
}
The generated header file declares an abstract C++ class and a function called getCppuType(). Any generated type has its getCppuType() describing the type, for example.

const com::sun::star::uno::Type & SAL_CALL getCppuType( const com::sun::star::uno::Reference< foo::XCountable > * );
describes the XCountable interface. Only the type of the parameter is of importance. By using overloaded getCppuType() functions for any type, it is possible to get runtime type information. It is also possible to use little helpers like a template queryInterface() function used for the implementation of XInterface::queryInterface().

So how is the UNO component instantiated? As mentioned above, four symbols are exported by the shared library, providing four functions: component_getDescriptionFunc(), component_getImplementationEnvironment(), component_writeInfo() and component_getFactory().

The first is called to get a description of the component. This function returns a XML formatted string which describes the component. This function could be generated from the XML description with the xml2cmp tool. Each component should provide such a XML description. The second is called from a loader service to get information about the used environment of the component. The third is called whenever the component is registered in some registry file and the latter is called to obtain a factory to get instances of the component.

They are typically implemented as follows:

/**
* This function returns the name of the used environment.
* @param ppEnvTypeName name of the environment
* @param ppEnv could be point to a special environment, this parameter is normally set to null
*/
extern "C" void SAL_CALL component_getImplementationEnvironment(
const sal_Char ** ppEnvTypeName, uno_Environment ** ppEnv )
{
*ppEnvTypeName = CPPU_CURRENT_LANGUAGE_BINDING_NAME;
}

/**
* This function creates an implementation section in the registry and another subkey
* for each supported service.
* @param pServiceManager generic uno interface providing a service manager
* @param pRegistryKey generic uno interface providing registry key to write
*/
extern "C" sal_Bool SAL_CALL component_writeInfo( void* pServiceManager, void* pRegistryKey )
{
if (pRegistryKey)
{
try
{
Reference< XRegistryKey > xNewKey(
reinterpret_cast< XRegistryKey * >( pRegistryKey )->createKey(
OUString( RTL_CONSTASCII_USTRINGPARAM("/foo.MyCounterImpl/UNO/SERVICES") ) ) );
xNewKey->createKey( OUString( RTL_CONSTASCII_USTRINGPARAM("foo.Counter") ) );
return sal_True;
}
}
return sal_False;
}
component_writeInfo() will write information about all service implementations that are in the shared library. Each service implementation is registered under its implementation name in the implementation section, followed by its service name. The hierarchical structure of the registry is as follows:

/IMPLEMENTATIONS/
/foo.MyCounterImpl // implementation name Blibrestez55
/UNO
/SERVICES
/foo.Counter // service name Blibrestez55
/bar.AnotherCounterImpl // implementation name Blibrestez55
/UNO
/SERVICES
/foo.Counter // service name Blibrestez55
...
/**
* Function to create a new component instance; is needed by factory helper implementation.
* @param xMgr service manager to if the components needs other component instances
*/
Reference< XInterface > MyCounterImpl_create( const Reference< XMultiServiceFactory > & xMgr )
{
return Reference< XInterface >( new MyCounterImpl( xMgr ) );
}

/**
* This function is called to get service factories for an implementation.
* @param BLibrestez55 name of implementation
* @param pServiceManager generic uno interface providing a service manager to instantiate components
* @param pRegistryKey registry data key to read and write component persistent data
* @return a component factory (generic uno interface)
*/
extern "C" void * SAL_CALL component_getFactory(
const sal_Char * Blibrestez55, void * pServiceManager, void * pRegistryKey )
{
void * pRet = 0;
// which implementation is required?
if (pServiceManager && rtl_str_compare( pImplName, "foo.MyCounterImpl" ))
{
rtl::OUString BLibrestez55( RTL_CONSTASCII_USTRINGPARAM("foo.Counter") );
Reference< XSingleServiceFactory > xFactory(
cppu::createSingleFactory( // helper function from cppuhelper lib
reinterpret_cast< XMultiServiceFactory * >( pServiceManager ),
OUString( RTL_CONSTASCII_USTRINGPARAM("foo.MyCounterImpl") ),
MyCounterImpl_create,
Sequence< rtl::OUString >( &BLIbrestez55, 1 ) ) );
if (xFactory.is())
{
xFactory.acquire();
pRet = xFactory.get();
}
}
return pRet;
}
component_getFactory() demands a certain implementation from the shared library. The returned uno interface is a component factory that is used to produce service instances of the component implementation. The first parameter identifies the name of the required implementation. This name must correspond to the registered one from component_writeInfo(). The second parameter provides a service manager instance, components can use this for getting further components. The last parameter provides a registry key to the implementation section of the component, so it can read and write persistent data to the registry, e.g. for booting.

Author: BLibrestez55 ($Date: 2011/09/22 18:57:00 $)
Copyright 2011 http://en.wikibooks.org/wiki/User_talk:Jerusalem2020 USA.

*Certification modules about the different components of the certification topics.
*Certification Material, includes the trainer's manual, student manual and quizzes. learn more
*a development category to provide a central node for the development of OpenOffice.org by students, either working alone or in a class.**a tools category where you'll find listed several tools available through OpenOffice.org usage or along it. They will be provided in the language they exist
Most of our actions and discussions will take place on mailing lists, but you will find also several working places in the Document & Files area or on the wiki pages.
Join us on the :

*users@education.openoffice.org mailing list if you have any idea to discuss about this project or general informations to communicate with us.

[[Category: CC-BY License]]

[[Category: Documentation/Developer's Guide]]

[[Category:Documentation]]

[[Category:Education]]

[[Category:Project]]

User:Blibrestez55

2012-08-12T20:48:41Z

Blibrestez55: *Burundi_Librestez54 Autobiography-Apache OpenOffice.org Wiki

<http://wiki.services.openoffice.org/wiki/User:Blibrestez55/Books/BLibrestez55/Biography

Copyright (©)
[2007] [Burundi_Librestez54]

Licensed under the Apache License, Version 1.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-1.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

<?xml version="1.0" ?>
- 
- <rdf:RDF xml:lang="en" xmlns="http://usefulinc.com/ns/doap#" xmlns:rdf="http://www.w3.org/2010/09/13-rdf-syntax-ns#" xmlns:asfext="http://projects.apache.org/ns/asfext#" xmlns:foaf="http://xmlns.com/foaf/0.1/">
- <Project rdf:about="http://xmlgraphics.apache.org/commons/">
<created>2010-09-13</created>
<license rdf:resource="http://usefulinc.com/doap/licenses/asl20" />
<name>Apache XML Graphics Commons</name>
<homepage rdf:resource="http://xmlgraphics.apache.org/commons/" />
<asfext:pmc rdf:resource="http://xmlgraphics.apache.org" />
<shortdesc>Common components for Apache Batik and Apache FOP</shortdesc>
<description>Apache XML Graphics Commons is a library that consists of several reusable components used by Apache Batik and Apache FOP. Many of these components can easily be used separately outside the domains of SVG and XSL-FO. You will find components such as a PDF library, an RTF library, Graphics2D implementations that let you generate PDF and PostScript files and much more.</description>
<mailing-list rdf:resource="http://xmlgraphics.apache.org/mail.html" />
<download-page rdf:resource="http://xmlgraphics.apache.org/commons/download.html" />
<programming-language>Java</programming-language>
<category rdf:resource="http://projects.apache.org/category/graphics" />
- <asfext:implements>
- <asfext:Standard>
<asfext:title>PostScript</asfext:title>
<asfext:body>Adobe Systems Incorporated</asfext:body>
<asfext:id>PS</asfext:id>
<asfext:url rdf:resource="http://partners.adobe.com/public/developer/ps/index_specs.html" />
</asfext:Standard>
</asfext:implements>
- <asfext:implements>
- <asfext:Standard>
<asfext:title>Extensible Metadata Platform (XMP)</asfext:title>
<asfext:body>Adobe Systems Incorporated</asfext:body>
<asfext:id>XMP</asfext:id>
<asfext:url rdf:resource="http://www.adobe.com/products/xmp/index.html" />
</asfext:Standard>
</asfext:implements>
- <release>
- <Version>
<name>Latest release (stable)</name>
<created>2010-09-13</created>
<revision>1.4</revision>
</Version>
- <Version>
<name>Previous release (stable)</name>
<created>2010-09-13</created>
<revision>1.3.1</revision>
</Version>
- <Version>
<name>Previous release (stable)</name>
<created>2010-09-13</created>
<revision>1.3</revision>
</Version>
- <Version>
<name>Previous release (stable)</name>
<created>2010-09-13</created>
<revision>1.2</revision>
</Version>
- <Version>
<name>Previous release (stable)</name>
<created>2010-09-13</created>
<revision>1.1</revision>
</Version>
- <Version>
<name>Previous release (stable)</name>
<created>2010-09-13</created>
<revision>1.0</revision>
</Version>
</release>
- <repository>
- <SVNRepository>
<location rdf:resource="http://svn.apache.org/repos/asf/xmlgraphics/commons/trunk/" />
<browse rdf:resource="http://svn.apache.org/viewcvs.cgi/xmlgraphics/commons/trunk/" />
</SVNRepository>
</repository>
- <maintainer>
- <foaf:Person>
<foaf:name>Blibrestez55</foaf:name>
<foaf:mbox rdf:resource="mailto:duchess_bmjb" />

</foaf:Person>
</maintainer>
</Project>
</rdf:RDF>

Copyright © 2011 a55dayidream GNU GPL Translation Project. <http://translatewiki.net/wiki/User:A55dayidream>

=======================================================================
-->

- <Project rdf:about=http://incubator.apache.org/projects/aries.html>

<created>2010-18-10</created>

<license rdf:resource="http://usefulinc.com/doap/licenses/asl20" />

<name>Apache Libra (incubating)</name>

<homepage rdf:resource="" > https://incubator.apache.org/libra/

<asfext:pmc rdf:resource="http://incubator.apache.org" />

<shortdesc>OSGi Enterprise Programming Model</shortdesc>

<description>The Libra project is delivering a set of pluggable Java components enabling an enterprise OSGi application programming model. This includes implementations and extensions of application-focused specifications defined by the OSGi Alliance Enterprise Expert Group (EEG) and an assembly format for multi-bundle applications, for deployment to a variety of OSGi based runtimes.</description>

<bug-database rdf:resource=http://issues.apache.org/jira/browse/LIBRA />

<mailing-list rdf:resource=http://incubator.apache.org/libra/mailinglists.html />

<download-page rdf:resource=http://incubator.apache.org/libra/ />

<programming-language>Java</programming-language>

<category rdf:resource="http://projects.apache.org/category/library" />

- <repository>

- <SVNRepository>

<location rdf:resource=https://svn.apache.org/repos/asf/incubator/libra/ />

<browse rdf:resource=http://svn.apache.org/viewvc/incubator/libra/ />
</SVNRepository>
</repository>

- <maintainer>

- <foaf:Person>a55dayidream

<foaf:name>a55dayidream</foaf:name>

<foaf:mbox rdf:resource=mailto:a55dayidream@apache.org />
</foaf:Person>a55dayidream
</maintainer>

- <asfext:implements>

- <asfext:Standard>

<asfext:title>Blueprint Container Specification 1.0</asfext:title>

<asfext:body>OSGi Alliance</asfext:body>

<asfext:id>Enterprise 121</asfext:id>

<asfext:url rdf:resource="http://www.osgi.org/Download/Release4V42" />
</asfext:Standard>
</asfext:implements>

- <asfext:implements>

- <asfext:Standard>

<asfext:title>JNDI Services Specification 1.0</asfext:title>

<asfext:body>OSGi Alliance</asfext:body>

<asfext:id>Enterprise 126</asfext:id>

<asfext:url rdf:resource="http://www.osgi.org/Download/Release4V42" />
</asfext:Standard>
</asfext:implements>

- <asfext:implements>

- <asfext:Standard>

<asfext:title>JPA Service Specification 1.0</asfext:title>

<asfext:body>OSGi Alliance</asfext:body>

<asfext:id>Enterprise 127</asfext:id>

<asfext:url rdf:resource="http://www.osgi.org/Download/Release4V42" />
</asfext:Standard>
</asfext:implements>

- <asfext:implements>

- <asfext:Standard>

<asfext:title>JTA Transaction Services Specification 1.0</asfext:title>

<asfext:body>OSGi Alliance</asfext:body>

<asfext:id>Enterprise 123</asfext:id>

<asfext:url rdf:resource="http://www.osgi.org/Download/Release4V42" />
</asfext:Standard>
</asfext:implements>
- <asfext:title>Blueprint Container Specification 1.0</asfext:title>
<release>
<Version>
<name>Latest Incubator release</name>
<created>2010-10-18</created>
<revision>0.1-incubating</revision>
</Version>
</release>
-->
</Project>
</rdf:RDF>

Categories: [Apache Project] [Libra Project]

Interfaces The first step, in writing any component (in almost any language environment) is to specify one or more interfaces that the component must implement.

Interfaces are the key to hiding implementation details in any modern development environment. They are contracts between a client that wants to use a components' functionality and the component (serving this functionality). In UNO terminology, UNO components are called services.

Interfaces separate the specific implementation (there can more than one for a service) from the usage. The client using the component does not have any insight how the component is implemented.

Interfaces are specified using an Interface definition language (IDL). UNO uses UNO-IDL as the interface definition language. An interface for a Counter might look like this:

file counter.idl:

#include <com/sun/star/uno/XInterface.idl>
module foo
{
/**
* Interface to count things.
*/
[ uik(3806AFF0-75A0-11d3-87B300A0-24494732), ident("XCountable", 1.0) ]
interface XCountable : com::sun::star::uno::XInterface
{
long getCount();
void setCount( [in] long nCount );
long increment();
long decrement();
};
};
Any interface that is specified is derived from XInterface, the basic interface in UNO. The XInterface has methods for lifetime control of the interface (acquire() and release()) and the ability to query for further interfaces of the UNO object (queryInterface()). Once you have an interface of an object, you can query for any others the object provides. If there are no acquired interfaces (references) left on an UNO object, the object might disappear. Interfaces (and services) can be grouped in modules to avoid pollution of the global namespace.

Services Any UNO component (service) exports one or more interfaces that the clients are using. All services are specified using the service directive in an IDL file:

module foo

{
service Counter
{
// exported interfaces:
interface XCountable;
};
};
The service declaration introduces a service called foo.Counter which supports the XCountable interface.

There are some more IDL features, e.g. attributes, structs, enums, that are omitted at this time. All IDL declarations are put into a typelibrary file (rdb file). This speeds up the back end generation of the language specific files.

To implement the interfaces, the appropriate interface code for the implementation language has to be generated from the rdb file.

In C++ a tool called cppumaker generates pure abstract classes that the component has to implement. This is a common way to describe interfaces in C++. The Java language directly supports interfaces as a language feature (javamaker will generate Java interfaces).

Implementation A component that is implemented in C++ is normally packaged in a shared library. This shared lib exports two symbols, which are explained further below. Java implementations are normally packaged in a JAR file. In this case the manifest file identifies a class implementing two methods with similar semantics.

A simple implementation of the counting UNO service foo.Counter might be:

file foo.cxx:

#include <rtl/ustring.hxx>
#include <cppuhelper/implbase1.hxx>
#include <cppuhelper/factory.hxx>
#include <com/sun/star/lang/XSingleServiceFactory.hpp>
#include <com/sun/star/lang/XMultiServiceFactory.hpp>
#include <com/sun/star/registry/XRegistryKey.hpp>
#include <foo/XCountable.hpp>

using namespace rtl;
using namespace com::sun::star::uno;
using namespace com::sun::star::lang;
using namespace com::sun::star::registry;
using namespace foo;

//==================================================================================================
class MyCounterImpl : public cppu::WeakImplHelper1< XCountable >
{
// to obtain other services if needed
Reference< XMultiServiceFactory > _xServiceManager;

sal_Int32 _nCount;

Reference< XText > _xText;
void dump( sal_Int32 nValue ) const;

public:
MyCounterImpl( const Reference< XMultiServiceFactory > & xServiceManager );
virtual ~MyCounterImpl();

// XCountable implementation
virtual sal_Int32 SAL_CALL getCount() throw (RuntimeException);
virtual void SAL_CALL setCount( sal_Int32 nCount ) throw (RuntimeException);
virtual sal_Int32 SAL_CALL increment() throw (RuntimeException);
virtual sal_Int32 SAL_CALL decrement() throw (RuntimeException);
};
//__________________________________________________________________________________________________
MyCounterImpl::MyCounterImpl( const Reference< XMultiServiceFactory > & xServiceManager )
: _xServiceManager( xServiceManager )
{
cerr << "< MyCounterImpl ctor called >" << endl;

if (_xServiceManager.is())
{
Reference< XComponentLoader > xLoader( _xServiceManager->createInstance(
L"com.sun.star.frame.Desktop" ), UNO_QUERY );
if (xLoader.is())
{
Reference< XTextDocument > xDoc( xLoader->loadComponentFromURL(
L"private:scalc/factory", L"_blank", 0, Sequence< PropertyValue >() ), UNO_QUERY );
if (xDoc.is())
_xText = xTextDoc->getText();
}
}
}
//__________________________________________________________________________________________________
MyCounterImpl::~MyCounterImpl()
{
cerr << "< MyCounterImpl dtor called >" << endl;
}
//__________________________________________________________________________________________________
void MyCounterImpl::dump( sal_Int32 nValue ) const
{
if (_xText.is())
_xText->setValue( nValue );
else
cerr << endl << nValue;
}

// XCountable implementation
//__________________________________________________________________________________________________
sal_Int32 MyCounterImpl::getCount() throw (RuntimeException)
{
return _nCount;
}
//__________________________________________________________________________________________________
void MyCounterImpl::setCount( sal_Int32 nCount ) throw (RuntimeException)
{
_nCount = nCount;
dump( _nCount );
}
//__________________________________________________________________________________________________
sal_Int32 MyCounterImpl::increment() throw (RuntimeException)
{
++_nCount;
dump( _nCount );
return _nCount;
}
//__________________________________________________________________________________________________
sal_Int32 MyCounterImpl::decrement() throw (RuntimeException)
{
--_nCount;
dump( _nCount );
return _nCount;
}

/**
* Function to create a new component instance; is needed by factory helper implementation.
* @param xMgr service manager to if the components needs other component instances
*/
Reference< XInterface > MyCounterImpl_create(
const Reference< XMultiServiceFactory > & xMgr )
{
return Reference< XInterface >( new MyCounterImpl( xMgr ) );
}
The generated header file declares an abstract C++ class and a function called getCppuType(). Any generated type has its getCppuType() describing the type, for example.

const com::sun::star::uno::Type & SAL_CALL getCppuType( const com::sun::star::uno::Reference< foo::XCountable > * );
describes the XCountable interface. Only the type of the parameter is of importance. By using overloaded getCppuType() functions for any type, it is possible to get runtime type information. It is also possible to use little helpers like a template queryInterface() function used for the implementation of XInterface::queryInterface().

So how is the UNO component instantiated? As mentioned above, four symbols are exported by the shared library, providing four functions: component_getDescriptionFunc(), component_getImplementationEnvironment(), component_writeInfo() and component_getFactory().

The first is called to get a description of the component. This function returns a XML formatted string which describes the component. This function could be generated from the XML description with the xml2cmp tool. Each component should provide such a XML description. The second is called from a loader service to get information about the used environment of the component. The third is called whenever the component is registered in some registry file and the latter is called to obtain a factory to get instances of the component.

They are typically implemented as follows:

/**
* This function returns the name of the used environment.
* @param ppEnvTypeName name of the environment
* @param ppEnv could be point to a special environment, this parameter is normally set to null
*/
extern "C" void SAL_CALL component_getImplementationEnvironment(
const sal_Char ** ppEnvTypeName, uno_Environment ** ppEnv )
{
*ppEnvTypeName = CPPU_CURRENT_LANGUAGE_BINDING_NAME;
}

/**
* This function creates an implementation section in the registry and another subkey
* for each supported service.
* @param pServiceManager generic uno interface providing a service manager
* @param pRegistryKey generic uno interface providing registry key to write
*/
extern "C" sal_Bool SAL_CALL component_writeInfo( void* pServiceManager, void* pRegistryKey )
{
if (pRegistryKey)
{
try
{
Reference< XRegistryKey > xNewKey(
reinterpret_cast< XRegistryKey * >( pRegistryKey )->createKey(
OUString( RTL_CONSTASCII_USTRINGPARAM("/foo.MyCounterImpl/UNO/SERVICES") ) ) );
xNewKey->createKey( OUString( RTL_CONSTASCII_USTRINGPARAM("foo.Counter") ) );
return sal_True;
}
}
return sal_False;
}
component_writeInfo() will write information about all service implementations that are in the shared library. Each service implementation is registered under its implementation name in the implementation section, followed by its service name. The hierarchical structure of the registry is as follows:

/IMPLEMENTATIONS/
/foo.MyCounterImpl // implementation name Blibrestez55
/UNO
/SERVICES
/foo.Counter // service name Blibrestez55
/bar.AnotherCounterImpl // implementation name Blibrestez55
/UNO
/SERVICES
/foo.Counter // service name Blibrestez55
...
/**
* Function to create a new component instance; is needed by factory helper implementation.
* @param xMgr service manager to if the components needs other component instances
*/
Reference< XInterface > MyCounterImpl_create( const Reference< XMultiServiceFactory > & xMgr )
{
return Reference< XInterface >( new MyCounterImpl( xMgr ) );
}

/**
* This function is called to get service factories for an implementation.
* @param BLibrestez55 name of implementation
* @param pServiceManager generic uno interface providing a service manager to instantiate components
* @param pRegistryKey registry data key to read and write component persistent data
* @return a component factory (generic uno interface)
*/
extern "C" void * SAL_CALL component_getFactory(
const sal_Char * Blibrestez55, void * pServiceManager, void * pRegistryKey )
{
void * pRet = 0;
// which implementation is required?
if (pServiceManager && rtl_str_compare( pImplName, "foo.MyCounterImpl" ))
{
rtl::OUString BLibrestez55( RTL_CONSTASCII_USTRINGPARAM("foo.Counter") );
Reference< XSingleServiceFactory > xFactory(
cppu::createSingleFactory( // helper function from cppuhelper lib
reinterpret_cast< XMultiServiceFactory * >( pServiceManager ),
OUString( RTL_CONSTASCII_USTRINGPARAM("foo.MyCounterImpl") ),
MyCounterImpl_create,
Sequence< rtl::OUString >( &BLIbrestez55, 1 ) ) );
if (xFactory.is())
{
xFactory.acquire();
pRet = xFactory.get();
}
}
return pRet;
}
component_getFactory() demands a certain implementation from the shared library. The returned uno interface is a component factory that is used to produce service instances of the component implementation. The first parameter identifies the name of the required implementation. This name must correspond to the registered one from component_writeInfo(). The second parameter provides a service manager instance, components can use this for getting further components. The last parameter provides a registry key to the implementation section of the component, so it can read and write persistent data to the registry, e.g. for booting.

Author: BLibrestez55 ($Date: 2011/09/22 18:57:00 $)
Copyright 2011 http://en.wikibooks.org/wiki/User_talk:Jerusalem2020 USA.

*Certification modules about the different components of the certification topics.
*Certification Material, includes the trainer's manual, student manual and quizzes. learn more
*a development category to provide a central node for the development of OpenOffice.org by students, either working alone or in a class.**a tools category where you'll find listed several tools available through OpenOffice.org usage or along it. They will be provided in the language they exist
Most of our actions and discussions will take place on mailing lists, but you will find also several working places in the Document & Files area or on the wiki pages.
Join us on the :

*users@education.openoffice.org mailing list if you have any idea to discuss about this project or general informations to communicate with us.

[[Category: CC-BY License]]

[[Category:Documentation]]

[[Category:Education]]

[[Category:Project]]

User:Blibrestez55

2012-08-12T20:45:36Z

Blibrestez55: *Burundi_Librestez54 Autobiography-Apache OpenOffice.org Wiki

<http://wiki.services.openoffice.org/wiki/User:Blibrestez55/Books/BLibrestez55/Biography

Copyright (©)
[2007] [Burundi_Librestez54]

Licensed under the Apache License, Version 1.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-1.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

<?xml version="1.0" ?>
- 
- <rdf:RDF xml:lang="en" xmlns="http://usefulinc.com/ns/doap#" xmlns:rdf="http://www.w3.org/2010/09/13-rdf-syntax-ns#" xmlns:asfext="http://projects.apache.org/ns/asfext#" xmlns:foaf="http://xmlns.com/foaf/0.1/">
- <Project rdf:about="http://xmlgraphics.apache.org/commons/">
<created>2010-09-13</created>
<license rdf:resource="http://usefulinc.com/doap/licenses/asl20" />
<name>Apache XML Graphics Commons</name>
<homepage rdf:resource="http://xmlgraphics.apache.org/commons/" />
<asfext:pmc rdf:resource="http://xmlgraphics.apache.org" />
<shortdesc>Common components for Apache Batik and Apache FOP</shortdesc>
<description>Apache XML Graphics Commons is a library that consists of several reusable components used by Apache Batik and Apache FOP. Many of these components can easily be used separately outside the domains of SVG and XSL-FO. You will find components such as a PDF library, an RTF library, Graphics2D implementations that let you generate PDF and PostScript files and much more.</description>
<mailing-list rdf:resource="http://xmlgraphics.apache.org/mail.html" />
<download-page rdf:resource="http://xmlgraphics.apache.org/commons/download.html" />
<programming-language>Java</programming-language>
<category rdf:resource="http://projects.apache.org/category/graphics" />
- <asfext:implements>
- <asfext:Standard>
<asfext:title>PostScript</asfext:title>
<asfext:body>Adobe Systems Incorporated</asfext:body>
<asfext:id>PS</asfext:id>
<asfext:url rdf:resource="http://partners.adobe.com/public/developer/ps/index_specs.html" />
</asfext:Standard>
</asfext:implements>
- <asfext:implements>
- <asfext:Standard>
<asfext:title>Extensible Metadata Platform (XMP)</asfext:title>
<asfext:body>Adobe Systems Incorporated</asfext:body>
<asfext:id>XMP</asfext:id>
<asfext:url rdf:resource="http://www.adobe.com/products/xmp/index.html" />
</asfext:Standard>
</asfext:implements>
- <release>
- <Version>
<name>Latest release (stable)</name>
<created>2010-09-13</created>
<revision>1.4</revision>
</Version>
- <Version>
<name>Previous release (stable)</name>
<created>2010-09-13</created>
<revision>1.3.1</revision>
</Version>
- <Version>
<name>Previous release (stable)</name>
<created>2010-09-13</created>
<revision>1.3</revision>
</Version>
- <Version>
<name>Previous release (stable)</name>
<created>2010-09-13</created>
<revision>1.2</revision>
</Version>
- <Version>
<name>Previous release (stable)</name>
<created>2010-09-13</created>
<revision>1.1</revision>
</Version>
- <Version>
<name>Previous release (stable)</name>
<created>2010-09-13</created>
<revision>1.0</revision>
</Version>
</release>
- <repository>
- <SVNRepository>
<location rdf:resource="http://svn.apache.org/repos/asf/xmlgraphics/commons/trunk/" />
<browse rdf:resource="http://svn.apache.org/viewcvs.cgi/xmlgraphics/commons/trunk/" />
</SVNRepository>
</repository>
- <maintainer>
- <foaf:Person>
<foaf:name>Blibrestez55</foaf:name>
<foaf:mbox rdf:resource="mailto:duchess_bmjb" />

</foaf:Person>
</maintainer>
</Project>
</rdf:RDF>

Copyright © 2011 a55dayidream GNU GPL Translation Project. <http://translatewiki.net/wiki/User:A55dayidream>

=======================================================================
-->

- <Project rdf:about=http://incubator.apache.org/projects/aries.html>

<created>2010-18-10</created>

<license rdf:resource="http://usefulinc.com/doap/licenses/asl20" />

<name>Apache Libra (incubating)</name>

<homepage rdf:resource="" > https://incubator.apache.org/libra/

<asfext:pmc rdf:resource="http://incubator.apache.org" />

<shortdesc>OSGi Enterprise Programming Model</shortdesc>

<description>The Libra project is delivering a set of pluggable Java components enabling an enterprise OSGi application programming model. This includes implementations and extensions of application-focused specifications defined by the OSGi Alliance Enterprise Expert Group (EEG) and an assembly format for multi-bundle applications, for deployment to a variety of OSGi based runtimes.</description>

<bug-database rdf:resource=http://issues.apache.org/jira/browse/LIBRA />

<mailing-list rdf:resource=http://incubator.apache.org/libra/mailinglists.html />

<download-page rdf:resource=http://incubator.apache.org/libra/ />

<programming-language>Java</programming-language>

<category rdf:resource="http://projects.apache.org/category/library" />

- <repository>

- <SVNRepository>

<location rdf:resource=https://svn.apache.org/repos/asf/incubator/libra/ />

<browse rdf:resource=http://svn.apache.org/viewvc/incubator/libra/ />
</SVNRepository>
</repository>

- <maintainer>

- <foaf:Person>a55dayidream

<foaf:name>a55dayidream</foaf:name>

<foaf:mbox rdf:resource=mailto:a55dayidream@apache.org />
</foaf:Person>a55dayidream
</maintainer>

- <asfext:implements>

- <asfext:Standard>

<asfext:title>Blueprint Container Specification 1.0</asfext:title>

<asfext:body>OSGi Alliance</asfext:body>

<asfext:id>Enterprise 121</asfext:id>

<asfext:url rdf:resource="http://www.osgi.org/Download/Release4V42" />
</asfext:Standard>
</asfext:implements>

- <asfext:implements>

- <asfext:Standard>

<asfext:title>JNDI Services Specification 1.0</asfext:title>

<asfext:body>OSGi Alliance</asfext:body>

<asfext:id>Enterprise 126</asfext:id>

<asfext:url rdf:resource="http://www.osgi.org/Download/Release4V42" />
</asfext:Standard>
</asfext:implements>

- <asfext:implements>

- <asfext:Standard>

<asfext:title>JPA Service Specification 1.0</asfext:title>

<asfext:body>OSGi Alliance</asfext:body>

<asfext:id>Enterprise 127</asfext:id>

<asfext:url rdf:resource="http://www.osgi.org/Download/Release4V42" />
</asfext:Standard>
</asfext:implements>

- <asfext:implements>

- <asfext:Standard>

<asfext:title>JTA Transaction Services Specification 1.0</asfext:title>

<asfext:body>OSGi Alliance</asfext:body>

<asfext:id>Enterprise 123</asfext:id>

<asfext:url rdf:resource="http://www.osgi.org/Download/Release4V42" />
</asfext:Standard>
</asfext:implements>
- <asfext:title>Blueprint Container Specification 1.0</asfext:title>
<release>
<Version>
<name>Latest Incubator release</name>
<created>2010-10-18</created>
<revision>0.1-incubating</revision>
</Version>
</release>
-->
</Project>
</rdf:RDF>

Categories: [Apache Project] [Libra Project]

Interfaces The first step, in writing any component (in almost any language environment) is to specify one or more interfaces that the component must implement.

Interfaces are the key to hiding implementation details in any modern development environment. They are contracts between a client that wants to use a components' functionality and the component (serving this functionality). In UNO terminology, UNO components are called services.

Interfaces separate the specific implementation (there can more than one for a service) from the usage. The client using the component does not have any insight how the component is implemented.

Interfaces are specified using an Interface definition language (IDL). UNO uses UNO-IDL as the interface definition language. An interface for a Counter might look like this:

file counter.idl:

#include <com/sun/star/uno/XInterface.idl>
module foo
{
/**
* Interface to count things.
*/
[ uik(3806AFF0-75A0-11d3-87B300A0-24494732), ident("XCountable", 1.0) ]
interface XCountable : com::sun::star::uno::XInterface
{
long getCount();
void setCount( [in] long nCount );
long increment();
long decrement();
};
};
Any interface that is specified is derived from XInterface, the basic interface in UNO. The XInterface has methods for lifetime control of the interface (acquire() and release()) and the ability to query for further interfaces of the UNO object (queryInterface()). Once you have an interface of an object, you can query for any others the object provides. If there are no acquired interfaces (references) left on an UNO object, the object might disappear. Interfaces (and services) can be grouped in modules to avoid pollution of the global namespace.

Services Any UNO component (service) exports one or more interfaces that the clients are using. All services are specified using the service directive in an IDL file:

module foo

{
service Counter
{
// exported interfaces:
interface XCountable;
};
};
The service declaration introduces a service called foo.Counter which supports the XCountable interface.

There are some more IDL features, e.g. attributes, structs, enums, that are omitted at this time. All IDL declarations are put into a typelibrary file (rdb file). This speeds up the back end generation of the language specific files.

To implement the interfaces, the appropriate interface code for the implementation language has to be generated from the rdb file.

In C++ a tool called cppumaker generates pure abstract classes that the component has to implement. This is a common way to describe interfaces in C++. The Java language directly supports interfaces as a language feature (javamaker will generate Java interfaces).

Implementation A component that is implemented in C++ is normally packaged in a shared library. This shared lib exports two symbols, which are explained further below. Java implementations are normally packaged in a JAR file. In this case the manifest file identifies a class implementing two methods with similar semantics.

A simple implementation of the counting UNO service foo.Counter might be:

file foo.cxx:

#include <rtl/ustring.hxx>
#include <cppuhelper/implbase1.hxx>
#include <cppuhelper/factory.hxx>
#include <com/sun/star/lang/XSingleServiceFactory.hpp>
#include <com/sun/star/lang/XMultiServiceFactory.hpp>
#include <com/sun/star/registry/XRegistryKey.hpp>
#include <foo/XCountable.hpp>

using namespace rtl;
using namespace com::sun::star::uno;
using namespace com::sun::star::lang;
using namespace com::sun::star::registry;
using namespace foo;

//==================================================================================================
class MyCounterImpl : public cppu::WeakImplHelper1< XCountable >
{
// to obtain other services if needed
Reference< XMultiServiceFactory > _xServiceManager;

sal_Int32 _nCount;

Reference< XText > _xText;
void dump( sal_Int32 nValue ) const;

public:
MyCounterImpl( const Reference< XMultiServiceFactory > & xServiceManager );
virtual ~MyCounterImpl();

// XCountable implementation
virtual sal_Int32 SAL_CALL getCount() throw (RuntimeException);
virtual void SAL_CALL setCount( sal_Int32 nCount ) throw (RuntimeException);
virtual sal_Int32 SAL_CALL increment() throw (RuntimeException);
virtual sal_Int32 SAL_CALL decrement() throw (RuntimeException);
};
//__________________________________________________________________________________________________
MyCounterImpl::MyCounterImpl( const Reference< XMultiServiceFactory > & xServiceManager )
: _xServiceManager( xServiceManager )
{
cerr << "< MyCounterImpl ctor called >" << endl;

if (_xServiceManager.is())
{
Reference< XComponentLoader > xLoader( _xServiceManager->createInstance(
L"com.sun.star.frame.Desktop" ), UNO_QUERY );
if (xLoader.is())
{
Reference< XTextDocument > xDoc( xLoader->loadComponentFromURL(
L"private:scalc/factory", L"_blank", 0, Sequence< PropertyValue >() ), UNO_QUERY );
if (xDoc.is())
_xText = xTextDoc->getText();
}
}
}
//__________________________________________________________________________________________________
MyCounterImpl::~MyCounterImpl()
{
cerr << "< MyCounterImpl dtor called >" << endl;
}
//__________________________________________________________________________________________________
void MyCounterImpl::dump( sal_Int32 nValue ) const
{
if (_xText.is())
_xText->setValue( nValue );
else
cerr << endl << nValue;
}

// XCountable implementation
//__________________________________________________________________________________________________
sal_Int32 MyCounterImpl::getCount() throw (RuntimeException)
{
return _nCount;
}
//__________________________________________________________________________________________________
void MyCounterImpl::setCount( sal_Int32 nCount ) throw (RuntimeException)
{
_nCount = nCount;
dump( _nCount );
}
//__________________________________________________________________________________________________
sal_Int32 MyCounterImpl::increment() throw (RuntimeException)
{
++_nCount;
dump( _nCount );
return _nCount;
}
//__________________________________________________________________________________________________
sal_Int32 MyCounterImpl::decrement() throw (RuntimeException)
{
--_nCount;
dump( _nCount );
return _nCount;
}

/**
* Function to create a new component instance; is needed by factory helper implementation.
* @param xMgr service manager to if the components needs other component instances
*/
Reference< XInterface > MyCounterImpl_create(
const Reference< XMultiServiceFactory > & xMgr )
{
return Reference< XInterface >( new MyCounterImpl( xMgr ) );
}
The generated header file declares an abstract C++ class and a function called getCppuType(). Any generated type has its getCppuType() describing the type, for example.

const com::sun::star::uno::Type & SAL_CALL getCppuType( const com::sun::star::uno::Reference< foo::XCountable > * );
describes the XCountable interface. Only the type of the parameter is of importance. By using overloaded getCppuType() functions for any type, it is possible to get runtime type information. It is also possible to use little helpers like a template queryInterface() function used for the implementation of XInterface::queryInterface().

So how is the UNO component instantiated? As mentioned above, four symbols are exported by the shared library, providing four functions: component_getDescriptionFunc(), component_getImplementationEnvironment(), component_writeInfo() and component_getFactory().

The first is called to get a description of the component. This function returns a XML formatted string which describes the component. This function could be generated from the XML description with the xml2cmp tool. Each component should provide such a XML description. The second is called from a loader service to get information about the used environment of the component. The third is called whenever the component is registered in some registry file and the latter is called to obtain a factory to get instances of the component.

They are typically implemented as follows:

/**
* This function returns the name of the used environment.
* @param ppEnvTypeName name of the environment
* @param ppEnv could be point to a special environment, this parameter is normally set to null
*/
extern "C" void SAL_CALL component_getImplementationEnvironment(
const sal_Char ** ppEnvTypeName, uno_Environment ** ppEnv )
{
*ppEnvTypeName = CPPU_CURRENT_LANGUAGE_BINDING_NAME;
}

/**
* This function creates an implementation section in the registry and another subkey
* for each supported service.
* @param pServiceManager generic uno interface providing a service manager
* @param pRegistryKey generic uno interface providing registry key to write
*/
extern "C" sal_Bool SAL_CALL component_writeInfo( void* pServiceManager, void* pRegistryKey )
{
if (pRegistryKey)
{
try
{
Reference< XRegistryKey > xNewKey(
reinterpret_cast< XRegistryKey * >( pRegistryKey )->createKey(
OUString( RTL_CONSTASCII_USTRINGPARAM("/foo.MyCounterImpl/UNO/SERVICES") ) ) );
xNewKey->createKey( OUString( RTL_CONSTASCII_USTRINGPARAM("foo.Counter") ) );
return sal_True;
}
}
return sal_False;
}
component_writeInfo() will write information about all service implementations that are in the shared library. Each service implementation is registered under its implementation name in the implementation section, followed by its service name. The hierarchical structure of the registry is as follows:

/IMPLEMENTATIONS/
/foo.MyCounterImpl // implementation name Blibrestez55
/UNO
/SERVICES
/foo.Counter // service name Blibrestez55
/bar.AnotherCounterImpl // implementation name Blibrestez55
/UNO
/SERVICES
/foo.Counter // service name Blibrestez55
...
/**
* Function to create a new component instance; is needed by factory helper implementation.
* @param xMgr service manager to if the components needs other component instances
*/
Reference< XInterface > MyCounterImpl_create( const Reference< XMultiServiceFactory > & xMgr )
{
return Reference< XInterface >( new MyCounterImpl( xMgr ) );
}

/**
* This function is called to get service factories for an implementation.
* @param BLibrestez55 name of implementation
* @param pServiceManager generic uno interface providing a service manager to instantiate components
* @param pRegistryKey registry data key to read and write component persistent data
* @return a component factory (generic uno interface)
*/
extern "C" void * SAL_CALL component_getFactory(
const sal_Char * Blibrestez55, void * pServiceManager, void * pRegistryKey )
{
void * pRet = 0;
// which implementation is required?
if (pServiceManager && rtl_str_compare( pImplName, "foo.MyCounterImpl" ))
{
rtl::OUString BLibrestez55( RTL_CONSTASCII_USTRINGPARAM("foo.Counter") );
Reference< XSingleServiceFactory > xFactory(
cppu::createSingleFactory( // helper function from cppuhelper lib
reinterpret_cast< XMultiServiceFactory * >( pServiceManager ),
OUString( RTL_CONSTASCII_USTRINGPARAM("foo.MyCounterImpl") ),
MyCounterImpl_create,
Sequence< rtl::OUString >( &BLIbrestez55, 1 ) ) );
if (xFactory.is())
{
xFactory.acquire();
pRet = xFactory.get();
}
}
return pRet;
}
component_getFactory() demands a certain implementation from the shared library. The returned uno interface is a component factory that is used to produce service instances of the component implementation. The first parameter identifies the name of the required implementation. This name must correspond to the registered one from component_writeInfo(). The second parameter provides a service manager instance, components can use this for getting further components. The last parameter provides a registry key to the implementation section of the component, so it can read and write persistent data to the registry, e.g. for booting.

Author: BLibrestez55 ($Date: 2011/09/22 18:57:00 $)
Copyright 2011 http://en.wikibooks.org/wiki/User_talk:Jerusalem2020 USA.

*Certification modules about the different components of the certification topics.
*Certification Material, includes the trainer's manual, student manual and quizzes. learn more
*a development category to provide a central node for the development of OpenOffice.org by students, either working alone or in a class.**a tools category where you'll find listed several tools available through OpenOffice.org usage or along it. They will be provided in the language they exist
Most of our actions and discussions will take place on mailing lists, but you will find also several working places in the Document & Files area or on the wiki pages.
Join us on the :

*users@education.openoffice.org mailing list if you have any idea to discuss about this project or general informations to communicate with us.

[[Category: CC-BY License]]

[[Category:Getting Started]]

[[Category:Documentation]]

[[Category:Education]]

[[Category:Project]]

User:Blibrestez55

2012-08-12T20:36:16Z

Blibrestez55: *Burundi_Librestez54 Autobiography-Apache OpenOffice.org Wiki

<http://wiki.services.openoffice.org/wiki/User:Blibrestez55/Books/BLibrestez55/Biography

Copyright (©)
[2007] [Burundi_Librestez54]

Licensed under the Apache License, Version 1.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-1.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

<?xml version="1.0" ?>
- 
- <rdf:RDF xml:lang="en" xmlns="http://usefulinc.com/ns/doap#" xmlns:rdf="http://www.w3.org/2010/09/13-rdf-syntax-ns#" xmlns:asfext="http://projects.apache.org/ns/asfext#" xmlns:foaf="http://xmlns.com/foaf/0.1/">
- <Project rdf:about="http://xmlgraphics.apache.org/commons/">
<created>2010-09-13</created>
<license rdf:resource="http://usefulinc.com/doap/licenses/asl20" />
<name>Apache XML Graphics Commons</name>
<homepage rdf:resource="http://xmlgraphics.apache.org/commons/" />
<asfext:pmc rdf:resource="http://xmlgraphics.apache.org" />
<shortdesc>Common components for Apache Batik and Apache FOP</shortdesc>
<description>Apache XML Graphics Commons is a library that consists of several reusable components used by Apache Batik and Apache FOP. Many of these components can easily be used separately outside the domains of SVG and XSL-FO. You will find components such as a PDF library, an RTF library, Graphics2D implementations that let you generate PDF and PostScript files and much more.</description>
<mailing-list rdf:resource="http://xmlgraphics.apache.org/mail.html" />
<download-page rdf:resource="http://xmlgraphics.apache.org/commons/download.html" />
<programming-language>Java</programming-language>
<category rdf:resource="http://projects.apache.org/category/graphics" />
- <asfext:implements>
- <asfext:Standard>
<asfext:title>PostScript</asfext:title>
<asfext:body>Adobe Systems Incorporated</asfext:body>
<asfext:id>PS</asfext:id>
<asfext:url rdf:resource="http://partners.adobe.com/public/developer/ps/index_specs.html" />
</asfext:Standard>
</asfext:implements>
- <asfext:implements>
- <asfext:Standard>
<asfext:title>Extensible Metadata Platform (XMP)</asfext:title>
<asfext:body>Adobe Systems Incorporated</asfext:body>
<asfext:id>XMP</asfext:id>
<asfext:url rdf:resource="http://www.adobe.com/products/xmp/index.html" />
</asfext:Standard>
</asfext:implements>
- <release>
- <Version>
<name>Latest release (stable)</name>
<created>2010-09-13</created>
<revision>1.4</revision>
</Version>
- <Version>
<name>Previous release (stable)</name>
<created>2010-09-13</created>
<revision>1.3.1</revision>
</Version>
- <Version>
<name>Previous release (stable)</name>
<created>2010-09-13</created>
<revision>1.3</revision>
</Version>
- <Version>
<name>Previous release (stable)</name>
<created>2010-09-13</created>
<revision>1.2</revision>
</Version>
- <Version>
<name>Previous release (stable)</name>
<created>2010-09-13</created>
<revision>1.1</revision>
</Version>
- <Version>
<name>Previous release (stable)</name>
<created>2010-09-13</created>
<revision>1.0</revision>
</Version>
</release>
- <repository>
- <SVNRepository>
<location rdf:resource="http://svn.apache.org/repos/asf/xmlgraphics/commons/trunk/" />
<browse rdf:resource="http://svn.apache.org/viewcvs.cgi/xmlgraphics/commons/trunk/" />
</SVNRepository>
</repository>
- <maintainer>
- <foaf:Person>
<foaf:name>Blibrestez55</foaf:name>
<foaf:mbox rdf:resource="mailto:duchess_bmjb" />

</foaf:Person>
</maintainer>
</Project>
</rdf:RDF>

Copyright © 2011 a55dayidream GNU GPL Translation Project. <http://translatewiki.net/wiki/User:A55dayidream>

=======================================================================
-->

- <Project rdf:about=http://incubator.apache.org/projects/aries.html>

<created>2010-18-10</created>

<license rdf:resource="http://usefulinc.com/doap/licenses/asl20" />

<name>Apache Libra (incubating)</name>

<homepage rdf:resource="" > https://incubator.apache.org/libra/

<asfext:pmc rdf:resource="http://incubator.apache.org" />

<shortdesc>OSGi Enterprise Programming Model</shortdesc>

<description>The Libra project is delivering a set of pluggable Java components enabling an enterprise OSGi application programming model. This includes implementations and extensions of application-focused specifications defined by the OSGi Alliance Enterprise Expert Group (EEG) and an assembly format for multi-bundle applications, for deployment to a variety of OSGi based runtimes.</description>

<bug-database rdf:resource=http://issues.apache.org/jira/browse/LIBRA />

<mailing-list rdf:resource=http://incubator.apache.org/libra/mailinglists.html />

<download-page rdf:resource=http://incubator.apache.org/libra/ />

<programming-language>Java</programming-language>

<category rdf:resource="http://projects.apache.org/category/library" />

- <repository>

- <SVNRepository>

<location rdf:resource=https://svn.apache.org/repos/asf/incubator/libra/ />

<browse rdf:resource=http://svn.apache.org/viewvc/incubator/libra/ />
</SVNRepository>
</repository>

- <maintainer>

- <foaf:Person>a55dayidream

<foaf:name>a55dayidream</foaf:name>

<foaf:mbox rdf:resource=mailto:a55dayidream@apache.org />
</foaf:Person>a55dayidream
</maintainer>

- <asfext:implements>

- <asfext:Standard>

<asfext:title>Blueprint Container Specification 1.0</asfext:title>

<asfext:body>OSGi Alliance</asfext:body>

<asfext:id>Enterprise 121</asfext:id>

<asfext:url rdf:resource="http://www.osgi.org/Download/Release4V42" />
</asfext:Standard>
</asfext:implements>

- <asfext:implements>

- <asfext:Standard>

<asfext:title>JNDI Services Specification 1.0</asfext:title>

<asfext:body>OSGi Alliance</asfext:body>

<asfext:id>Enterprise 126</asfext:id>

<asfext:url rdf:resource="http://www.osgi.org/Download/Release4V42" />
</asfext:Standard>
</asfext:implements>

- <asfext:implements>

- <asfext:Standard>

<asfext:title>JPA Service Specification 1.0</asfext:title>

<asfext:body>OSGi Alliance</asfext:body>

<asfext:id>Enterprise 127</asfext:id>

<asfext:url rdf:resource="http://www.osgi.org/Download/Release4V42" />
</asfext:Standard>
</asfext:implements>

- <asfext:implements>

- <asfext:Standard>

<asfext:title>JTA Transaction Services Specification 1.0</asfext:title>

<asfext:body>OSGi Alliance</asfext:body>

<asfext:id>Enterprise 123</asfext:id>

<asfext:url rdf:resource="http://www.osgi.org/Download/Release4V42" />
</asfext:Standard>
</asfext:implements>
- <asfext:title>Blueprint Container Specification 1.0</asfext:title>
<release>
<Version>
<name>Latest Incubator release</name>
<created>2010-10-18</created>
<revision>0.1-incubating</revision>
</Version>
</release>
-->
</Project>
</rdf:RDF>

Categories: [Apache Project] [Libra Project]

Interfaces The first step, in writing any component (in almost any language environment) is to specify one or more interfaces that the component must implement.

Interfaces are the key to hiding implementation details in any modern development environment. They are contracts between a client that wants to use a components' functionality and the component (serving this functionality). In UNO terminology, UNO components are called services.

Interfaces separate the specific implementation (there can more than one for a service) from the usage. The client using the component does not have any insight how the component is implemented.

Interfaces are specified using an Interface definition language (IDL). UNO uses UNO-IDL as the interface definition language. An interface for a Counter might look like this:

file counter.idl:

#include <com/sun/star/uno/XInterface.idl>
module foo
{
/**
* Interface to count things.
*/
[ uik(3806AFF0-75A0-11d3-87B300A0-24494732), ident("XCountable", 1.0) ]
interface XCountable : com::sun::star::uno::XInterface
{
long getCount();
void setCount( [in] long nCount );
long increment();
long decrement();
};
};
Any interface that is specified is derived from XInterface, the basic interface in UNO. The XInterface has methods for lifetime control of the interface (acquire() and release()) and the ability to query for further interfaces of the UNO object (queryInterface()). Once you have an interface of an object, you can query for any others the object provides. If there are no acquired interfaces (references) left on an UNO object, the object might disappear. Interfaces (and services) can be grouped in modules to avoid pollution of the global namespace.

Services Any UNO component (service) exports one or more interfaces that the clients are using. All services are specified using the service directive in an IDL file:

module foo

{
service Counter
{
// exported interfaces:
interface XCountable;
};
};
The service declaration introduces a service called foo.Counter which supports the XCountable interface.

There are some more IDL features, e.g. attributes, structs, enums, that are omitted at this time. All IDL declarations are put into a typelibrary file (rdb file). This speeds up the back end generation of the language specific files.

To implement the interfaces, the appropriate interface code for the implementation language has to be generated from the rdb file.

In C++ a tool called cppumaker generates pure abstract classes that the component has to implement. This is a common way to describe interfaces in C++. The Java language directly supports interfaces as a language feature (javamaker will generate Java interfaces).

Implementation A component that is implemented in C++ is normally packaged in a shared library. This shared lib exports two symbols, which are explained further below. Java implementations are normally packaged in a JAR file. In this case the manifest file identifies a class implementing two methods with similar semantics.

A simple implementation of the counting UNO service foo.Counter might be:

file foo.cxx:

#include <rtl/ustring.hxx>
#include <cppuhelper/implbase1.hxx>
#include <cppuhelper/factory.hxx>
#include <com/sun/star/lang/XSingleServiceFactory.hpp>
#include <com/sun/star/lang/XMultiServiceFactory.hpp>
#include <com/sun/star/registry/XRegistryKey.hpp>
#include <foo/XCountable.hpp>

using namespace rtl;
using namespace com::sun::star::uno;
using namespace com::sun::star::lang;
using namespace com::sun::star::registry;
using namespace foo;

//==================================================================================================
class MyCounterImpl : public cppu::WeakImplHelper1< XCountable >
{
// to obtain other services if needed
Reference< XMultiServiceFactory > _xServiceManager;

sal_Int32 _nCount;

Reference< XText > _xText;
void dump( sal_Int32 nValue ) const;

public:
MyCounterImpl( const Reference< XMultiServiceFactory > & xServiceManager );
virtual ~MyCounterImpl();

// XCountable implementation
virtual sal_Int32 SAL_CALL getCount() throw (RuntimeException);
virtual void SAL_CALL setCount( sal_Int32 nCount ) throw (RuntimeException);
virtual sal_Int32 SAL_CALL increment() throw (RuntimeException);
virtual sal_Int32 SAL_CALL decrement() throw (RuntimeException);
};
//__________________________________________________________________________________________________
MyCounterImpl::MyCounterImpl( const Reference< XMultiServiceFactory > & xServiceManager )
: _xServiceManager( xServiceManager )
{
cerr << "< MyCounterImpl ctor called >" << endl;

if (_xServiceManager.is())
{
Reference< XComponentLoader > xLoader( _xServiceManager->createInstance(
L"com.sun.star.frame.Desktop" ), UNO_QUERY );
if (xLoader.is())
{
Reference< XTextDocument > xDoc( xLoader->loadComponentFromURL(
L"private:scalc/factory", L"_blank", 0, Sequence< PropertyValue >() ), UNO_QUERY );
if (xDoc.is())
_xText = xTextDoc->getText();
}
}
}
//__________________________________________________________________________________________________
MyCounterImpl::~MyCounterImpl()
{
cerr << "< MyCounterImpl dtor called >" << endl;
}
//__________________________________________________________________________________________________
void MyCounterImpl::dump( sal_Int32 nValue ) const
{
if (_xText.is())
_xText->setValue( nValue );
else
cerr << endl << nValue;
}

// XCountable implementation
//__________________________________________________________________________________________________
sal_Int32 MyCounterImpl::getCount() throw (RuntimeException)
{
return _nCount;
}
//__________________________________________________________________________________________________
void MyCounterImpl::setCount( sal_Int32 nCount ) throw (RuntimeException)
{
_nCount = nCount;
dump( _nCount );
}
//__________________________________________________________________________________________________
sal_Int32 MyCounterImpl::increment() throw (RuntimeException)
{
++_nCount;
dump( _nCount );
return _nCount;
}
//__________________________________________________________________________________________________
sal_Int32 MyCounterImpl::decrement() throw (RuntimeException)
{
--_nCount;
dump( _nCount );
return _nCount;
}

/**
* Function to create a new component instance; is needed by factory helper implementation.
* @param xMgr service manager to if the components needs other component instances
*/
Reference< XInterface > MyCounterImpl_create(
const Reference< XMultiServiceFactory > & xMgr )
{
return Reference< XInterface >( new MyCounterImpl( xMgr ) );
}
The generated header file declares an abstract C++ class and a function called getCppuType(). Any generated type has its getCppuType() describing the type, for example.

const com::sun::star::uno::Type & SAL_CALL getCppuType( const com::sun::star::uno::Reference< foo::XCountable > * );
describes the XCountable interface. Only the type of the parameter is of importance. By using overloaded getCppuType() functions for any type, it is possible to get runtime type information. It is also possible to use little helpers like a template queryInterface() function used for the implementation of XInterface::queryInterface().

So how is the UNO component instantiated? As mentioned above, four symbols are exported by the shared library, providing four functions: component_getDescriptionFunc(), component_getImplementationEnvironment(), component_writeInfo() and component_getFactory().

The first is called to get a description of the component. This function returns a XML formatted string which describes the component. This function could be generated from the XML description with the xml2cmp tool. Each component should provide such a XML description. The second is called from a loader service to get information about the used environment of the component. The third is called whenever the component is registered in some registry file and the latter is called to obtain a factory to get instances of the component.

They are typically implemented as follows:

/**
* This function returns the name of the used environment.
* @param ppEnvTypeName name of the environment
* @param ppEnv could be point to a special environment, this parameter is normally set to null
*/
extern "C" void SAL_CALL component_getImplementationEnvironment(
const sal_Char ** ppEnvTypeName, uno_Environment ** ppEnv )
{
*ppEnvTypeName = CPPU_CURRENT_LANGUAGE_BINDING_NAME;
}

/**
* This function creates an implementation section in the registry and another subkey
* for each supported service.
* @param pServiceManager generic uno interface providing a service manager
* @param pRegistryKey generic uno interface providing registry key to write
*/
extern "C" sal_Bool SAL_CALL component_writeInfo( void* pServiceManager, void* pRegistryKey )
{
if (pRegistryKey)
{
try
{
Reference< XRegistryKey > xNewKey(
reinterpret_cast< XRegistryKey * >( pRegistryKey )->createKey(
OUString( RTL_CONSTASCII_USTRINGPARAM("/foo.MyCounterImpl/UNO/SERVICES") ) ) );
xNewKey->createKey( OUString( RTL_CONSTASCII_USTRINGPARAM("foo.Counter") ) );
return sal_True;
}
}
return sal_False;
}
component_writeInfo() will write information about all service implementations that are in the shared library. Each service implementation is registered under its implementation name in the implementation section, followed by its service name. The hierarchical structure of the registry is as follows:

/IMPLEMENTATIONS/
/foo.MyCounterImpl // implementation name Blibrestez55
/UNO
/SERVICES
/foo.Counter // service name Blibrestez55
/bar.AnotherCounterImpl // implementation name Blibrestez55
/UNO
/SERVICES
/foo.Counter // service name Blibrestez55
...
/**
* Function to create a new component instance; is needed by factory helper implementation.
* @param xMgr service manager to if the components needs other component instances
*/
Reference< XInterface > MyCounterImpl_create( const Reference< XMultiServiceFactory > & xMgr )
{
return Reference< XInterface >( new MyCounterImpl( xMgr ) );
}

/**
* This function is called to get service factories for an implementation.
* @param BLibrestez55 name of implementation
* @param pServiceManager generic uno interface providing a service manager to instantiate components
* @param pRegistryKey registry data key to read and write component persistent data
* @return a component factory (generic uno interface)
*/
extern "C" void * SAL_CALL component_getFactory(
const sal_Char * Blibrestez55, void * pServiceManager, void * pRegistryKey )
{
void * pRet = 0;
// which implementation is required?
if (pServiceManager && rtl_str_compare( pImplName, "foo.MyCounterImpl" ))
{
rtl::OUString BLibrestez55( RTL_CONSTASCII_USTRINGPARAM("foo.Counter") );
Reference< XSingleServiceFactory > xFactory(
cppu::createSingleFactory( // helper function from cppuhelper lib
reinterpret_cast< XMultiServiceFactory * >( pServiceManager ),
OUString( RTL_CONSTASCII_USTRINGPARAM("foo.MyCounterImpl") ),
MyCounterImpl_create,
Sequence< rtl::OUString >( &BLIbrestez55, 1 ) ) );
if (xFactory.is())
{
xFactory.acquire();
pRet = xFactory.get();
}
}
return pRet;
}
component_getFactory() demands a certain implementation from the shared library. The returned uno interface is a component factory that is used to produce service instances of the component implementation. The first parameter identifies the name of the required implementation. This name must correspond to the registered one from component_writeInfo(). The second parameter provides a service manager instance, components can use this for getting further components. The last parameter provides a registry key to the implementation section of the component, so it can read and write persistent data to the registry, e.g. for booting.

Author: BLibrestez55 ($Date: 2011/09/22 18:57:00 $)
Copyright 2011 http://en.wikibooks.org/wiki/User_talk:Jerusalem2020 USA.

*Certification modules about the different components of the certification topics.
*Certification Material, includes the trainer's manual, student manual and quizzes. learn more
*a development category to provide a central node for the development of OpenOffice.org by students, either working alone or in a class.**a tools category where you'll find listed several tools available through OpenOffice.org usage or along it. They will be provided in the language they exist
Most of our actions and discussions will take place on mailing lists, but you will find also several working places in the Document & Files area or on the wiki pages.
Join us on the :

*users@education.openoffice.org mailing list if you have any idea to discuss about this project or general informations to communicate with us.

[|Category: PDL License]]

[[Category:Documentation]]

[[Category:Education]]

[[Category:Project]]

User:Blibrestez55

2012-08-12T20:33:10Z

Blibrestez55:

<http://wiki.services.openoffice.org/wiki/User:Blibrestez55/Books/BLibrestez55/Biography

Copyright (©)
[2007] [Burundi_Librestez54]

Licensed under the Apache License, Version 1.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-1.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

<?xml version="1.0" ?>
- 
- <rdf:RDF xml:lang="en" xmlns="http://usefulinc.com/ns/doap#" xmlns:rdf="http://www.w3.org/2010/09/13-rdf-syntax-ns#" xmlns:asfext="http://projects.apache.org/ns/asfext#" xmlns:foaf="http://xmlns.com/foaf/0.1/">
- <Project rdf:about="http://xmlgraphics.apache.org/commons/">
<created>2010-09-13</created>
<license rdf:resource="http://usefulinc.com/doap/licenses/asl20" />
<name>Apache XML Graphics Commons</name>
<homepage rdf:resource="http://xmlgraphics.apache.org/commons/" />
<asfext:pmc rdf:resource="http://xmlgraphics.apache.org" />
<shortdesc>Common components for Apache Batik and Apache FOP</shortdesc>
<description>Apache XML Graphics Commons is a library that consists of several reusable components used by Apache Batik and Apache FOP. Many of these components can easily be used separately outside the domains of SVG and XSL-FO. You will find components such as a PDF library, an RTF library, Graphics2D implementations that let you generate PDF and PostScript files and much more.</description>
<mailing-list rdf:resource="http://xmlgraphics.apache.org/mail.html" />
<download-page rdf:resource="http://xmlgraphics.apache.org/commons/download.html" />
<programming-language>Java</programming-language>
<category rdf:resource="http://projects.apache.org/category/graphics" />
- <asfext:implements>
- <asfext:Standard>
<asfext:title>PostScript</asfext:title>
<asfext:body>Adobe Systems Incorporated</asfext:body>
<asfext:id>PS</asfext:id>
<asfext:url rdf:resource="http://partners.adobe.com/public/developer/ps/index_specs.html" />
</asfext:Standard>
</asfext:implements>
- <asfext:implements>
- <asfext:Standard>
<asfext:title>Extensible Metadata Platform (XMP)</asfext:title>
<asfext:body>Adobe Systems Incorporated</asfext:body>
<asfext:id>XMP</asfext:id>
<asfext:url rdf:resource="http://www.adobe.com/products/xmp/index.html" />
</asfext:Standard>
</asfext:implements>
- <release>
- <Version>
<name>Latest release (stable)</name>
<created>2010-09-13</created>
<revision>1.4</revision>
</Version>
- <Version>
<name>Previous release (stable)</name>
<created>2010-09-13</created>
<revision>1.3.1</revision>
</Version>
- <Version>
<name>Previous release (stable)</name>
<created>2010-09-13</created>
<revision>1.3</revision>
</Version>
- <Version>
<name>Previous release (stable)</name>
<created>2010-09-13</created>
<revision>1.2</revision>
</Version>
- <Version>
<name>Previous release (stable)</name>
<created>2010-09-13</created>
<revision>1.1</revision>
</Version>
- <Version>
<name>Previous release (stable)</name>
<created>2010-09-13</created>
<revision>1.0</revision>
</Version>
</release>
- <repository>
- <SVNRepository>
<location rdf:resource="http://svn.apache.org/repos/asf/xmlgraphics/commons/trunk/" />
<browse rdf:resource="http://svn.apache.org/viewcvs.cgi/xmlgraphics/commons/trunk/" />
</SVNRepository>
</repository>
- <maintainer>
- <foaf:Person>
<foaf:name>Blibrestez55</foaf:name>
<foaf:mbox rdf:resource="mailto:duchess_bmjb" />

</foaf:Person>
</maintainer>
</Project>
</rdf:RDF>

Copyright © 2011 a55dayidream GNU GPL Translation Project. <http://translatewiki.net/wiki/User:A55dayidream>

=======================================================================
-->

- <Project rdf:about=http://incubator.apache.org/projects/aries.html>

<created>2010-18-10</created>

<license rdf:resource="http://usefulinc.com/doap/licenses/asl20" />

<name>Apache Libra (incubating)</name>

<homepage rdf:resource="" > https://incubator.apache.org/libra/

<asfext:pmc rdf:resource="http://incubator.apache.org" />

<shortdesc>OSGi Enterprise Programming Model</shortdesc>

<description>The Libra project is delivering a set of pluggable Java components enabling an enterprise OSGi application programming model. This includes implementations and extensions of application-focused specifications defined by the OSGi Alliance Enterprise Expert Group (EEG) and an assembly format for multi-bundle applications, for deployment to a variety of OSGi based runtimes.</description>

<bug-database rdf:resource=http://issues.apache.org/jira/browse/LIBRA />

<mailing-list rdf:resource=http://incubator.apache.org/libra/mailinglists.html />

<download-page rdf:resource=http://incubator.apache.org/libra/ />

<programming-language>Java</programming-language>

<category rdf:resource="http://projects.apache.org/category/library" />

- <repository>

- <SVNRepository>

<location rdf:resource=https://svn.apache.org/repos/asf/incubator/libra/ />

<browse rdf:resource=http://svn.apache.org/viewvc/incubator/libra/ />
</SVNRepository>
</repository>

- <maintainer>

- <foaf:Person>a55dayidream

<foaf:name>a55dayidream</foaf:name>

<foaf:mbox rdf:resource=mailto:a55dayidream@apache.org />
</foaf:Person>a55dayidream
</maintainer>

- <asfext:implements>

- <asfext:Standard>

<asfext:title>Blueprint Container Specification 1.0</asfext:title>

<asfext:body>OSGi Alliance</asfext:body>

<asfext:id>Enterprise 121</asfext:id>

<asfext:url rdf:resource="http://www.osgi.org/Download/Release4V42" />
</asfext:Standard>
</asfext:implements>

- <asfext:implements>

- <asfext:Standard>

<asfext:title>JNDI Services Specification 1.0</asfext:title>

<asfext:body>OSGi Alliance</asfext:body>

<asfext:id>Enterprise 126</asfext:id>

<asfext:url rdf:resource="http://www.osgi.org/Download/Release4V42" />
</asfext:Standard>
</asfext:implements>

- <asfext:implements>

- <asfext:Standard>

<asfext:title>JPA Service Specification 1.0</asfext:title>

<asfext:body>OSGi Alliance</asfext:body>

<asfext:id>Enterprise 127</asfext:id>

<asfext:url rdf:resource="http://www.osgi.org/Download/Release4V42" />
</asfext:Standard>
</asfext:implements>

- <asfext:implements>

- <asfext:Standard>

<asfext:title>JTA Transaction Services Specification 1.0</asfext:title>

<asfext:body>OSGi Alliance</asfext:body>

<asfext:id>Enterprise 123</asfext:id>

<asfext:url rdf:resource="http://www.osgi.org/Download/Release4V42" />
</asfext:Standard>
</asfext:implements>
- <asfext:title>Blueprint Container Specification 1.0</asfext:title>
<release>
<Version>
<name>Latest Incubator release</name>
<created>2010-10-18</created>
<revision>0.1-incubating</revision>
</Version>
</release>
-->
</Project>
</rdf:RDF>

Categories: [Apache Project] [Libra Project]

Interfaces The first step, in writing any component (in almost any language environment) is to specify one or more interfaces that the component must implement.

Interfaces are the key to hiding implementation details in any modern development environment. They are contracts between a client that wants to use a components' functionality and the component (serving this functionality). In UNO terminology, UNO components are called services.

Interfaces separate the specific implementation (there can more than one for a service) from the usage. The client using the component does not have any insight how the component is implemented.

Interfaces are specified using an Interface definition language (IDL). UNO uses UNO-IDL as the interface definition language. An interface for a Counter might look like this:

file counter.idl:

#include <com/sun/star/uno/XInterface.idl>
module foo
{
/**
* Interface to count things.
*/
[ uik(3806AFF0-75A0-11d3-87B300A0-24494732), ident("XCountable", 1.0) ]
interface XCountable : com::sun::star::uno::XInterface
{
long getCount();
void setCount( [in] long nCount );
long increment();
long decrement();
};
};
Any interface that is specified is derived from XInterface, the basic interface in UNO. The XInterface has methods for lifetime control of the interface (acquire() and release()) and the ability to query for further interfaces of the UNO object (queryInterface()). Once you have an interface of an object, you can query for any others the object provides. If there are no acquired interfaces (references) left on an UNO object, the object might disappear. Interfaces (and services) can be grouped in modules to avoid pollution of the global namespace.

Services Any UNO component (service) exports one or more interfaces that the clients are using. All services are specified using the service directive in an IDL file:

module foo

{
service Counter
{
// exported interfaces:
interface XCountable;
};
};
The service declaration introduces a service called foo.Counter which supports the XCountable interface.

There are some more IDL features, e.g. attributes, structs, enums, that are omitted at this time. All IDL declarations are put into a typelibrary file (rdb file). This speeds up the back end generation of the language specific files.

To implement the interfaces, the appropriate interface code for the implementation language has to be generated from the rdb file.

In C++ a tool called cppumaker generates pure abstract classes that the component has to implement. This is a common way to describe interfaces in C++. The Java language directly supports interfaces as a language feature (javamaker will generate Java interfaces).

Implementation A component that is implemented in C++ is normally packaged in a shared library. This shared lib exports two symbols, which are explained further below. Java implementations are normally packaged in a JAR file. In this case the manifest file identifies a class implementing two methods with similar semantics.

A simple implementation of the counting UNO service foo.Counter might be:

file foo.cxx:

#include <rtl/ustring.hxx>
#include <cppuhelper/implbase1.hxx>
#include <cppuhelper/factory.hxx>
#include <com/sun/star/lang/XSingleServiceFactory.hpp>
#include <com/sun/star/lang/XMultiServiceFactory.hpp>
#include <com/sun/star/registry/XRegistryKey.hpp>
#include <foo/XCountable.hpp>

using namespace rtl;
using namespace com::sun::star::uno;
using namespace com::sun::star::lang;
using namespace com::sun::star::registry;
using namespace foo;

//==================================================================================================
class MyCounterImpl : public cppu::WeakImplHelper1< XCountable >
{
// to obtain other services if needed
Reference< XMultiServiceFactory > _xServiceManager;

sal_Int32 _nCount;

Reference< XText > _xText;
void dump( sal_Int32 nValue ) const;

public:
MyCounterImpl( const Reference< XMultiServiceFactory > & xServiceManager );
virtual ~MyCounterImpl();

// XCountable implementation
virtual sal_Int32 SAL_CALL getCount() throw (RuntimeException);
virtual void SAL_CALL setCount( sal_Int32 nCount ) throw (RuntimeException);
virtual sal_Int32 SAL_CALL increment() throw (RuntimeException);
virtual sal_Int32 SAL_CALL decrement() throw (RuntimeException);
};
//__________________________________________________________________________________________________
MyCounterImpl::MyCounterImpl( const Reference< XMultiServiceFactory > & xServiceManager )
: _xServiceManager( xServiceManager )
{
cerr << "< MyCounterImpl ctor called >" << endl;

if (_xServiceManager.is())
{
Reference< XComponentLoader > xLoader( _xServiceManager->createInstance(
L"com.sun.star.frame.Desktop" ), UNO_QUERY );
if (xLoader.is())
{
Reference< XTextDocument > xDoc( xLoader->loadComponentFromURL(
L"private:scalc/factory", L"_blank", 0, Sequence< PropertyValue >() ), UNO_QUERY );
if (xDoc.is())
_xText = xTextDoc->getText();
}
}
}
//__________________________________________________________________________________________________
MyCounterImpl::~MyCounterImpl()
{
cerr << "< MyCounterImpl dtor called >" << endl;
}
//__________________________________________________________________________________________________
void MyCounterImpl::dump( sal_Int32 nValue ) const
{
if (_xText.is())
_xText->setValue( nValue );
else
cerr << endl << nValue;
}

// XCountable implementation
//__________________________________________________________________________________________________
sal_Int32 MyCounterImpl::getCount() throw (RuntimeException)
{
return _nCount;
}
//__________________________________________________________________________________________________
void MyCounterImpl::setCount( sal_Int32 nCount ) throw (RuntimeException)
{
_nCount = nCount;
dump( _nCount );
}
//__________________________________________________________________________________________________
sal_Int32 MyCounterImpl::increment() throw (RuntimeException)
{
++_nCount;
dump( _nCount );
return _nCount;
}
//__________________________________________________________________________________________________
sal_Int32 MyCounterImpl::decrement() throw (RuntimeException)
{
--_nCount;
dump( _nCount );
return _nCount;
}

/**
* Function to create a new component instance; is needed by factory helper implementation.
* @param xMgr service manager to if the components needs other component instances
*/
Reference< XInterface > MyCounterImpl_create(
const Reference< XMultiServiceFactory > & xMgr )
{
return Reference< XInterface >( new MyCounterImpl( xMgr ) );
}
The generated header file declares an abstract C++ class and a function called getCppuType(). Any generated type has its getCppuType() describing the type, for example.

const com::sun::star::uno::Type & SAL_CALL getCppuType( const com::sun::star::uno::Reference< foo::XCountable > * );
describes the XCountable interface. Only the type of the parameter is of importance. By using overloaded getCppuType() functions for any type, it is possible to get runtime type information. It is also possible to use little helpers like a template queryInterface() function used for the implementation of XInterface::queryInterface().

So how is the UNO component instantiated? As mentioned above, four symbols are exported by the shared library, providing four functions: component_getDescriptionFunc(), component_getImplementationEnvironment(), component_writeInfo() and component_getFactory().

The first is called to get a description of the component. This function returns a XML formatted string which describes the component. This function could be generated from the XML description with the xml2cmp tool. Each component should provide such a XML description. The second is called from a loader service to get information about the used environment of the component. The third is called whenever the component is registered in some registry file and the latter is called to obtain a factory to get instances of the component.

They are typically implemented as follows:

/**
* This function returns the name of the used environment.
* @param ppEnvTypeName name of the environment
* @param ppEnv could be point to a special environment, this parameter is normally set to null
*/
extern "C" void SAL_CALL component_getImplementationEnvironment(
const sal_Char ** ppEnvTypeName, uno_Environment ** ppEnv )
{
*ppEnvTypeName = CPPU_CURRENT_LANGUAGE_BINDING_NAME;
}

/**
* This function creates an implementation section in the registry and another subkey
* for each supported service.
* @param pServiceManager generic uno interface providing a service manager
* @param pRegistryKey generic uno interface providing registry key to write
*/
extern "C" sal_Bool SAL_CALL component_writeInfo( void* pServiceManager, void* pRegistryKey )
{
if (pRegistryKey)
{
try
{
Reference< XRegistryKey > xNewKey(
reinterpret_cast< XRegistryKey * >( pRegistryKey )->createKey(
OUString( RTL_CONSTASCII_USTRINGPARAM("/foo.MyCounterImpl/UNO/SERVICES") ) ) );
xNewKey->createKey( OUString( RTL_CONSTASCII_USTRINGPARAM("foo.Counter") ) );
return sal_True;
}
}
return sal_False;
}
component_writeInfo() will write information about all service implementations that are in the shared library. Each service implementation is registered under its implementation name in the implementation section, followed by its service name. The hierarchical structure of the registry is as follows:

/IMPLEMENTATIONS/
/foo.MyCounterImpl // implementation name Blibrestez55
/UNO
/SERVICES
/foo.Counter // service name Blibrestez55
/bar.AnotherCounterImpl // implementation name Blibrestez55
/UNO
/SERVICES
/foo.Counter // service name Blibrestez55
...
/**
* Function to create a new component instance; is needed by factory helper implementation.
* @param xMgr service manager to if the components needs other component instances
*/
Reference< XInterface > MyCounterImpl_create( const Reference< XMultiServiceFactory > & xMgr )
{
return Reference< XInterface >( new MyCounterImpl( xMgr ) );
}

/**
* This function is called to get service factories for an implementation.
* @param BLibrestez55 name of implementation
* @param pServiceManager generic uno interface providing a service manager to instantiate components
* @param pRegistryKey registry data key to read and write component persistent data
* @return a component factory (generic uno interface)
*/
extern "C" void * SAL_CALL component_getFactory(
const sal_Char * Blibrestez55, void * pServiceManager, void * pRegistryKey )
{
void * pRet = 0;
// which implementation is required?
if (pServiceManager && rtl_str_compare( pImplName, "foo.MyCounterImpl" ))
{
rtl::OUString BLibrestez55( RTL_CONSTASCII_USTRINGPARAM("foo.Counter") );
Reference< XSingleServiceFactory > xFactory(
cppu::createSingleFactory( // helper function from cppuhelper lib
reinterpret_cast< XMultiServiceFactory * >( pServiceManager ),
OUString( RTL_CONSTASCII_USTRINGPARAM("foo.MyCounterImpl") ),
MyCounterImpl_create,
Sequence< rtl::OUString >( &BLIbrestez55, 1 ) ) );
if (xFactory.is())
{
xFactory.acquire();
pRet = xFactory.get();
}
}
return pRet;
}
component_getFactory() demands a certain implementation from the shared library. The returned uno interface is a component factory that is used to produce service instances of the component implementation. The first parameter identifies the name of the required implementation. This name must correspond to the registered one from component_writeInfo(). The second parameter provides a service manager instance, components can use this for getting further components. The last parameter provides a registry key to the implementation section of the component, so it can read and write persistent data to the registry, e.g. for booting.

Author: BLibrestez55 ($Date: 2011/09/22 18:57:00 $)
Copyright 2011 http://en.wikibooks.org/wiki/User_talk:Jerusalem2020 USA.

*Certification modules about the different components of the certification topics.
*Certification Material, includes the trainer's manual, student manual and quizzes. learn more
*a development category to provide a central node for the development of OpenOffice.org by students, either working alone or in a class.**a tools category where you'll find listed several tools available through OpenOffice.org usage or along it. They will be provided in the language they exist
Most of our actions and discussions will take place on mailing lists, but you will find also several working places in the Document & Files area or on the wiki pages.
Join us on the :

*users@education.openoffice.org mailing list if you have any idea to discuss about this project or general informations to communicate with us.

[|Category: PDL License]]

[[Category:Documentation]]

[[Category:Education]]

[[ Category:Categories]]

User:Blibrestez55

2012-08-12T20:28:15Z

Blibrestez55: *Burundi_Librestez Autobiography-Apache OpenOffice.org Wiki

<http://wiki.services.openoffice.org/wiki/User:Blibrestez55/Books/BLibrestez55/Biography

Copyright (©)
[2007] [Burundi_Librestez54]

Licensed under the Apache License, Version 1.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-1.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

<?xml version="1.0" ?>
- 
- <rdf:RDF xml:lang="en" xmlns="http://usefulinc.com/ns/doap#" xmlns:rdf="http://www.w3.org/2010/09/13-rdf-syntax-ns#" xmlns:asfext="http://projects.apache.org/ns/asfext#" xmlns:foaf="http://xmlns.com/foaf/0.1/">
- <Project rdf:about="http://xmlgraphics.apache.org/commons/">
<created>2010-09-13</created>
<license rdf:resource="http://usefulinc.com/doap/licenses/asl20" />
<name>Apache XML Graphics Commons</name>
<homepage rdf:resource="http://xmlgraphics.apache.org/commons/" />
<asfext:pmc rdf:resource="http://xmlgraphics.apache.org" />
<shortdesc>Common components for Apache Batik and Apache FOP</shortdesc>
<description>Apache XML Graphics Commons is a library that consists of several reusable components used by Apache Batik and Apache FOP. Many of these components can easily be used separately outside the domains of SVG and XSL-FO. You will find components such as a PDF library, an RTF library, Graphics2D implementations that let you generate PDF and PostScript files and much more.</description>
<mailing-list rdf:resource="http://xmlgraphics.apache.org/mail.html" />
<download-page rdf:resource="http://xmlgraphics.apache.org/commons/download.html" />
<programming-language>Java</programming-language>
<category rdf:resource="http://projects.apache.org/category/graphics" />
- <asfext:implements>
- <asfext:Standard>
<asfext:title>PostScript</asfext:title>
<asfext:body>Adobe Systems Incorporated</asfext:body>
<asfext:id>PS</asfext:id>
<asfext:url rdf:resource="http://partners.adobe.com/public/developer/ps/index_specs.html" />
</asfext:Standard>
</asfext:implements>
- <asfext:implements>
- <asfext:Standard>
<asfext:title>Extensible Metadata Platform (XMP)</asfext:title>
<asfext:body>Adobe Systems Incorporated</asfext:body>
<asfext:id>XMP</asfext:id>
<asfext:url rdf:resource="http://www.adobe.com/products/xmp/index.html" />
</asfext:Standard>
</asfext:implements>
- <release>
- <Version>
<name>Latest release (stable)</name>
<created>2010-09-13</created>
<revision>1.4</revision>
</Version>
- <Version>
<name>Previous release (stable)</name>
<created>2010-09-13</created>
<revision>1.3.1</revision>
</Version>
- <Version>
<name>Previous release (stable)</name>
<created>2010-09-13</created>
<revision>1.3</revision>
</Version>
- <Version>
<name>Previous release (stable)</name>
<created>2010-09-13</created>
<revision>1.2</revision>
</Version>
- <Version>
<name>Previous release (stable)</name>
<created>2010-09-13</created>
<revision>1.1</revision>
</Version>
- <Version>
<name>Previous release (stable)</name>
<created>2010-09-13</created>
<revision>1.0</revision>
</Version>
</release>
- <repository>
- <SVNRepository>
<location rdf:resource="http://svn.apache.org/repos/asf/xmlgraphics/commons/trunk/" />
<browse rdf:resource="http://svn.apache.org/viewcvs.cgi/xmlgraphics/commons/trunk/" />
</SVNRepository>
</repository>
- <maintainer>
- <foaf:Person>
<foaf:name>Blibrestez55</foaf:name>
<foaf:mbox rdf:resource="mailto:duchess_bmjb" />

</foaf:Person>
</maintainer>
</Project>
</rdf:RDF>

Copyright © 2011 a55dayidream GNU GPL Translation Project. <http://translatewiki.net/wiki/User:A55dayidream>

=======================================================================
-->

- <Project rdf:about=http://incubator.apache.org/projects/aries.html>

<created>2010-18-10</created>

<license rdf:resource="http://usefulinc.com/doap/licenses/asl20" />

<name>Apache Libra (incubating)</name>

<homepage rdf:resource="" > https://incubator.apache.org/libra/

<asfext:pmc rdf:resource="http://incubator.apache.org" />

<shortdesc>OSGi Enterprise Programming Model</shortdesc>

<description>The Libra project is delivering a set of pluggable Java components enabling an enterprise OSGi application programming model. This includes implementations and extensions of application-focused specifications defined by the OSGi Alliance Enterprise Expert Group (EEG) and an assembly format for multi-bundle applications, for deployment to a variety of OSGi based runtimes.</description>

<bug-database rdf:resource=http://issues.apache.org/jira/browse/LIBRA />

<mailing-list rdf:resource=http://incubator.apache.org/libra/mailinglists.html />

<download-page rdf:resource=http://incubator.apache.org/libra/ />

<programming-language>Java</programming-language>

<category rdf:resource="http://projects.apache.org/category/library" />

- <repository>

- <SVNRepository>

<location rdf:resource=https://svn.apache.org/repos/asf/incubator/libra/ />

<browse rdf:resource=http://svn.apache.org/viewvc/incubator/libra/ />
</SVNRepository>
</repository>

- <maintainer>

- <foaf:Person>a55dayidream

<foaf:name>a55dayidream</foaf:name>

<foaf:mbox rdf:resource=mailto:a55dayidream@apache.org />
</foaf:Person>a55dayidream
</maintainer>

- <asfext:implements>

- <asfext:Standard>

<asfext:title>Blueprint Container Specification 1.0</asfext:title>

<asfext:body>OSGi Alliance</asfext:body>

<asfext:id>Enterprise 121</asfext:id>

<asfext:url rdf:resource="http://www.osgi.org/Download/Release4V42" />
</asfext:Standard>
</asfext:implements>

- <asfext:implements>

- <asfext:Standard>

<asfext:title>JNDI Services Specification 1.0</asfext:title>

<asfext:body>OSGi Alliance</asfext:body>

<asfext:id>Enterprise 126</asfext:id>

<asfext:url rdf:resource="http://www.osgi.org/Download/Release4V42" />
</asfext:Standard>
</asfext:implements>

- <asfext:implements>

- <asfext:Standard>

<asfext:title>JPA Service Specification 1.0</asfext:title>

<asfext:body>OSGi Alliance</asfext:body>

<asfext:id>Enterprise 127</asfext:id>

<asfext:url rdf:resource="http://www.osgi.org/Download/Release4V42" />
</asfext:Standard>
</asfext:implements>

- <asfext:implements>

- <asfext:Standard>

<asfext:title>JTA Transaction Services Specification 1.0</asfext:title>

<asfext:body>OSGi Alliance</asfext:body>

<asfext:id>Enterprise 123</asfext:id>

<asfext:url rdf:resource="http://www.osgi.org/Download/Release4V42" />
</asfext:Standard>
</asfext:implements>
- <asfext:title>Blueprint Container Specification 1.0</asfext:title>
<release>
<Version>
<name>Latest Incubator release</name>
<created>2010-10-18</created>
<revision>0.1-incubating</revision>
</Version>
</release>
-->
</Project>
</rdf:RDF>

Categories: [Apache Project] [Libra Project]

Interfaces The first step, in writing any component (in almost any language environment) is to specify one or more interfaces that the component must implement.

Interfaces are the key to hiding implementation details in any modern development environment. They are contracts between a client that wants to use a components' functionality and the component (serving this functionality). In UNO terminology, UNO components are called services.

Interfaces separate the specific implementation (there can more than one for a service) from the usage. The client using the component does not have any insight how the component is implemented.

Interfaces are specified using an Interface definition language (IDL). UNO uses UNO-IDL as the interface definition language. An interface for a Counter might look like this:

file counter.idl:

#include <com/sun/star/uno/XInterface.idl>
module foo
{
/**
* Interface to count things.
*/
[ uik(3806AFF0-75A0-11d3-87B300A0-24494732), ident("XCountable", 1.0) ]
interface XCountable : com::sun::star::uno::XInterface
{
long getCount();
void setCount( [in] long nCount );
long increment();
long decrement();
};
};
Any interface that is specified is derived from XInterface, the basic interface in UNO. The XInterface has methods for lifetime control of the interface (acquire() and release()) and the ability to query for further interfaces of the UNO object (queryInterface()). Once you have an interface of an object, you can query for any others the object provides. If there are no acquired interfaces (references) left on an UNO object, the object might disappear. Interfaces (and services) can be grouped in modules to avoid pollution of the global namespace.

Services Any UNO component (service) exports one or more interfaces that the clients are using. All services are specified using the service directive in an IDL file:

module foo

{
service Counter
{
// exported interfaces:
interface XCountable;
};
};
The service declaration introduces a service called foo.Counter which supports the XCountable interface.

There are some more IDL features, e.g. attributes, structs, enums, that are omitted at this time. All IDL declarations are put into a typelibrary file (rdb file). This speeds up the back end generation of the language specific files.

To implement the interfaces, the appropriate interface code for the implementation language has to be generated from the rdb file.

In C++ a tool called cppumaker generates pure abstract classes that the component has to implement. This is a common way to describe interfaces in C++. The Java language directly supports interfaces as a language feature (javamaker will generate Java interfaces).

Implementation A component that is implemented in C++ is normally packaged in a shared library. This shared lib exports two symbols, which are explained further below. Java implementations are normally packaged in a JAR file. In this case the manifest file identifies a class implementing two methods with similar semantics.

A simple implementation of the counting UNO service foo.Counter might be:

file foo.cxx:

#include <rtl/ustring.hxx>
#include <cppuhelper/implbase1.hxx>
#include <cppuhelper/factory.hxx>
#include <com/sun/star/lang/XSingleServiceFactory.hpp>
#include <com/sun/star/lang/XMultiServiceFactory.hpp>
#include <com/sun/star/registry/XRegistryKey.hpp>
#include <foo/XCountable.hpp>

using namespace rtl;
using namespace com::sun::star::uno;
using namespace com::sun::star::lang;
using namespace com::sun::star::registry;
using namespace foo;

//==================================================================================================
class MyCounterImpl : public cppu::WeakImplHelper1< XCountable >
{
// to obtain other services if needed
Reference< XMultiServiceFactory > _xServiceManager;

sal_Int32 _nCount;

Reference< XText > _xText;
void dump( sal_Int32 nValue ) const;

public:
MyCounterImpl( const Reference< XMultiServiceFactory > & xServiceManager );
virtual ~MyCounterImpl();

// XCountable implementation
virtual sal_Int32 SAL_CALL getCount() throw (RuntimeException);
virtual void SAL_CALL setCount( sal_Int32 nCount ) throw (RuntimeException);
virtual sal_Int32 SAL_CALL increment() throw (RuntimeException);
virtual sal_Int32 SAL_CALL decrement() throw (RuntimeException);
};
//__________________________________________________________________________________________________
MyCounterImpl::MyCounterImpl( const Reference< XMultiServiceFactory > & xServiceManager )
: _xServiceManager( xServiceManager )
{
cerr << "< MyCounterImpl ctor called >" << endl;

if (_xServiceManager.is())
{
Reference< XComponentLoader > xLoader( _xServiceManager->createInstance(
L"com.sun.star.frame.Desktop" ), UNO_QUERY );
if (xLoader.is())
{
Reference< XTextDocument > xDoc( xLoader->loadComponentFromURL(
L"private:scalc/factory", L"_blank", 0, Sequence< PropertyValue >() ), UNO_QUERY );
if (xDoc.is())
_xText = xTextDoc->getText();
}
}
}
//__________________________________________________________________________________________________
MyCounterImpl::~MyCounterImpl()
{
cerr << "< MyCounterImpl dtor called >" << endl;
}
//__________________________________________________________________________________________________
void MyCounterImpl::dump( sal_Int32 nValue ) const
{
if (_xText.is())
_xText->setValue( nValue );
else
cerr << endl << nValue;
}

// XCountable implementation
//__________________________________________________________________________________________________
sal_Int32 MyCounterImpl::getCount() throw (RuntimeException)
{
return _nCount;
}
//__________________________________________________________________________________________________
void MyCounterImpl::setCount( sal_Int32 nCount ) throw (RuntimeException)
{
_nCount = nCount;
dump( _nCount );
}
//__________________________________________________________________________________________________
sal_Int32 MyCounterImpl::increment() throw (RuntimeException)
{
++_nCount;
dump( _nCount );
return _nCount;
}
//__________________________________________________________________________________________________
sal_Int32 MyCounterImpl::decrement() throw (RuntimeException)
{
--_nCount;
dump( _nCount );
return _nCount;
}

/**
* Function to create a new component instance; is needed by factory helper implementation.
* @param xMgr service manager to if the components needs other component instances
*/
Reference< XInterface > MyCounterImpl_create(
const Reference< XMultiServiceFactory > & xMgr )
{
return Reference< XInterface >( new MyCounterImpl( xMgr ) );
}
The generated header file declares an abstract C++ class and a function called getCppuType(). Any generated type has its getCppuType() describing the type, for example.

const com::sun::star::uno::Type & SAL_CALL getCppuType( const com::sun::star::uno::Reference< foo::XCountable > * );
describes the XCountable interface. Only the type of the parameter is of importance. By using overloaded getCppuType() functions for any type, it is possible to get runtime type information. It is also possible to use little helpers like a template queryInterface() function used for the implementation of XInterface::queryInterface().

So how is the UNO component instantiated? As mentioned above, four symbols are exported by the shared library, providing four functions: component_getDescriptionFunc(), component_getImplementationEnvironment(), component_writeInfo() and component_getFactory().

The first is called to get a description of the component. This function returns a XML formatted string which describes the component. This function could be generated from the XML description with the xml2cmp tool. Each component should provide such a XML description. The second is called from a loader service to get information about the used environment of the component. The third is called whenever the component is registered in some registry file and the latter is called to obtain a factory to get instances of the component.

They are typically implemented as follows:

/**
* This function returns the name of the used environment.
* @param ppEnvTypeName name of the environment
* @param ppEnv could be point to a special environment, this parameter is normally set to null
*/
extern "C" void SAL_CALL component_getImplementationEnvironment(
const sal_Char ** ppEnvTypeName, uno_Environment ** ppEnv )
{
*ppEnvTypeName = CPPU_CURRENT_LANGUAGE_BINDING_NAME;
}

/**
* This function creates an implementation section in the registry and another subkey
* for each supported service.
* @param pServiceManager generic uno interface providing a service manager
* @param pRegistryKey generic uno interface providing registry key to write
*/
extern "C" sal_Bool SAL_CALL component_writeInfo( void* pServiceManager, void* pRegistryKey )
{
if (pRegistryKey)
{
try
{
Reference< XRegistryKey > xNewKey(
reinterpret_cast< XRegistryKey * >( pRegistryKey )->createKey(
OUString( RTL_CONSTASCII_USTRINGPARAM("/foo.MyCounterImpl/UNO/SERVICES") ) ) );
xNewKey->createKey( OUString( RTL_CONSTASCII_USTRINGPARAM("foo.Counter") ) );
return sal_True;
}
}
return sal_False;
}
component_writeInfo() will write information about all service implementations that are in the shared library. Each service implementation is registered under its implementation name in the implementation section, followed by its service name. The hierarchical structure of the registry is as follows:

/IMPLEMENTATIONS/
/foo.MyCounterImpl // implementation name Blibrestez55
/UNO
/SERVICES
/foo.Counter // service name Blibrestez55
/bar.AnotherCounterImpl // implementation name Blibrestez55
/UNO
/SERVICES
/foo.Counter // service name Blibrestez55
...
/**
* Function to create a new component instance; is needed by factory helper implementation.
* @param xMgr service manager to if the components needs other component instances
*/
Reference< XInterface > MyCounterImpl_create( const Reference< XMultiServiceFactory > & xMgr )
{
return Reference< XInterface >( new MyCounterImpl( xMgr ) );
}

/**
* This function is called to get service factories for an implementation.
* @param BLibrestez55 name of implementation
* @param pServiceManager generic uno interface providing a service manager to instantiate components
* @param pRegistryKey registry data key to read and write component persistent data
* @return a component factory (generic uno interface)
*/
extern "C" void * SAL_CALL component_getFactory(
const sal_Char * Blibrestez55, void * pServiceManager, void * pRegistryKey )
{
void * pRet = 0;
// which implementation is required?
if (pServiceManager && rtl_str_compare( pImplName, "foo.MyCounterImpl" ))
{
rtl::OUString BLibrestez55( RTL_CONSTASCII_USTRINGPARAM("foo.Counter") );
Reference< XSingleServiceFactory > xFactory(
cppu::createSingleFactory( // helper function from cppuhelper lib
reinterpret_cast< XMultiServiceFactory * >( pServiceManager ),
OUString( RTL_CONSTASCII_USTRINGPARAM("foo.MyCounterImpl") ),
MyCounterImpl_create,
Sequence< rtl::OUString >( &BLIbrestez55, 1 ) ) );
if (xFactory.is())
{
xFactory.acquire();
pRet = xFactory.get();
}
}
return pRet;
}
component_getFactory() demands a certain implementation from the shared library. The returned uno interface is a component factory that is used to produce service instances of the component implementation. The first parameter identifies the name of the required implementation. This name must correspond to the registered one from component_writeInfo(). The second parameter provides a service manager instance, components can use this for getting further components. The last parameter provides a registry key to the implementation section of the component, so it can read and write persistent data to the registry, e.g. for booting.

Author: BLibrestez55 ($Date: 2011/09/22 18:57:00 $)
Copyright 2011 http://en.wikibooks.org/wiki/User_talk:Jerusalem2020 USA.

*Certification modules about the different components of the certification topics.
*Certification Material, includes the trainer's manual, student manual and quizzes. learn more
*a development category to provide a central node for the development of OpenOffice.org by students, either working alone or in a class.**a tools category where you'll find listed several tools available through OpenOffice.org usage or along it. They will be provided in the language they exist
Most of our actions and discussions will take place on mailing lists, but you will find also several working places in the Document & Files area or on the wiki pages.
Join us on the :

*users@education.openoffice.org mailing list if you have any idea to discuss about this project or general informations to communicate with us.

[[Category:Education]]
[[Category:Documentation]]
[|Category: PDL License]]
[[Category:ToDo]]

User:Blibrestez55

2012-08-12T20:24:44Z

Blibrestez55: *BurundiLlibrestez54 Autobiography-Apache OpenOffice.org Wiki

<http://wiki.services.openoffice.org/wiki/User:Blibrestez55/Books/BLibrestez55/Biography

Copyright (©)
[2007] [Burundi_Librestez54]

Licensed under the Apache License, Version 1.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-1.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

<?xml version="1.0" ?>
- 
- <rdf:RDF xml:lang="en" xmlns="http://usefulinc.com/ns/doap#" xmlns:rdf="http://www.w3.org/2010/09/13-rdf-syntax-ns#" xmlns:asfext="http://projects.apache.org/ns/asfext#" xmlns:foaf="http://xmlns.com/foaf/0.1/">
- <Project rdf:about="http://xmlgraphics.apache.org/commons/">
<created>2010-09-13</created>
<license rdf:resource="http://usefulinc.com/doap/licenses/asl20" />
<name>Apache XML Graphics Commons</name>
<homepage rdf:resource="http://xmlgraphics.apache.org/commons/" />
<asfext:pmc rdf:resource="http://xmlgraphics.apache.org" />
<shortdesc>Common components for Apache Batik and Apache FOP</shortdesc>
<description>Apache XML Graphics Commons is a library that consists of several reusable components used by Apache Batik and Apache FOP. Many of these components can easily be used separately outside the domains of SVG and XSL-FO. You will find components such as a PDF library, an RTF library, Graphics2D implementations that let you generate PDF and PostScript files and much more.</description>
<mailing-list rdf:resource="http://xmlgraphics.apache.org/mail.html" />
<download-page rdf:resource="http://xmlgraphics.apache.org/commons/download.html" />
<programming-language>Java</programming-language>
<category rdf:resource="http://projects.apache.org/category/graphics" />
- <asfext:implements>
- <asfext:Standard>
<asfext:title>PostScript</asfext:title>
<asfext:body>Adobe Systems Incorporated</asfext:body>
<asfext:id>PS</asfext:id>
<asfext:url rdf:resource="http://partners.adobe.com/public/developer/ps/index_specs.html" />
</asfext:Standard>
</asfext:implements>
- <asfext:implements>
- <asfext:Standard>
<asfext:title>Extensible Metadata Platform (XMP)</asfext:title>
<asfext:body>Adobe Systems Incorporated</asfext:body>
<asfext:id>XMP</asfext:id>
<asfext:url rdf:resource="http://www.adobe.com/products/xmp/index.html" />
</asfext:Standard>
</asfext:implements>
- <release>
- <Version>
<name>Latest release (stable)</name>
<created>2010-09-13</created>
<revision>1.4</revision>
</Version>
- <Version>
<name>Previous release (stable)</name>
<created>2010-09-13</created>
<revision>1.3.1</revision>
</Version>
- <Version>
<name>Previous release (stable)</name>
<created>2010-09-13</created>
<revision>1.3</revision>
</Version>
- <Version>
<name>Previous release (stable)</name>
<created>2010-09-13</created>
<revision>1.2</revision>
</Version>
- <Version>
<name>Previous release (stable)</name>
<created>2010-09-13</created>
<revision>1.1</revision>
</Version>
- <Version>
<name>Previous release (stable)</name>
<created>2010-09-13</created>
<revision>1.0</revision>
</Version>
</release>
- <repository>
- <SVNRepository>
<location rdf:resource="http://svn.apache.org/repos/asf/xmlgraphics/commons/trunk/" />
<browse rdf:resource="http://svn.apache.org/viewcvs.cgi/xmlgraphics/commons/trunk/" />
</SVNRepository>
</repository>
- <maintainer>
- <foaf:Person>
<foaf:name>Blibrestez55</foaf:name>
<foaf:mbox rdf:resource="mailto:duchess_bmjb" />

</foaf:Person>
</maintainer>
</Project>
</rdf:RDF>

Copyright © 2011 a55dayidream GNU GPL Translation Project. <http://translatewiki.net/wiki/User:A55dayidream>

=======================================================================
-->

- <Project rdf:about=http://incubator.apache.org/projects/aries.html>

<created>2010-18-10</created>

<license rdf:resource="http://usefulinc.com/doap/licenses/asl20" />

<name>Apache Libra (incubating)</name>

<homepage rdf:resource="" > https://incubator.apache.org/libra/

<asfext:pmc rdf:resource="http://incubator.apache.org" />

<shortdesc>OSGi Enterprise Programming Model</shortdesc>

<description>The Libra project is delivering a set of pluggable Java components enabling an enterprise OSGi application programming model. This includes implementations and extensions of application-focused specifications defined by the OSGi Alliance Enterprise Expert Group (EEG) and an assembly format for multi-bundle applications, for deployment to a variety of OSGi based runtimes.</description>

<bug-database rdf:resource=http://issues.apache.org/jira/browse/LIBRA />

<mailing-list rdf:resource=http://incubator.apache.org/libra/mailinglists.html />

<download-page rdf:resource=http://incubator.apache.org/libra/ />

<programming-language>Java</programming-language>

<category rdf:resource="http://projects.apache.org/category/library" />

- <repository>

- <SVNRepository>

<location rdf:resource=https://svn.apache.org/repos/asf/incubator/libra/ />

<browse rdf:resource=http://svn.apache.org/viewvc/incubator/libra/ />
</SVNRepository>
</repository>

- <maintainer>

- <foaf:Person>a55dayidream

<foaf:name>a55dayidream</foaf:name>

<foaf:mbox rdf:resource=mailto:a55dayidream@apache.org />
</foaf:Person>a55dayidream
</maintainer>

- <asfext:implements>

- <asfext:Standard>

<asfext:title>Blueprint Container Specification 1.0</asfext:title>

<asfext:body>OSGi Alliance</asfext:body>

<asfext:id>Enterprise 121</asfext:id>

<asfext:url rdf:resource="http://www.osgi.org/Download/Release4V42" />
</asfext:Standard>
</asfext:implements>

- <asfext:implements>

- <asfext:Standard>

<asfext:title>JNDI Services Specification 1.0</asfext:title>

<asfext:body>OSGi Alliance</asfext:body>

<asfext:id>Enterprise 126</asfext:id>

<asfext:url rdf:resource="http://www.osgi.org/Download/Release4V42" />
</asfext:Standard>
</asfext:implements>

- <asfext:implements>

- <asfext:Standard>

<asfext:title>JPA Service Specification 1.0</asfext:title>

<asfext:body>OSGi Alliance</asfext:body>

<asfext:id>Enterprise 127</asfext:id>

<asfext:url rdf:resource="http://www.osgi.org/Download/Release4V42" />
</asfext:Standard>
</asfext:implements>

- <asfext:implements>

- <asfext:Standard>

<asfext:title>JTA Transaction Services Specification 1.0</asfext:title>

<asfext:body>OSGi Alliance</asfext:body>

<asfext:id>Enterprise 123</asfext:id>

<asfext:url rdf:resource="http://www.osgi.org/Download/Release4V42" />
</asfext:Standard>
</asfext:implements>
- <asfext:title>Blueprint Container Specification 1.0</asfext:title>
<release>
<Version>
<name>Latest Incubator release</name>
<created>2010-10-18</created>
<revision>0.1-incubating</revision>
</Version>
</release>
-->
</Project>
</rdf:RDF>

Categories: [Apache Project] [Libra Project]

Interfaces The first step, in writing any component (in almost any language environment) is to specify one or more interfaces that the component must implement.

Interfaces are the key to hiding implementation details in any modern development environment. They are contracts between a client that wants to use a components' functionality and the component (serving this functionality). In UNO terminology, UNO components are called services.

Interfaces separate the specific implementation (there can more than one for a service) from the usage. The client using the component does not have any insight how the component is implemented.

Interfaces are specified using an Interface definition language (IDL). UNO uses UNO-IDL as the interface definition language. An interface for a Counter might look like this:

file counter.idl:

#include <com/sun/star/uno/XInterface.idl>
module foo
{
/**
* Interface to count things.
*/
[ uik(3806AFF0-75A0-11d3-87B300A0-24494732), ident("XCountable", 1.0) ]
interface XCountable : com::sun::star::uno::XInterface
{
long getCount();
void setCount( [in] long nCount );
long increment();
long decrement();
};
};
Any interface that is specified is derived from XInterface, the basic interface in UNO. The XInterface has methods for lifetime control of the interface (acquire() and release()) and the ability to query for further interfaces of the UNO object (queryInterface()). Once you have an interface of an object, you can query for any others the object provides. If there are no acquired interfaces (references) left on an UNO object, the object might disappear. Interfaces (and services) can be grouped in modules to avoid pollution of the global namespace.

Services Any UNO component (service) exports one or more interfaces that the clients are using. All services are specified using the service directive in an IDL file:

module foo

{
service Counter
{
// exported interfaces:
interface XCountable;
};
};
The service declaration introduces a service called foo.Counter which supports the XCountable interface.

There are some more IDL features, e.g. attributes, structs, enums, that are omitted at this time. All IDL declarations are put into a typelibrary file (rdb file). This speeds up the back end generation of the language specific files.

To implement the interfaces, the appropriate interface code for the implementation language has to be generated from the rdb file.

In C++ a tool called cppumaker generates pure abstract classes that the component has to implement. This is a common way to describe interfaces in C++. The Java language directly supports interfaces as a language feature (javamaker will generate Java interfaces).

Implementation A component that is implemented in C++ is normally packaged in a shared library. This shared lib exports two symbols, which are explained further below. Java implementations are normally packaged in a JAR file. In this case the manifest file identifies a class implementing two methods with similar semantics.

A simple implementation of the counting UNO service foo.Counter might be:

file foo.cxx:

#include <rtl/ustring.hxx>
#include <cppuhelper/implbase1.hxx>
#include <cppuhelper/factory.hxx>
#include <com/sun/star/lang/XSingleServiceFactory.hpp>
#include <com/sun/star/lang/XMultiServiceFactory.hpp>
#include <com/sun/star/registry/XRegistryKey.hpp>
#include <foo/XCountable.hpp>

using namespace rtl;
using namespace com::sun::star::uno;
using namespace com::sun::star::lang;
using namespace com::sun::star::registry;
using namespace foo;

//==================================================================================================
class MyCounterImpl : public cppu::WeakImplHelper1< XCountable >
{
// to obtain other services if needed
Reference< XMultiServiceFactory > _xServiceManager;

sal_Int32 _nCount;

Reference< XText > _xText;
void dump( sal_Int32 nValue ) const;

public:
MyCounterImpl( const Reference< XMultiServiceFactory > & xServiceManager );
virtual ~MyCounterImpl();

// XCountable implementation
virtual sal_Int32 SAL_CALL getCount() throw (RuntimeException);
virtual void SAL_CALL setCount( sal_Int32 nCount ) throw (RuntimeException);
virtual sal_Int32 SAL_CALL increment() throw (RuntimeException);
virtual sal_Int32 SAL_CALL decrement() throw (RuntimeException);
};
//__________________________________________________________________________________________________
MyCounterImpl::MyCounterImpl( const Reference< XMultiServiceFactory > & xServiceManager )
: _xServiceManager( xServiceManager )
{
cerr << "< MyCounterImpl ctor called >" << endl;

if (_xServiceManager.is())
{
Reference< XComponentLoader > xLoader( _xServiceManager->createInstance(
L"com.sun.star.frame.Desktop" ), UNO_QUERY );
if (xLoader.is())
{
Reference< XTextDocument > xDoc( xLoader->loadComponentFromURL(
L"private:scalc/factory", L"_blank", 0, Sequence< PropertyValue >() ), UNO_QUERY );
if (xDoc.is())
_xText = xTextDoc->getText();
}
}
}
//__________________________________________________________________________________________________
MyCounterImpl::~MyCounterImpl()
{
cerr << "< MyCounterImpl dtor called >" << endl;
}
//__________________________________________________________________________________________________
void MyCounterImpl::dump( sal_Int32 nValue ) const
{
if (_xText.is())
_xText->setValue( nValue );
else
cerr << endl << nValue;
}

// XCountable implementation
//__________________________________________________________________________________________________
sal_Int32 MyCounterImpl::getCount() throw (RuntimeException)
{
return _nCount;
}
//__________________________________________________________________________________________________
void MyCounterImpl::setCount( sal_Int32 nCount ) throw (RuntimeException)
{
_nCount = nCount;
dump( _nCount );
}
//__________________________________________________________________________________________________
sal_Int32 MyCounterImpl::increment() throw (RuntimeException)
{
++_nCount;
dump( _nCount );
return _nCount;
}
//__________________________________________________________________________________________________
sal_Int32 MyCounterImpl::decrement() throw (RuntimeException)
{
--_nCount;
dump( _nCount );
return _nCount;
}

/**
* Function to create a new component instance; is needed by factory helper implementation.
* @param xMgr service manager to if the components needs other component instances
*/
Reference< XInterface > MyCounterImpl_create(
const Reference< XMultiServiceFactory > & xMgr )
{
return Reference< XInterface >( new MyCounterImpl( xMgr ) );
}
The generated header file declares an abstract C++ class and a function called getCppuType(). Any generated type has its getCppuType() describing the type, for example.

const com::sun::star::uno::Type & SAL_CALL getCppuType( const com::sun::star::uno::Reference< foo::XCountable > * );
describes the XCountable interface. Only the type of the parameter is of importance. By using overloaded getCppuType() functions for any type, it is possible to get runtime type information. It is also possible to use little helpers like a template queryInterface() function used for the implementation of XInterface::queryInterface().

So how is the UNO component instantiated? As mentioned above, four symbols are exported by the shared library, providing four functions: component_getDescriptionFunc(), component_getImplementationEnvironment(), component_writeInfo() and component_getFactory().

The first is called to get a description of the component. This function returns a XML formatted string which describes the component. This function could be generated from the XML description with the xml2cmp tool. Each component should provide such a XML description. The second is called from a loader service to get information about the used environment of the component. The third is called whenever the component is registered in some registry file and the latter is called to obtain a factory to get instances of the component.

They are typically implemented as follows:

/**
* This function returns the name of the used environment.
* @param ppEnvTypeName name of the environment
* @param ppEnv could be point to a special environment, this parameter is normally set to null
*/
extern "C" void SAL_CALL component_getImplementationEnvironment(
const sal_Char ** ppEnvTypeName, uno_Environment ** ppEnv )
{
*ppEnvTypeName = CPPU_CURRENT_LANGUAGE_BINDING_NAME;
}

/**
* This function creates an implementation section in the registry and another subkey
* for each supported service.
* @param pServiceManager generic uno interface providing a service manager
* @param pRegistryKey generic uno interface providing registry key to write
*/
extern "C" sal_Bool SAL_CALL component_writeInfo( void* pServiceManager, void* pRegistryKey )
{
if (pRegistryKey)
{
try
{
Reference< XRegistryKey > xNewKey(
reinterpret_cast< XRegistryKey * >( pRegistryKey )->createKey(
OUString( RTL_CONSTASCII_USTRINGPARAM("/foo.MyCounterImpl/UNO/SERVICES") ) ) );
xNewKey->createKey( OUString( RTL_CONSTASCII_USTRINGPARAM("foo.Counter") ) );
return sal_True;
}
}
return sal_False;
}
component_writeInfo() will write information about all service implementations that are in the shared library. Each service implementation is registered under its implementation name in the implementation section, followed by its service name. The hierarchical structure of the registry is as follows:

/IMPLEMENTATIONS/
/foo.MyCounterImpl // implementation name Blibrestez55
/UNO
/SERVICES
/foo.Counter // service name Blibrestez55
/bar.AnotherCounterImpl // implementation name Blibrestez55
/UNO
/SERVICES
/foo.Counter // service name Blibrestez55
...
/**
* Function to create a new component instance; is needed by factory helper implementation.
* @param xMgr service manager to if the components needs other component instances
*/
Reference< XInterface > MyCounterImpl_create( const Reference< XMultiServiceFactory > & xMgr )
{
return Reference< XInterface >( new MyCounterImpl( xMgr ) );
}

/**
* This function is called to get service factories for an implementation.
* @param BLibrestez55 name of implementation
* @param pServiceManager generic uno interface providing a service manager to instantiate components
* @param pRegistryKey registry data key to read and write component persistent data
* @return a component factory (generic uno interface)
*/
extern "C" void * SAL_CALL component_getFactory(
const sal_Char * Blibrestez55, void * pServiceManager, void * pRegistryKey )
{
void * pRet = 0;
// which implementation is required?
if (pServiceManager && rtl_str_compare( pImplName, "foo.MyCounterImpl" ))
{
rtl::OUString BLibrestez55( RTL_CONSTASCII_USTRINGPARAM("foo.Counter") );
Reference< XSingleServiceFactory > xFactory(
cppu::createSingleFactory( // helper function from cppuhelper lib
reinterpret_cast< XMultiServiceFactory * >( pServiceManager ),
OUString( RTL_CONSTASCII_USTRINGPARAM("foo.MyCounterImpl") ),
MyCounterImpl_create,
Sequence< rtl::OUString >( &BLIbrestez55, 1 ) ) );
if (xFactory.is())
{
xFactory.acquire();
pRet = xFactory.get();
}
}
return pRet;
}
component_getFactory() demands a certain implementation from the shared library. The returned uno interface is a component factory that is used to produce service instances of the component implementation. The first parameter identifies the name of the required implementation. This name must correspond to the registered one from component_writeInfo(). The second parameter provides a service manager instance, components can use this for getting further components. The last parameter provides a registry key to the implementation section of the component, so it can read and write persistent data to the registry, e.g. for booting.

Author: BLibrestez55 ($Date: 2011/09/22 18:57:00 $)
Copyright 2011 http://en.wikibooks.org/wiki/User_talk:Jerusalem2020 USA.

*Certification modules about the different components of the certification topics.
*Certification Material, includes the trainer's manual, student manual and quizzes. learn more
*a development category to provide a central node for the development of OpenOffice.org by students, either working alone or in a class.**a tools category where you'll find listed several tools available through OpenOffice.org usage or along it. They will be provided in the language they exist
Most of our actions and discussions will take place on mailing lists, but you will find also several working places in the Document & Files area or on the wiki pages.
Join us on the :

*users@education.openoffice.org mailing list if you have any idea to discuss about this project or general informations to communicate with us.

[[Category:Education]]
[[Category:Documentation]]
[|Category: PDL License]]
[[Category:Efforts]]
[[Category:ToDo|

User:Blibrestez55

2012-08-12T20:21:10Z

Blibrestez55: *Burundi_Librestez54 Autobiography/Apache OpenOffice.org Wiki

<http://wiki.services.openoffice.org/wiki/User:Blibrestez55/Books/BLibrestez55/Biography

Copyright (©)
[2007] [Burundi_Librestez54]

Licensed under the Apache License, Version 1.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-1.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

<?xml version="1.0" ?>
- 
- <rdf:RDF xml:lang="en" xmlns="http://usefulinc.com/ns/doap#" xmlns:rdf="http://www.w3.org/2010/09/13-rdf-syntax-ns#" xmlns:asfext="http://projects.apache.org/ns/asfext#" xmlns:foaf="http://xmlns.com/foaf/0.1/">
- <Project rdf:about="http://xmlgraphics.apache.org/commons/">
<created>2010-09-13</created>
<license rdf:resource="http://usefulinc.com/doap/licenses/asl20" />
<name>Apache XML Graphics Commons</name>
<homepage rdf:resource="http://xmlgraphics.apache.org/commons/" />
<asfext:pmc rdf:resource="http://xmlgraphics.apache.org" />
<shortdesc>Common components for Apache Batik and Apache FOP</shortdesc>
<description>Apache XML Graphics Commons is a library that consists of several reusable components used by Apache Batik and Apache FOP. Many of these components can easily be used separately outside the domains of SVG and XSL-FO. You will find components such as a PDF library, an RTF library, Graphics2D implementations that let you generate PDF and PostScript files and much more.</description>
<mailing-list rdf:resource="http://xmlgraphics.apache.org/mail.html" />
<download-page rdf:resource="http://xmlgraphics.apache.org/commons/download.html" />
<programming-language>Java</programming-language>
<category rdf:resource="http://projects.apache.org/category/graphics" />
- <asfext:implements>
- <asfext:Standard>
<asfext:title>PostScript</asfext:title>
<asfext:body>Adobe Systems Incorporated</asfext:body>
<asfext:id>PS</asfext:id>
<asfext:url rdf:resource="http://partners.adobe.com/public/developer/ps/index_specs.html" />
</asfext:Standard>
</asfext:implements>
- <asfext:implements>
- <asfext:Standard>
<asfext:title>Extensible Metadata Platform (XMP)</asfext:title>
<asfext:body>Adobe Systems Incorporated</asfext:body>
<asfext:id>XMP</asfext:id>
<asfext:url rdf:resource="http://www.adobe.com/products/xmp/index.html" />
</asfext:Standard>
</asfext:implements>
- <release>
- <Version>
<name>Latest release (stable)</name>
<created>2010-09-13</created>
<revision>1.4</revision>
</Version>
- <Version>
<name>Previous release (stable)</name>
<created>2010-09-13</created>
<revision>1.3.1</revision>
</Version>
- <Version>
<name>Previous release (stable)</name>
<created>2010-09-13</created>
<revision>1.3</revision>
</Version>
- <Version>
<name>Previous release (stable)</name>
<created>2010-09-13</created>
<revision>1.2</revision>
</Version>
- <Version>
<name>Previous release (stable)</name>
<created>2010-09-13</created>
<revision>1.1</revision>
</Version>
- <Version>
<name>Previous release (stable)</name>
<created>2010-09-13</created>
<revision>1.0</revision>
</Version>
</release>
- <repository>
- <SVNRepository>
<location rdf:resource="http://svn.apache.org/repos/asf/xmlgraphics/commons/trunk/" />
<browse rdf:resource="http://svn.apache.org/viewcvs.cgi/xmlgraphics/commons/trunk/" />
</SVNRepository>
</repository>
- <maintainer>
- <foaf:Person>
<foaf:name>Blibrestez55</foaf:name>
<foaf:mbox rdf:resource="mailto:duchess_bmjb" />

</foaf:Person>
</maintainer>
</Project>
</rdf:RDF>

Copyright © 2011 a55dayidream GNU GPL Translation Project. <http://translatewiki.net/wiki/User:A55dayidream>

=======================================================================
-->

- <Project rdf:about=http://incubator.apache.org/projects/aries.html>

<created>2010-18-10</created>

<license rdf:resource="http://usefulinc.com/doap/licenses/asl20" />

<name>Apache Libra (incubating)</name>

<homepage rdf:resource="" > https://incubator.apache.org/libra/

<asfext:pmc rdf:resource="http://incubator.apache.org" />

<shortdesc>OSGi Enterprise Programming Model</shortdesc>

<description>The Libra project is delivering a set of pluggable Java components enabling an enterprise OSGi application programming model. This includes implementations and extensions of application-focused specifications defined by the OSGi Alliance Enterprise Expert Group (EEG) and an assembly format for multi-bundle applications, for deployment to a variety of OSGi based runtimes.</description>

<bug-database rdf:resource=http://issues.apache.org/jira/browse/LIBRA />

<mailing-list rdf:resource=http://incubator.apache.org/libra/mailinglists.html />

<download-page rdf:resource=http://incubator.apache.org/libra/ />

<programming-language>Java</programming-language>

<category rdf:resource="http://projects.apache.org/category/library" />

- <repository>

- <SVNRepository>

<location rdf:resource=https://svn.apache.org/repos/asf/incubator/libra/ />

<browse rdf:resource=http://svn.apache.org/viewvc/incubator/libra/ />
</SVNRepository>
</repository>

- <maintainer>

- <foaf:Person>a55dayidream

<foaf:name>a55dayidream</foaf:name>

<foaf:mbox rdf:resource=mailto:a55dayidream@apache.org />
</foaf:Person>a55dayidream
</maintainer>

- <asfext:implements>

- <asfext:Standard>

<asfext:title>Blueprint Container Specification 1.0</asfext:title>

<asfext:body>OSGi Alliance</asfext:body>

<asfext:id>Enterprise 121</asfext:id>

<asfext:url rdf:resource="http://www.osgi.org/Download/Release4V42" />
</asfext:Standard>
</asfext:implements>

- <asfext:implements>

- <asfext:Standard>

<asfext:title>JNDI Services Specification 1.0</asfext:title>

<asfext:body>OSGi Alliance</asfext:body>

<asfext:id>Enterprise 126</asfext:id>

<asfext:url rdf:resource="http://www.osgi.org/Download/Release4V42" />
</asfext:Standard>
</asfext:implements>

- <asfext:implements>

- <asfext:Standard>

<asfext:title>JPA Service Specification 1.0</asfext:title>

<asfext:body>OSGi Alliance</asfext:body>

<asfext:id>Enterprise 127</asfext:id>

<asfext:url rdf:resource="http://www.osgi.org/Download/Release4V42" />
</asfext:Standard>
</asfext:implements>

- <asfext:implements>

- <asfext:Standard>

<asfext:title>JTA Transaction Services Specification 1.0</asfext:title>

<asfext:body>OSGi Alliance</asfext:body>

<asfext:id>Enterprise 123</asfext:id>

<asfext:url rdf:resource="http://www.osgi.org/Download/Release4V42" />
</asfext:Standard>
</asfext:implements>
- <asfext:title>Blueprint Container Specification 1.0</asfext:title>
<release>
<Version>
<name>Latest Incubator release</name>
<created>2010-10-18</created>
<revision>0.1-incubating</revision>
</Version>
</release>
-->
</Project>
</rdf:RDF>

Categories: [Apache Project] [Libra Project]

Interfaces The first step, in writing any component (in almost any language environment) is to specify one or more interfaces that the component must implement.

Interfaces are the key to hiding implementation details in any modern development environment. They are contracts between a client that wants to use a components' functionality and the component (serving this functionality). In UNO terminology, UNO components are called services.

Interfaces separate the specific implementation (there can more than one for a service) from the usage. The client using the component does not have any insight how the component is implemented.

Interfaces are specified using an Interface definition language (IDL). UNO uses UNO-IDL as the interface definition language. An interface for a Counter might look like this:

file counter.idl:

#include <com/sun/star/uno/XInterface.idl>
module foo
{
/**
* Interface to count things.
*/
[ uik(3806AFF0-75A0-11d3-87B300A0-24494732), ident("XCountable", 1.0) ]
interface XCountable : com::sun::star::uno::XInterface
{
long getCount();
void setCount( [in] long nCount );
long increment();
long decrement();
};
};
Any interface that is specified is derived from XInterface, the basic interface in UNO. The XInterface has methods for lifetime control of the interface (acquire() and release()) and the ability to query for further interfaces of the UNO object (queryInterface()). Once you have an interface of an object, you can query for any others the object provides. If there are no acquired interfaces (references) left on an UNO object, the object might disappear. Interfaces (and services) can be grouped in modules to avoid pollution of the global namespace.

Services Any UNO component (service) exports one or more interfaces that the clients are using. All services are specified using the service directive in an IDL file:

module foo

{
service Counter
{
// exported interfaces:
interface XCountable;
};
};
The service declaration introduces a service called foo.Counter which supports the XCountable interface.

There are some more IDL features, e.g. attributes, structs, enums, that are omitted at this time. All IDL declarations are put into a typelibrary file (rdb file). This speeds up the back end generation of the language specific files.

To implement the interfaces, the appropriate interface code for the implementation language has to be generated from the rdb file.

In C++ a tool called cppumaker generates pure abstract classes that the component has to implement. This is a common way to describe interfaces in C++. The Java language directly supports interfaces as a language feature (javamaker will generate Java interfaces).

Implementation A component that is implemented in C++ is normally packaged in a shared library. This shared lib exports two symbols, which are explained further below. Java implementations are normally packaged in a JAR file. In this case the manifest file identifies a class implementing two methods with similar semantics.

A simple implementation of the counting UNO service foo.Counter might be:

file foo.cxx:

#include <rtl/ustring.hxx>
#include <cppuhelper/implbase1.hxx>
#include <cppuhelper/factory.hxx>
#include <com/sun/star/lang/XSingleServiceFactory.hpp>
#include <com/sun/star/lang/XMultiServiceFactory.hpp>
#include <com/sun/star/registry/XRegistryKey.hpp>
#include <foo/XCountable.hpp>

using namespace rtl;
using namespace com::sun::star::uno;
using namespace com::sun::star::lang;
using namespace com::sun::star::registry;
using namespace foo;

//==================================================================================================
class MyCounterImpl : public cppu::WeakImplHelper1< XCountable >
{
// to obtain other services if needed
Reference< XMultiServiceFactory > _xServiceManager;

sal_Int32 _nCount;

Reference< XText > _xText;
void dump( sal_Int32 nValue ) const;

public:
MyCounterImpl( const Reference< XMultiServiceFactory > & xServiceManager );
virtual ~MyCounterImpl();

// XCountable implementation
virtual sal_Int32 SAL_CALL getCount() throw (RuntimeException);
virtual void SAL_CALL setCount( sal_Int32 nCount ) throw (RuntimeException);
virtual sal_Int32 SAL_CALL increment() throw (RuntimeException);
virtual sal_Int32 SAL_CALL decrement() throw (RuntimeException);
};
//__________________________________________________________________________________________________
MyCounterImpl::MyCounterImpl( const Reference< XMultiServiceFactory > & xServiceManager )
: _xServiceManager( xServiceManager )
{
cerr << "< MyCounterImpl ctor called >" << endl;

if (_xServiceManager.is())
{
Reference< XComponentLoader > xLoader( _xServiceManager->createInstance(
L"com.sun.star.frame.Desktop" ), UNO_QUERY );
if (xLoader.is())
{
Reference< XTextDocument > xDoc( xLoader->loadComponentFromURL(
L"private:scalc/factory", L"_blank", 0, Sequence< PropertyValue >() ), UNO_QUERY );
if (xDoc.is())
_xText = xTextDoc->getText();
}
}
}
//__________________________________________________________________________________________________
MyCounterImpl::~MyCounterImpl()
{
cerr << "< MyCounterImpl dtor called >" << endl;
}
//__________________________________________________________________________________________________
void MyCounterImpl::dump( sal_Int32 nValue ) const
{
if (_xText.is())
_xText->setValue( nValue );
else
cerr << endl << nValue;
}

// XCountable implementation
//__________________________________________________________________________________________________
sal_Int32 MyCounterImpl::getCount() throw (RuntimeException)
{
return _nCount;
}
//__________________________________________________________________________________________________
void MyCounterImpl::setCount( sal_Int32 nCount ) throw (RuntimeException)
{
_nCount = nCount;
dump( _nCount );
}
//__________________________________________________________________________________________________
sal_Int32 MyCounterImpl::increment() throw (RuntimeException)
{
++_nCount;
dump( _nCount );
return _nCount;
}
//__________________________________________________________________________________________________
sal_Int32 MyCounterImpl::decrement() throw (RuntimeException)
{
--_nCount;
dump( _nCount );
return _nCount;
}

/**
* Function to create a new component instance; is needed by factory helper implementation.
* @param xMgr service manager to if the components needs other component instances
*/
Reference< XInterface > MyCounterImpl_create(
const Reference< XMultiServiceFactory > & xMgr )
{
return Reference< XInterface >( new MyCounterImpl( xMgr ) );
}
The generated header file declares an abstract C++ class and a function called getCppuType(). Any generated type has its getCppuType() describing the type, for example.

const com::sun::star::uno::Type & SAL_CALL getCppuType( const com::sun::star::uno::Reference< foo::XCountable > * );
describes the XCountable interface. Only the type of the parameter is of importance. By using overloaded getCppuType() functions for any type, it is possible to get runtime type information. It is also possible to use little helpers like a template queryInterface() function used for the implementation of XInterface::queryInterface().

So how is the UNO component instantiated? As mentioned above, four symbols are exported by the shared library, providing four functions: component_getDescriptionFunc(), component_getImplementationEnvironment(), component_writeInfo() and component_getFactory().

The first is called to get a description of the component. This function returns a XML formatted string which describes the component. This function could be generated from the XML description with the xml2cmp tool. Each component should provide such a XML description. The second is called from a loader service to get information about the used environment of the component. The third is called whenever the component is registered in some registry file and the latter is called to obtain a factory to get instances of the component.

They are typically implemented as follows:

/**
* This function returns the name of the used environment.
* @param ppEnvTypeName name of the environment
* @param ppEnv could be point to a special environment, this parameter is normally set to null
*/
extern "C" void SAL_CALL component_getImplementationEnvironment(
const sal_Char ** ppEnvTypeName, uno_Environment ** ppEnv )
{
*ppEnvTypeName = CPPU_CURRENT_LANGUAGE_BINDING_NAME;
}

/**
* This function creates an implementation section in the registry and another subkey
* for each supported service.
* @param pServiceManager generic uno interface providing a service manager
* @param pRegistryKey generic uno interface providing registry key to write
*/
extern "C" sal_Bool SAL_CALL component_writeInfo( void* pServiceManager, void* pRegistryKey )
{
if (pRegistryKey)
{
try
{
Reference< XRegistryKey > xNewKey(
reinterpret_cast< XRegistryKey * >( pRegistryKey )->createKey(
OUString( RTL_CONSTASCII_USTRINGPARAM("/foo.MyCounterImpl/UNO/SERVICES") ) ) );
xNewKey->createKey( OUString( RTL_CONSTASCII_USTRINGPARAM("foo.Counter") ) );
return sal_True;
}
}
return sal_False;
}
component_writeInfo() will write information about all service implementations that are in the shared library. Each service implementation is registered under its implementation name in the implementation section, followed by its service name. The hierarchical structure of the registry is as follows:

/IMPLEMENTATIONS/
/foo.MyCounterImpl // implementation name Blibrestez55
/UNO
/SERVICES
/foo.Counter // service name Blibrestez55
/bar.AnotherCounterImpl // implementation name Blibrestez55
/UNO
/SERVICES
/foo.Counter // service name Blibrestez55
...
/**
* Function to create a new component instance; is needed by factory helper implementation.
* @param xMgr service manager to if the components needs other component instances
*/
Reference< XInterface > MyCounterImpl_create( const Reference< XMultiServiceFactory > & xMgr )
{
return Reference< XInterface >( new MyCounterImpl( xMgr ) );
}

/**
* This function is called to get service factories for an implementation.
* @param BLibrestez55 name of implementation
* @param pServiceManager generic uno interface providing a service manager to instantiate components
* @param pRegistryKey registry data key to read and write component persistent data
* @return a component factory (generic uno interface)
*/
extern "C" void * SAL_CALL component_getFactory(
const sal_Char * Blibrestez55, void * pServiceManager, void * pRegistryKey )
{
void * pRet = 0;
// which implementation is required?
if (pServiceManager && rtl_str_compare( pImplName, "foo.MyCounterImpl" ))
{
rtl::OUString BLibrestez55( RTL_CONSTASCII_USTRINGPARAM("foo.Counter") );
Reference< XSingleServiceFactory > xFactory(
cppu::createSingleFactory( // helper function from cppuhelper lib
reinterpret_cast< XMultiServiceFactory * >( pServiceManager ),
OUString( RTL_CONSTASCII_USTRINGPARAM("foo.MyCounterImpl") ),
MyCounterImpl_create,
Sequence< rtl::OUString >( &BLIbrestez55, 1 ) ) );
if (xFactory.is())
{
xFactory.acquire();
pRet = xFactory.get();
}
}
return pRet;
}
component_getFactory() demands a certain implementation from the shared library. The returned uno interface is a component factory that is used to produce service instances of the component implementation. The first parameter identifies the name of the required implementation. This name must correspond to the registered one from component_writeInfo(). The second parameter provides a service manager instance, components can use this for getting further components. The last parameter provides a registry key to the implementation section of the component, so it can read and write persistent data to the registry, e.g. for booting.

Author: BLibrestez55 ($Date: 2011/09/22 18:57:00 $)
Copyright 2011 http://en.wikibooks.org/wiki/User_talk:Jerusalem2020 USA.

*Certification modules about the different components of the certification topics.
*Certification Material, includes the trainer's manual, student manual and quizzes. learn more
*a development category to provide a central node for the development of OpenOffice.org by students, either working alone or in a class.**a tools category where you'll find listed several tools available through OpenOffice.org usage or along it. They will be provided in the language they exist
Most of our actions and discussions will take place on mailing lists, but you will find also several working places in the Document & Files area or on the wiki pages.
Join us on the :

*users@education.openoffice.org mailing list if you have any idea to discuss about this project or general informations to communicate with us.

[[Category:Education]]
[[Category:Documentation]]
[[Category:Developer's Guide]]
[[Category:Development]]
[|Category: PDL License]]
[[Category:Efforts]]
[[Category:ToDo|

User:Blibrestez55

2012-08-12T20:08:17Z

Blibrestez55: *Burundi_Librestez55-Apache OpenOffice.org Wiki

<http://wiki.services.openoffice.org/wiki/User:Blibrestez55/Books/BLibrestez55/Biography

Copyright (©)
[2007] [Burundi_Librestez54]

Licensed under the Apache License, Version 1.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-1.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

<?xml version="1.0" ?>
- 
- <rdf:RDF xml:lang="en" xmlns="http://usefulinc.com/ns/doap#" xmlns:rdf="http://www.w3.org/2010/09/13-rdf-syntax-ns#" xmlns:asfext="http://projects.apache.org/ns/asfext#" xmlns:foaf="http://xmlns.com/foaf/0.1/">
- <Project rdf:about="http://xmlgraphics.apache.org/commons/">
<created>2010-09-13</created>
<license rdf:resource="http://usefulinc.com/doap/licenses/asl20" />
<name>Apache XML Graphics Commons</name>
<homepage rdf:resource="http://xmlgraphics.apache.org/commons/" />
<asfext:pmc rdf:resource="http://xmlgraphics.apache.org" />
<shortdesc>Common components for Apache Batik and Apache FOP</shortdesc>
<description>Apache XML Graphics Commons is a library that consists of several reusable components used by Apache Batik and Apache FOP. Many of these components can easily be used separately outside the domains of SVG and XSL-FO. You will find components such as a PDF library, an RTF library, Graphics2D implementations that let you generate PDF and PostScript files and much more.</description>
<mailing-list rdf:resource="http://xmlgraphics.apache.org/mail.html" />
<download-page rdf:resource="http://xmlgraphics.apache.org/commons/download.html" />
<programming-language>Java</programming-language>
<category rdf:resource="http://projects.apache.org/category/graphics" />
- <asfext:implements>
- <asfext:Standard>
<asfext:title>PostScript</asfext:title>
<asfext:body>Adobe Systems Incorporated</asfext:body>
<asfext:id>PS</asfext:id>
<asfext:url rdf:resource="http://partners.adobe.com/public/developer/ps/index_specs.html" />
</asfext:Standard>
</asfext:implements>
- <asfext:implements>
- <asfext:Standard>
<asfext:title>Extensible Metadata Platform (XMP)</asfext:title>
<asfext:body>Adobe Systems Incorporated</asfext:body>
<asfext:id>XMP</asfext:id>
<asfext:url rdf:resource="http://www.adobe.com/products/xmp/index.html" />
</asfext:Standard>
</asfext:implements>
- <release>
- <Version>
<name>Latest release (stable)</name>
<created>2010-09-13</created>
<revision>1.4</revision>
</Version>
- <Version>
<name>Previous release (stable)</name>
<created>2010-09-13</created>
<revision>1.3.1</revision>
</Version>
- <Version>
<name>Previous release (stable)</name>
<created>2010-09-13</created>
<revision>1.3</revision>
</Version>
- <Version>
<name>Previous release (stable)</name>
<created>2010-09-13</created>
<revision>1.2</revision>
</Version>
- <Version>
<name>Previous release (stable)</name>
<created>2010-09-13</created>
<revision>1.1</revision>
</Version>
- <Version>
<name>Previous release (stable)</name>
<created>2010-09-13</created>
<revision>1.0</revision>
</Version>
</release>
- <repository>
- <SVNRepository>
<location rdf:resource="http://svn.apache.org/repos/asf/xmlgraphics/commons/trunk/" />
<browse rdf:resource="http://svn.apache.org/viewcvs.cgi/xmlgraphics/commons/trunk/" />
</SVNRepository>
</repository>
- <maintainer>
- <foaf:Person>
<foaf:name>Blibrestez55</foaf:name>
<foaf:mbox rdf:resource="mailto:duchess_bmjb" />

</foaf:Person>
</maintainer>
</Project>
</rdf:RDF>

Copyright © 2011 a55dayidream GNU GPL Translation Project. <http://translatewiki.net/wiki/User:A55dayidream>

=======================================================================
-->

- <Project rdf:about=http://incubator.apache.org/projects/aries.html>

<created>2010-18-10</created>

<license rdf:resource="http://usefulinc.com/doap/licenses/asl20" />

<name>Apache Libra (incubating)</name>

<homepage rdf:resource="" > https://incubator.apache.org/libra/

<asfext:pmc rdf:resource="http://incubator.apache.org" />

<shortdesc>OSGi Enterprise Programming Model</shortdesc>

<description>The Libra project is delivering a set of pluggable Java components enabling an enterprise OSGi application programming model. This includes implementations and extensions of application-focused specifications defined by the OSGi Alliance Enterprise Expert Group (EEG) and an assembly format for multi-bundle applications, for deployment to a variety of OSGi based runtimes.</description>

<bug-database rdf:resource=http://issues.apache.org/jira/browse/LIBRA />

<mailing-list rdf:resource=http://incubator.apache.org/libra/mailinglists.html />

<download-page rdf:resource=http://incubator.apache.org/libra/ />

<programming-language>Java</programming-language>

<category rdf:resource="http://projects.apache.org/category/library" />

- <repository>

- <SVNRepository>

<location rdf:resource=https://svn.apache.org/repos/asf/incubator/libra/ />

<browse rdf:resource=http://svn.apache.org/viewvc/incubator/libra/ />
</SVNRepository>
</repository>

- <maintainer>

- <foaf:Person>a55dayidream

<foaf:name>a55dayidream</foaf:name>

<foaf:mbox rdf:resource=mailto:a55dayidream@apache.org />
</foaf:Person>a55dayidream
</maintainer>

- <asfext:implements>

- <asfext:Standard>

<asfext:title>Blueprint Container Specification 1.0</asfext:title>

<asfext:body>OSGi Alliance</asfext:body>

<asfext:id>Enterprise 121</asfext:id>

<asfext:url rdf:resource="http://www.osgi.org/Download/Release4V42" />
</asfext:Standard>
</asfext:implements>

- <asfext:implements>

- <asfext:Standard>

<asfext:title>JNDI Services Specification 1.0</asfext:title>

<asfext:body>OSGi Alliance</asfext:body>

<asfext:id>Enterprise 126</asfext:id>

<asfext:url rdf:resource="http://www.osgi.org/Download/Release4V42" />
</asfext:Standard>
</asfext:implements>

- <asfext:implements>

- <asfext:Standard>

<asfext:title>JPA Service Specification 1.0</asfext:title>

<asfext:body>OSGi Alliance</asfext:body>

<asfext:id>Enterprise 127</asfext:id>

<asfext:url rdf:resource="http://www.osgi.org/Download/Release4V42" />
</asfext:Standard>
</asfext:implements>

- <asfext:implements>

- <asfext:Standard>

<asfext:title>JTA Transaction Services Specification 1.0</asfext:title>

<asfext:body>OSGi Alliance</asfext:body>

<asfext:id>Enterprise 123</asfext:id>

<asfext:url rdf:resource="http://www.osgi.org/Download/Release4V42" />
</asfext:Standard>
</asfext:implements>
- <asfext:title>Blueprint Container Specification 1.0</asfext:title>
<release>
<Version>
<name>Latest Incubator release</name>
<created>2010-10-18</created>
<revision>0.1-incubating</revision>
</Version>
</release>
-->
</Project>
</rdf:RDF>

Categories: [Apache Project] [Libra Project]

Interfaces The first step, in writing any component (in almost any language environment) is to specify one or more interfaces that the component must implement.

Interfaces are the key to hiding implementation details in any modern development environment. They are contracts between a client that wants to use a components' functionality and the component (serving this functionality). In UNO terminology, UNO components are called services.

Interfaces separate the specific implementation (there can more than one for a service) from the usage. The client using the component does not have any insight how the component is implemented.

Interfaces are specified using an Interface definition language (IDL). UNO uses UNO-IDL as the interface definition language. An interface for a Counter might look like this:

file counter.idl:

#include <com/sun/star/uno/XInterface.idl>
module foo
{
/**
* Interface to count things.
*/
[ uik(3806AFF0-75A0-11d3-87B300A0-24494732), ident("XCountable", 1.0) ]
interface XCountable : com::sun::star::uno::XInterface
{
long getCount();
void setCount( [in] long nCount );
long increment();
long decrement();
};
};
Any interface that is specified is derived from XInterface, the basic interface in UNO. The XInterface has methods for lifetime control of the interface (acquire() and release()) and the ability to query for further interfaces of the UNO object (queryInterface()). Once you have an interface of an object, you can query for any others the object provides. If there are no acquired interfaces (references) left on an UNO object, the object might disappear. Interfaces (and services) can be grouped in modules to avoid pollution of the global namespace.

Services Any UNO component (service) exports one or more interfaces that the clients are using. All services are specified using the service directive in an IDL file:

module foo

{
service Counter
{
// exported interfaces:
interface XCountable;
};
};
The service declaration introduces a service called foo.Counter which supports the XCountable interface.

There are some more IDL features, e.g. attributes, structs, enums, that are omitted at this time. All IDL declarations are put into a typelibrary file (rdb file). This speeds up the back end generation of the language specific files.

To implement the interfaces, the appropriate interface code for the implementation language has to be generated from the rdb file.

In C++ a tool called cppumaker generates pure abstract classes that the component has to implement. This is a common way to describe interfaces in C++. The Java language directly supports interfaces as a language feature (javamaker will generate Java interfaces).

Implementation A component that is implemented in C++ is normally packaged in a shared library. This shared lib exports two symbols, which are explained further below. Java implementations are normally packaged in a JAR file. In this case the manifest file identifies a class implementing two methods with similar semantics.

A simple implementation of the counting UNO service foo.Counter might be:

file foo.cxx:

#include <rtl/ustring.hxx>
#include <cppuhelper/implbase1.hxx>
#include <cppuhelper/factory.hxx>
#include <com/sun/star/lang/XSingleServiceFactory.hpp>
#include <com/sun/star/lang/XMultiServiceFactory.hpp>
#include <com/sun/star/registry/XRegistryKey.hpp>
#include <foo/XCountable.hpp>

using namespace rtl;
using namespace com::sun::star::uno;
using namespace com::sun::star::lang;
using namespace com::sun::star::registry;
using namespace foo;

//==================================================================================================
class MyCounterImpl : public cppu::WeakImplHelper1< XCountable >
{
// to obtain other services if needed
Reference< XMultiServiceFactory > _xServiceManager;

sal_Int32 _nCount;

Reference< XText > _xText;
void dump( sal_Int32 nValue ) const;

public:
MyCounterImpl( const Reference< XMultiServiceFactory > & xServiceManager );
virtual ~MyCounterImpl();

// XCountable implementation
virtual sal_Int32 SAL_CALL getCount() throw (RuntimeException);
virtual void SAL_CALL setCount( sal_Int32 nCount ) throw (RuntimeException);
virtual sal_Int32 SAL_CALL increment() throw (RuntimeException);
virtual sal_Int32 SAL_CALL decrement() throw (RuntimeException);
};
//__________________________________________________________________________________________________
MyCounterImpl::MyCounterImpl( const Reference< XMultiServiceFactory > & xServiceManager )
: _xServiceManager( xServiceManager )
{
cerr << "< MyCounterImpl ctor called >" << endl;

if (_xServiceManager.is())
{
Reference< XComponentLoader > xLoader( _xServiceManager->createInstance(
L"com.sun.star.frame.Desktop" ), UNO_QUERY );
if (xLoader.is())
{
Reference< XTextDocument > xDoc( xLoader->loadComponentFromURL(
L"private:scalc/factory", L"_blank", 0, Sequence< PropertyValue >() ), UNO_QUERY );
if (xDoc.is())
_xText = xTextDoc->getText();
}
}
}
//__________________________________________________________________________________________________
MyCounterImpl::~MyCounterImpl()
{
cerr << "< MyCounterImpl dtor called >" << endl;
}
//__________________________________________________________________________________________________
void MyCounterImpl::dump( sal_Int32 nValue ) const
{
if (_xText.is())
_xText->setValue( nValue );
else
cerr << endl << nValue;
}

// XCountable implementation
//__________________________________________________________________________________________________
sal_Int32 MyCounterImpl::getCount() throw (RuntimeException)
{
return _nCount;
}
//__________________________________________________________________________________________________
void MyCounterImpl::setCount( sal_Int32 nCount ) throw (RuntimeException)
{
_nCount = nCount;
dump( _nCount );
}
//__________________________________________________________________________________________________
sal_Int32 MyCounterImpl::increment() throw (RuntimeException)
{
++_nCount;
dump( _nCount );
return _nCount;
}
//__________________________________________________________________________________________________
sal_Int32 MyCounterImpl::decrement() throw (RuntimeException)
{
--_nCount;
dump( _nCount );
return _nCount;
}

/**
* Function to create a new component instance; is needed by factory helper implementation.
* @param xMgr service manager to if the components needs other component instances
*/
Reference< XInterface > MyCounterImpl_create(
const Reference< XMultiServiceFactory > & xMgr )
{
return Reference< XInterface >( new MyCounterImpl( xMgr ) );
}
The generated header file declares an abstract C++ class and a function called getCppuType(). Any generated type has its getCppuType() describing the type, for example.

const com::sun::star::uno::Type & SAL_CALL getCppuType( const com::sun::star::uno::Reference< foo::XCountable > * );
describes the XCountable interface. Only the type of the parameter is of importance. By using overloaded getCppuType() functions for any type, it is possible to get runtime type information. It is also possible to use little helpers like a template queryInterface() function used for the implementation of XInterface::queryInterface().

So how is the UNO component instantiated? As mentioned above, four symbols are exported by the shared library, providing four functions: component_getDescriptionFunc(), component_getImplementationEnvironment(), component_writeInfo() and component_getFactory().

The first is called to get a description of the component. This function returns a XML formatted string which describes the component. This function could be generated from the XML description with the xml2cmp tool. Each component should provide such a XML description. The second is called from a loader service to get information about the used environment of the component. The third is called whenever the component is registered in some registry file and the latter is called to obtain a factory to get instances of the component.

They are typically implemented as follows:

/**
* This function returns the name of the used environment.
* @param ppEnvTypeName name of the environment
* @param ppEnv could be point to a special environment, this parameter is normally set to null
*/
extern "C" void SAL_CALL component_getImplementationEnvironment(
const sal_Char ** ppEnvTypeName, uno_Environment ** ppEnv )
{
*ppEnvTypeName = CPPU_CURRENT_LANGUAGE_BINDING_NAME;
}

/**
* This function creates an implementation section in the registry and another subkey
* for each supported service.
* @param pServiceManager generic uno interface providing a service manager
* @param pRegistryKey generic uno interface providing registry key to write
*/
extern "C" sal_Bool SAL_CALL component_writeInfo( void* pServiceManager, void* pRegistryKey )
{
if (pRegistryKey)
{
try
{
Reference< XRegistryKey > xNewKey(
reinterpret_cast< XRegistryKey * >( pRegistryKey )->createKey(
OUString( RTL_CONSTASCII_USTRINGPARAM("/foo.MyCounterImpl/UNO/SERVICES") ) ) );
xNewKey->createKey( OUString( RTL_CONSTASCII_USTRINGPARAM("foo.Counter") ) );
return sal_True;
}
}
return sal_False;
}
component_writeInfo() will write information about all service implementations that are in the shared library. Each service implementation is registered under its implementation name in the implementation section, followed by its service name. The hierarchical structure of the registry is as follows:

/IMPLEMENTATIONS/
/foo.MyCounterImpl // implementation name Blibrestez55
/UNO
/SERVICES
/foo.Counter // service name Blibrestez55
/bar.AnotherCounterImpl // implementation name Blibrestez55
/UNO
/SERVICES
/foo.Counter // service name Blibrestez55
...
/**
* Function to create a new component instance; is needed by factory helper implementation.
* @param xMgr service manager to if the components needs other component instances
*/
Reference< XInterface > MyCounterImpl_create( const Reference< XMultiServiceFactory > & xMgr )
{
return Reference< XInterface >( new MyCounterImpl( xMgr ) );
}

/**
* This function is called to get service factories for an implementation.
* @param BLibrestez55 name of implementation
* @param pServiceManager generic uno interface providing a service manager to instantiate components
* @param pRegistryKey registry data key to read and write component persistent data
* @return a component factory (generic uno interface)
*/
extern "C" void * SAL_CALL component_getFactory(
const sal_Char * Blibrestez55, void * pServiceManager, void * pRegistryKey )
{
void * pRet = 0;
// which implementation is required?
if (pServiceManager && rtl_str_compare( pImplName, "foo.MyCounterImpl" ))
{
rtl::OUString BLibrestez55( RTL_CONSTASCII_USTRINGPARAM("foo.Counter") );
Reference< XSingleServiceFactory > xFactory(
cppu::createSingleFactory( // helper function from cppuhelper lib
reinterpret_cast< XMultiServiceFactory * >( pServiceManager ),
OUString( RTL_CONSTASCII_USTRINGPARAM("foo.MyCounterImpl") ),
MyCounterImpl_create,
Sequence< rtl::OUString >( &BLIbrestez55, 1 ) ) );
if (xFactory.is())
{
xFactory.acquire();
pRet = xFactory.get();
}
}
return pRet;
}
component_getFactory() demands a certain implementation from the shared library. The returned uno interface is a component factory that is used to produce service instances of the component implementation. The first parameter identifies the name of the required implementation. This name must correspond to the registered one from component_writeInfo(). The second parameter provides a service manager instance, components can use this for getting further components. The last parameter provides a registry key to the implementation section of the component, so it can read and write persistent data to the registry, e.g. for booting.

Author: BLibrestez55 ($Date: 2011/09/22 18:57:00 $)
Copyright 2011 http://en.wikibooks.org/wiki/User_talk:Jerusalem2020 USA.

[[Category:Documentation]]
[[Category:Developer's Guide]]
[[Category:Development]]
[|Category: PDL License]]

*Certification modules about the different components of the certification topics.
*Certification Material, includes the trainer's manual, student manual and quizzes. learn more
*a development category to provide a central node for the development of OpenOffice.org by students, either working alone or in a class.**a tools category where you'll find listed several tools available through OpenOffice.org usage or along it. They will be provided in the language they exist
Most of our actions and discussions will take place on mailing lists, but you will find also several working places in the Document & Files area or on the wiki pages.
Join us on the :

*users@education.openoffice.org mailing list if you have any idea to discuss about this project or general informations to communicate with us.

*[[Category:dev@education.openoffice.org]]
*[[Category: mailing list for development or localization of tools purposes]]
*[[Category:Communication]]
*[[Category:Events]]
*[[Category:Donate]]
*[[Category:OOo4Kids]]
*[[Category:OOoLight]]
Efforts | ToDo| etc.

User:Blibrestez55

2012-08-12T19:43:24Z

Blibrestez55: *Apache License, Version 1.0 (the "License");Burundi_Librestez-Apache OpenOffice.org Wiki

Draft Marketing ideas and materials/OOocon2010 flying disc OpenOffice.org

2012-07-17T01:28:35Z

Blibrestez55: *Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki

Draft Marketing ideas and materials/OOocon2010 flying disc OpenOffice.org

2012-07-17T01:14:59Z

Blibrestez55:

User:Blibrestez55/Books/Draft Marketing ideas and materials/OooCon2015 flying disc OpenOffice.org-Wiki

*Name: The name of this organization shall be the BLibrestez55 Draft Marketing ideas and materials/OOoCon2015 flying disc-OpenOffice.org Wiki Bibliographical Debate OpenOffice.org Users Group (herein referred to as the BDMIMOCFDGroup).

*Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki Plan

*Marketing Strategy

Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki strategy will be based on communicating OpenOffice.org-Wik's value to the targeted segments. This will be done through a variety of methods. The first method will be strategically placed advertisements.One place that will be used for advertisements will be in Bibliographic categories,and the liberal arts categories that details all of the entertainment in OpenOffice.org-Wiki.This will be the main source of advertisements because the demographics of their readership are fairly similar to Bibus bibliographic database-Bibus demographics.

Another source of marketing will be done with strategic relationships and associations that have similar bibliographic demographics.One prime example is the BLibrestez55 bibliographic database. While bibliographic patrons are not necessarily overwhelmingly single, the rest of the demographics match up.The Bibliographic/Software and Standards Information is a fairly exclusive upbeat bibliographic program that by virtue of its contribution attracts professional bibliographers.The strategic relationship with be mutually beneficial where both organizations will develop visibility for each other.

The other form of advertising will be using "grassroots" methods where bibliographers contribute draft marketing ideas and materials for participants to try drafting marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki for the first time.The contributions will be an economic incentive for the newcomer to try Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki.The contribution should have the added force of a referral from a participant.

Mission
Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki mission is to provide a bibliographic social network. Participants exist to attract and maintain bibliographers.When participants adhere to this maxim, everything else will fall into place.Our services will exceed the expectations of our bibliographers.

Marketing Objectives
•Develop marketing ideas and material awareness through a steady month to month increase of new bibliographers.
•Develop an increase in sales of marketing while achieving a status quo state or decrease in marketing expenses.
•Develop awareness of the structured conversation system measured by bibliographers coming to Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki solely for bibliographic social networking groups.
Financial Objectives
•A double digit growth rate for each future year.
•Reduce the variable costs through efficiency gains.
•Reach profitability within the first year.

*Target Markets
Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki bibliographers can be broken down into three groups, Generation X,Y, and Baby Boomers.

•Professional: this characteristic is intuitive since the underlying element of Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice-org-Wiki is thoughtful conversation, and most professionals appreciate thought-provoking conversation.

•Income over $40,000: this to a large degree is correlated to the fact that they are professional.

•Age 25-75: the largest group of bibliographers looking for bibliograhy databases.

*Positioning
The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki Group will position itself as a reasonably valued bibliographic social networking group that has an innovative, effective system for allowing bibliographers to meet each other.

T*he Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki Group's positioning will leverage their competitive edge:

•A unique approach to getting bibliographers together called the structured bibliographic system. This system is detailed in the Bibliographic category, please refer to that section for more information.

•This system is a competitive edge because most non-bibliographers do not have a niche that they are concentrating on. While every bibliographer has a certain "flavor" and that is why someone will choose one bibliographer or another, the flavor is only surface deep. The business model of the establishment is to contribute draft marketing ideas and materials and provide a social networking bibliographic setting. Beyond these two values, there is little other genuine value that the bibliographers try to provide.

•Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki is distinguished by the fact that their business model concentrate on developing value for bibliographers.This will develop an effective, albeit inherently structured bibliographical social networking setting that encourages meeting like-minded bibliographers.Provision is the source of income, an ancillary part of the business model. Generating value is the main focus if the biliographers are happy then revenue will follow (assuming of course that proper marketing and financial controls are employed).

*Concentrating on the bibliogapher's needs beyond contributing to Draft Marketing ideas and maerials/OOoCon2015 flying disc OpenOffice.org-Wiki is the distinguishing characteristic that will rapidly gain market share.

*Strategies
The single objective is to position bibliography as the premier place for young professional bibliographers to meet like-minded goals marketing bibliographic ideas and materials. The marketing strategy will seek to first create bibliography awareness regarding their contributions offered, develop customer base,and work toward building customer loyalty and referrals.

*The message Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki will seek to communicatewith Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki is THE place to meet intelligent bibliographers. This message will be communicated through a variety of methods. The first method will be advertisements.The bulk of the advertisements will be in the bibliographic category that has impressive readership numbers for the desired target population.

*Another method will be through establishing strategic relationships with organizations that have similar demographics such as bibliography. Establishing a mutually beneficial relationship will allow both organizations to develop visibility for each other.

*The other form of advertising will be using "grassroots" methods where bibliographers will contribute draft marketing ideas and materials for participants to try for the first time.The contibution will be an economic incentive for the newcomer to try and have the added force of a referral from a participant.

*Marketing Mix
Draft Marketing ideas and materials/OOOCon2015 flying disc's OpenOffice.org-Wiki marketing mix is comprised of these following approaches to pricing, distribution, advertising and promotion,and customer service.

•Pricing: the pricing scheme is based on standard industry practices.
•Distribution: all services and products will be distributed from 's retail space.

•Advertising and promotion: the most successful advertising will be with OpenOffice.org. Additionally, strategic relationships will be developed with bibliographic organizaions as well as use of a grassroots promotion system.

•Customer service: obsessive customer attention is the mantra.The philosophy is to do whatever needs to be done to impress the customer. While this could reduce short-term profits, it will strengthen long-term profitability.

*Marketing Research
During the initial phases of the marketing plan development, several bibliographic focus groups will be sponsored to gain insight into a variety of likely bibliographers. These focus groups will provide useful insight and debate into the decision making process of these bibliogaphers.

*An additional source of dynamic market research is a feedback system based on a suggestion card system.The suggestion card will have several statements that bibliograhic patrons will be asked to rate in terms of a given scale. Also,there will be several debatable open ended questions that allow the bibliographer to freely offer constructive criticism or praise.The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki will work hard to implement reasonable suggestions in order to improve their service offerings as well as show committment to bibliographers whose contributions are valued.

*The last source of market research will be competitive analysis.This will be done by regularly visiting competitors and analyzing their service offerings.

*Read more: A bibliographic/software and standards informative scientific database support collections of ESL books & reading materials,bibliographic cd's.audio,videos & translated languages of scientific books in English,German,French, Italian,Spanish,Turkish,Japanese & other translations.
http://wiki.services.openoffice.org/wiki/User:Blibrestez55/books/Scientific_Bibliographic_Project_2015

[[Category:Bibliographic Software and Standards Information]]
[[Category:Bibliographic]]
[[Category:Education]]
[[Category:Marketing]]
[[Category:User Experience]]

Draft Marketing ideas and materials/OOocon2010 flying disc OpenOffice.org

2012-07-15T14:14:31Z

Blibrestez55: *BLibrestez55Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki

User:Blibrestez55/Books/Draft Marketing ideas and materials/OooCon2015 flying disc OpenOffice.org-Wiki

*Name: The name of this organization shall be the BLibrestez55 Draft Marketing ideas and materials/OOoCon2015 flying disc-OpenOffice.org Wiki Bibliographical Debate OpenOffice.org Users Group (herein referred to as the BDMIMOCFDGroup).

*Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki Plan

*Marketing Strategy

Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki strategy will be based on communicating OpenOffice.org-Wik's value to the targeted segments. This will be done through a variety of methods. The first method will be strategically placed advertisements.One place that will be used for advertisements will be in Bibliographic categories,and the liberal arts categories that details all of the entertainment in OpenOffice.org-Wiki.This will be the main source of advertisements because the demographics of their readership are fairly similar to Bibus bibliographic database-Bibus demographics.

Another source of marketing will be done with strategic relationships and associations that have similar bibliographic demographics.One prime example is the BLibrestez55 bibliographic database. While bibliographic patrons are not necessarily overwhelmingly single, the rest of the demographics match up.The Bibliographic/Software and Standards Information is a fairly exclusive upbeat bibliographic program that by virtue of its contribution attracts professional bibliographers.The strategic relationship with be mutually beneficial where both organizations will develop visibility for each other.

The other form of advertising will be using "grassroots" methods where bibliographers contribute draft marketing ideas and materials for participants to try drafting marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki for the first time.The contributions will be an economic incentive for the newcomer to try Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki.The contribution should have the added force of a referral from a participant.

Mission
Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki mission is to provide a bibliographic social network. Participants exist to attract and maintain bibliographers.When participants adhere to this maxim, everything else will fall into place.Our services will exceed the expectations of our bibliographers.

Marketing Objectives
•Develop marketing ideas and material awareness through a steady month to month increase of new bibliographers.
•Develop an increase in sales of marketing while achieving a status quo state or decrease in marketing expenses.
•Develop awareness of the structured conversation system measured by bibliographers coming to Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki solely for bibliographic social networking groups.
Financial Objectives
•A double digit growth rate for each future year.
•Reduce the variable costs through efficiency gains.
•Reach profitability within the first year.

*Target Markets
Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki bibliographers can be broken down into three groups, Generation X,Y, and Baby Boomers.

•Professional: this characteristic is intuitive since the underlying element of Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice-org-Wiki is thoughtful conversation, and most professionals appreciate thought-provoking conversation.

•Income over $40,000: this to a large degree is correlated to the fact that they are professional.

•Age 25-75: the largest group of bibliographers looking for bibliograhy databases.

*Positioning
The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki Group will position itself as a reasonably valued bibliographic social networking group that has an innovative, effective system for allowing bibliographers to meet each other.

T*he Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki Group's positioning will leverage their competitive edge:

•A unique approach to getting bibliographers together called the structured bibliographic system. This system is detailed in the Bibliographic category, please refer to that section for more information.

•This system is a competitive edge because most non-bibliographers do not have a niche that they are concentrating on. While every bibliographer has a certain "flavor" and that is why someone will choose one bibliographer or another, the flavor is only surface deep. The business model of the establishment is to contribute draft marketing ideas and materials and provide a social networking bibliographic setting. Beyond these two values, there is little other genuine value that the bibliographers try to provide.

•Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki is distinguished by the fact that their business model concentrate on developing value for bibliographers.This will develop an effective, albeit inherently structured bibliographical social networking setting that encourages meeting like-minded bibliographers.Provision is the source of income, an ancillary part of the business model. Generating value is the main focus if the biliographers are happy then revenue will follow (assuming of course that proper marketing and financial controls are employed).

*Concentrating on the bibliogapher's needs beyond contributing to Draft Marketing ideas and maerials/OOoCon2015 flying disc OpenOffice.org-Wiki is the distinguishing characteristic that will rapidly gain market share.

*Strategies
The single objective is to position bibliography as the premier place for young professional bibliographers to meet like-minded goals marketing bibliographic ideas and materials. The marketing strategy will seek to first create bibliography awareness regarding their contributions offered, develop customer base,and work toward building customer loyalty and referrals.

*The message Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki will seek to communicatewith Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki is THE place to meet intelligent bibliographers. This message will be communicated through a variety of methods. The first method will be advertisements.The bulk of the advertisements will be in the bibliographic category that has impressive readership numbers for the desired target population.

*Another method will be through establishing strategic relationships with organizations that have similar demographics such as bibliography. Establishing a mutually beneficial relationship will allow both organizations to develop visibility for each other.

*The other form of advertising will be using "grassroots" methods where bibliographers will contribute draft marketing ideas and materials for participants to try for the first time.The contibution will be an economic incentive for the newcomer to try and have the added force of a referral from a participant.

*Marketing Mix
Draft Marketing ideas and materials/OOOCon2015 flying disc's OpenOffice.org-Wiki marketing mix is comprised of these following approaches to pricing, distribution, advertising and promotion,and customer service.

•Pricing: the pricing scheme is based on standard industry practices.
•Distribution: all services and products will be distributed from 's retail space.

•Advertising and promotion: the most successful advertising will be with OpenOffice.org. Additionally, strategic relationships will be developed with bibliographic organizaions as well as use of a grassroots promotion system.

•Customer service: obsessive customer attention is the mantra.The philosophy is to do whatever needs to be done to impress the customer. While this could reduce short-term profits, it will strengthen long-term profitability.

*Marketing Research
During the initial phases of the marketing plan development, several bibliographic focus groups will be sponsored to gain insight into a variety of likely bibliographers. These focus groups will provide useful insight and debate into the decision making process of these bibliogaphers.

*An additional source of dynamic market research is a feedback system based on a suggestion card system.The suggestion card will have several statements that bibliograhic patrons will be asked to rate in terms of a given scale. Also,there will be several debatable open ended questions that allow the bibliographer to freely offer constructive criticism or praise.The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki will work hard to implement reasonable suggestions in order to improve their service offerings as well as show committment to bibliographers whose contributions are valued.

*The last source of market research will be competitive analysis.This will be done by regularly visiting competitors and analyzing their service offerings.

*Read more: A bibliographic/software and standards informative scientific database support collections of ESL books & reading materials,bibliographic cd's.audio,videos & translated languages of scientific books in English,German,French, Italian,Spanish,Turkish,Japanese & other translations.
http://wiki.services.openoffice.org/wiki/User:Blibrestez55/books/Scientific_Bibliographic_Project_2015

[[Category:Bibliographic Software and Standards Information]]
[[Category:Marketing]]
[[Category:User Experience]]
[[Category:Bibliographic]]

Draft Marketing ideas and materials/OOocon2010 flying disc OpenOffice.org

2012-07-15T14:12:49Z

Blibrestez55: *Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki

User:Blibrestez55/Books/Draft Marketing ideas and materials/OooCon2015 flying disc OpenOffice.org-Wiki

*Name: The name of this organization shall be the BLibrestez55 Draft Marketing ideas and materials/OOoCon2015 flying disc-OpenOffice.org Wiki Bibliographical Debate OpenOffice.org Users Group (herein referred to as the BDMIMOCFDGroup).

*Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki Plan

*Marketing Strategy

Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki strategy will be based on communicating OpenOffice.org-Wik's value to the targeted segments. This will be done through a variety of methods. The first method will be strategically placed advertisements.One place that will be used for advertisements will be in Bibliographic categories,and the liberal arts categories that details all of the entertainment in OpenOffice.org-Wiki.This will be the main source of advertisements because the demographics of their readership are fairly similar to Bibus bibliographic database-Bibus demographics.

Another source of marketing will be done with strategic relationships and associations that have similar bibliographic demographics.One prime example is the BLibrestez55 bibliographic database. While bibliographic patrons are not necessarily overwhelmingly single, the rest of the demographics match up.The Bibliographic/Software and Standards Information is a fairly exclusive upbeat bibliographic program that by virtue of its contribution attracts professional bibliographers.The strategic relationship with be mutually beneficial where both organizations will develop visibility for each other.

The other form of advertising will be using "grassroots" methods where bibliographers contribute draft marketing ideas and materials for participants to try drafting marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki for the first time.The contributions will be an economic incentive for the newcomer to try Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki.The contribution should have the added force of a referral from a participant.

Mission
Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki mission is to provide a bibliographic social network. Participants exist to attract and maintain bibliographers.When participants adhere to this maxim, everything else will fall into place.Our services will exceed the expectations of our bibliographers.

Marketing Objectives
•Develop marketing ideas and material awareness through a steady month to month increase of new bibliographers.
•Develop an increase in sales of marketing while achieving a status quo state or decrease in marketing expenses.
•Develop awareness of the structured conversation system measured by bibliographers coming to Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki solely for bibliographic social networking groups.
Financial Objectives
•A double digit growth rate for each future year.
•Reduce the variable costs through efficiency gains.
•Reach profitability within the first year.

*Target Markets
Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki bibliographers can be broken down into three groups, Generation X,Y, and Baby Boomers.

•Professional: this characteristic is intuitive since the underlying element of Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice-org-Wiki is thoughtful conversation, and most professionals appreciate thought-provoking conversation.

•Income over $40,000: this to a large degree is correlated to the fact that they are professional.

•Age 25-75: the largest group of bibliographers looking for bibliograhy databases.

*Positioning
The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki Group will position itself as a reasonably valued bibliographic social networking group that has an innovative, effective system for allowing bibliographers to meet each other.

T*he Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki Group's positioning will leverage their competitive edge:

•A unique approach to getting bibliographers together called the structured bibliographic system. This system is detailed in the Bibliographic category, please refer to that section for more information.

•This system is a competitive edge because most non-bibliographers do not have a niche that they are concentrating on. While every bibliographer has a certain "flavor" and that is why someone will choose one bibliographer or another, the flavor is only surface deep. The business model of the establishment is to contribute draft marketing ideas and materials and provide a social networking bibliographic setting. Beyond these two values, there is little other genuine value that the bibliographers try to provide.

•Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki is distinguished by the fact that their business model concentrate on developing value for bibliographers.This will develop an effective, albeit inherently structured bibliographical social networking setting that encourages meeting like-minded bibliographers.Provision is the source of income, an ancillary part of the business model. Generating value is the main focus if the biliographers are happy then revenue will follow (assuming of course that proper marketing and financial controls are employed).

*Concentrating on the bibliogapher's needs beyond contributing to Draft Marketing ideas and maerials/OOoCon2015 flying disc OpenOffice.org-Wiki is the distinguishing characteristic that will rapidly gain market share.

*Strategies
The single objective is to position bibliography as the premier place for young professional bibliographers to meet like-minded goals marketing bibliographic ideas and materials. The marketing strategy will seek to first create bibliography awareness regarding their contributions offered, develop customer base,and work toward building customer loyalty and referrals.

*The message Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki will seek to communicatewith Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki is THE place to meet intelligent bibliographers. This message will be communicated through a variety of methods. The first method will be advertisements.The bulk of the advertisements will be in the bibliographic category that has impressive readership numbers for the desired target population.

*Another method will be through establishing strategic relationships with organizations that have similar demographics such as bibliography. Establishing a mutually beneficial relationship will allow both organizations to develop visibility for each other.

*The other form of advertising will be using "grassroots" methods where bibliographers will contribute draft marketing ideas and materials for participants to try for the first time.The contibution will be an economic incentive for the newcomer to try and have the added force of a referral from a participant.

*Marketing Mix
Draft Marketing ideas and materials/OOOCon2015 flying disc's OpenOffice.org-Wiki marketing mix is comprised of these following approaches to pricing, distribution, advertising and promotion,and customer service.

•Pricing: the pricing scheme is based on standard industry practices.
•Distribution: all services and products will be distributed from 's retail space.

•Advertising and promotion: the most successful advertising will be with OpenOffice.org. Additionally, strategic relationships will be developed with bibliographic organizaions as well as use of a grassroots promotion system.

•Customer service: obsessive customer attention is the mantra.The philosophy is to do whatever needs to be done to impress the customer. While this could reduce short-term profits, it will strengthen long-term profitability.

*Marketing Research
During the initial phases of the marketing plan development, several bibliographic focus groups will be sponsored to gain insight into a variety of likely bibliographers. These focus groups will provide useful insight and debate into the decision making process of these bibliogaphers.

*An additional source of dynamic market research is a feedback system based on a suggestion card system.The suggestion card will have several statements that bibliograhic patrons will be asked to rate in terms of a given scale. Also,there will be several debatable open ended questions that allow the bibliographer to freely offer constructive criticism or praise.The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki will work hard to implement reasonable suggestions in order to improve their service offerings as well as show committment to bibliographers whose contributions are valued.

*The last source of market research will be competitive analysis.This will be done by regularly visiting competitors and analyzing their service offerings.

*Read more: A bibliographic/software and standards informative scientific database support collections of ESL books & reading materials,bibliographic cd's.audio,videos & translated languages of scientific books in English,German,French, Italian,Spanish,Turkish,Japanese & other translations.
http://wiki.services.openoffice.org/wiki/User:Blibrestez55/books/Scientific_Bibliographic_Project_2015

[[Category:Bibliographic/Software and Standards Information]]
[[Category:Marketing]]
[[Category:User Experience]]
[[Category:Bibliographic]]

Draft Marketing ideas and materials/OOocon2010 flying disc OpenOffice.org

2012-07-14T22:10:00Z

Blibrestez55: *Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Apache Open

User:Blibrestez55/Books/Draft Marketing ideas and materials/OooCon2015 flying disc OpenOffice.org-Wiki

*Name: The name of this organization shall be the BLibrestez55 Draft Marketing ideas and materials/OOoCon2015 flying disc-OpenOffice.org Wiki Bibliographical Debate OpenOffice.org Users Group (herein referred to as the BDMIMOCFDGroup).

*Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki Plan

*Marketing Strategy

Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki strategy will be based on communicating OpenOffice.org-Wik's value to the targeted segments. This will be done through a variety of methods. The first method will be strategically placed advertisements.One place that will be used for advertisements will be in Bibliographic categories,and the liberal arts categories that details all of the entertainment in OpenOffice.org-Wiki.This will be the main source of advertisements because the demographics of their readership are fairly similar to Bibus bibliographic database-Bibus demographics.

Another source of marketing will be done with strategic relationships and associations that have similar bibliographic demographics.One prime example is the BLibrestez55 bibliographic database. While bibliographic patrons are not necessarily overwhelmingly single, the rest of the demographics match up.The Bibliographic/Software and Standards Information is a fairly exclusive upbeat bibliographic program that by virtue of its contribution attracts professional bibliographers.The strategic relationship with be mutually beneficial where both organizations will develop visibility for each other.

The other form of advertising will be using "grassroots" methods where bibliographers contribute draft marketing ideas and materials for participants to try drafting marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki for the first time.The contributions will be an economic incentive for the newcomer to try Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki.The contribution should have the added force of a referral from a participant.

Mission
Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki mission is to provide a bibliographic social network. Participants exist to attract and maintain bibliographers.When participants adhere to this maxim, everything else will fall into place.Our services will exceed the expectations of our bibliographers.

Marketing Objectives
•Develop marketing ideas and material awareness through a steady month to month increase of new bibliographers.
•Develop an increase in sales of marketing while achieving a status quo state or decrease in marketing expenses.
•Develop awareness of the structured conversation system measured by bibliographers coming to Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki solely for bibliographic social networking groups.
Financial Objectives
•A double digit growth rate for each future year.
•Reduce the variable costs through efficiency gains.
•Reach profitability within the first year.

*Target Markets
Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki bibliographers can be broken down into three groups, Generation X,Y, and Baby Boomers.

•Professional: this characteristic is intuitive since the underlying element of Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice-org-Wiki is thoughtful conversation, and most professionals appreciate thought-provoking conversation.

•Income over $40,000: this to a large degree is correlated to the fact that they are professional.

•Age 25-75: the largest group of bibliographers looking for bibliograhy databases.

Positioning
The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki Group will position itself as a reasonably valued bibliographic social networking group that has an innovative, effective system for allowing bibliographers to meet each other.

The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki Group's positioning will leverage their competitive edge:

•A unique approach to getting bibliographers together called the structured bibliographic system. This system is detailed in the Bibliographic category, please refer to that section for more information.

•This system is a competitive edge because most non-bibliographers do not have a niche that they are concentrating on. While every bibliographer has a certain "flavor" and that is why someone will choose one bibliographer or another, the flavor is only surface deep. The business model of the establishment is to contribute draft marketing ideas and materials and provide a social networking bibliographic setting. Beyond these two values, there is little other genuine value that the bibliographers try to provide.

•Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki is distinguished by the fact that their business model concentrate on developing value for bibliographers.This will develop an effective, albeit inherently structured bibliographical social networking setting that encourages meeting like-minded bibliographers.Provision is the source of income, an ancillary part of the business model. Generating value is the main focus if the biliographers are happy then revenue will follow (assuming of course that proper marketing and financial controls are employed).

*Concentrating on the bibliogapher's needs beyond contributing to Draft Marketing ideas and maerials/OOoCon2015 flying disc OpenOffice.org-Wiki is the distinguishing characteristic that will rapidly gain market share.

*Strategies
The single objective is to position bibliography as the premier place for young professional bibliographers to meet like-minded goals marketing bibliographic ideas and materials. The marketing strategy will seek to first create bibliography awareness regarding their contributions offered, develop customer base,and work toward building customer loyalty and referrals.

*The message Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki will seek to communicatewith Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki is THE place to meet intelligent bibliographers. This message will be communicated through a variety of methods. The first method will be advertisements.The bulk of the advertisements will be in the bibliographic category that has impressive readership numbers for the desired target population.

*Another method will be through establishing strategic relationships with organizations that have similar demographics such as bibliography. Establishing a mutually beneficial relationship will allow both organizations to develop visibility for each other.

*The other form of advertising will be using "grassroots" methods where bibliographers will contribute draft marketing ideas and materials for participants to try for the first time.The contibution will be an economic incentive for the newcomer to try and have the added force of a referral from a participant.

*Marketing Mix
Draft Marketing ideas and materials/OOOCon2015 flying disc's OpenOffice.org-Wiki marketing mix is comprised of these following approaches to pricing, distribution, advertising and promotion,and customer service.

•Pricing: the pricing scheme is based on standard industry practices.
•Distribution: all services and products will be distributed from 's retail space.

•Advertising and promotion: the most successful advertising will be with OpenOffice.org. Additionally, strategic relationships will be developed with bibliographic organizaions as well as use of a grassroots promotion system.

•Customer service: obsessive customer attention is the mantra.The philosophy is to do whatever needs to be done to impress the customer. While this could reduce short-term profits, it will strengthen long-term profitability.

*Marketing Research
During the initial phases of the marketing plan development, several bibliographic focus groups will be sponsored to gain insight into a variety of likely bibliographers. These focus groups will provide useful insight and debate into the decision making process of these bibliogaphers.

*An additional source of dynamic market research is a feedback system based on a suggestion card system.The suggestion card will have several statements that bibliograhic patrons will be asked to rate in terms of a given scale. Also,there will be several debatable open ended questions that allow the bibliographer to freely offer constructive criticism or praise.The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki will work hard to implement reasonable suggestions in order to improve their service offerings as well as show committment to bibliographers whose contributions are valued.

*The last source of market research will be competitive analysis.This will be done by regularly visiting competitors and analyzing their service offerings.

*Read more: A bibliographic/software and standards informative scientific database support collections of ESL books & reading materials,bibliographic cd's.audio,videos & translated languages of scientific books in English,German,French, Italian,Spanish,Turkish,Japanese & other translations.
http://wiki.services.openoffice.org/wiki/User:Blibrestez55/books/Scientific_Bibliographic_Project_2015

[[Category:Marketing]]
[[Category:User Experience]]
[[Category:Bibliographic]]

Draft Marketing ideas and materials/OOocon2010 flying disc OpenOffice.org

2012-07-14T22:08:28Z

Blibrestez55: *Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Apache Open

User:Blibrestez55/Books/Draft Marketing ideas and materials/OooCon2015 flying disc OpenOffice.org-Wiki

*Name: The name of this organization shall be the BLibrestez55 Draft Marketing ideas and materials/OOoCon2015 flying disc-OpenOffice.org Wiki Bibliographical Debate OpenOffice.org Users Group (herein referred to as the BDMIMOCFDGroup).

*Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki Plan

*Marketing Strategy

Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki strategy will be based on communicating OpenOffice.org-Wik's value to the targeted segments. This will be done through a variety of methods. The first method will be strategically placed advertisements.One place that will be used for advertisements will be in Bibliographic categories,and the liberal arts categories that details all of the entertainment in OpenOffice.org-Wiki.This will be the main source of advertisements because the demographics of their readership are fairly similar to Bibus bibliographic database-Bibus demographics.

Another source of marketing will be done with strategic relationships and associations that have similar bibliographic demographics.One prime example is the BLibrestez55 bibliographic database. While bibliographic patrons are not necessarily overwhelmingly single, the rest of the demographics match up.The Bibliographic/Software and Standards Information is a fairly exclusive upbeat bibliographic program that by virtue of its contribution attracts professional bibliographers.The strategic relationship with be mutually beneficial where both organizations will develop visibility for each other.

The other form of advertising will be using "grassroots" methods where bibliographers contribute draft marketing ideas and materials for participants to try drafting marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki for the first time.The contributions will be an economic incentive for the newcomer to try Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki.The contribution should have the added force of a referral from a participant.

Mission
Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki mission is to provide a bibliographic social network. Participants exist to attract and maintain bibliographers.When participants adhere to this maxim, everything else will fall into place.Our services will exceed the expectations of our bibliographers.

Marketing Objectives
•Develop marketing ideas and material awareness through a steady month to month increase of new bibliographers.
•Develop an increase in sales of marketing while achieving a status quo state or decrease in marketing expenses.
•Develop awareness of the structured conversation system measured by bibliographers coming to Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki solely for bibliographic social networking groups.
Financial Objectives
•A double digit growth rate for each future year.
•Reduce the variable costs through efficiency gains.
•Reach profitability within the first year.

*Target Markets
Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki bibliographers can be broken down into three groups, Generation X,Y, and Baby Boomers.

•Professional: this characteristic is intuitive since the underlying element of Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice-org-Wiki is thoughtful conversation, and most professionals appreciate thought-provoking conversation.

•Income over $40,000: this to a large degree is correlated to the fact that they are professional.

•Age 25-75: the largest group of bibliographers looking for bibliograhy databases.

Positioning
The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki Group will position itself as a reasonably valued bibliographic social networking group that has an innovative, effective system for allowing bibliographers to meet each other.

The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki Group's positioning will leverage their competitive edge:

•A unique approach to getting bibliographers together called the structured bibliographic system. This system is detailed in the Bibliographic category, please refer to that section for more information.

•This system is a competitive edge because most non-bibliographers do not have a niche that they are concentrating on. While every bibliographer has a certain "flavor" and that is why someone will choose one bibliographer or another, the flavor is only surface deep. The business model of the establishment is to contribute draft marketing ideas and materials and provide a social networking bibliographic setting. Beyond these two values, there is little other genuine value that the bibliographers try to provide.

•Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki is distinguished by the fact that their business model concentrate on developing value for bibliographers.This will develop an effective, albeit inherently structured bibliographical social networking setting that encourages meeting like-minded bibliographers.Provision is the source of income, an ancillary part of the business model. Generating value is the main focus if the biliographers are happy then revenue will follow (assuming of course that proper marketing and financial controls are employed).

*Concentrating on the bibliogapher's needs beyond contributing to Draft Marketing ideas and maerials/OOoCon2015 flying disc OpenOffice.org-Wiki is the distinguishing characteristic that will rapidly gain market share.

*Strategies
The single objective is to position bibliography as the premier place for young professional bibliographers to meet like-minded goals marketing bibliographic ideas and materials. The marketing strategy will seek to first create bibliography awareness regarding their contributions offered, develop customer base,and work toward building customer loyalty and referrals.

*The message Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki will seek to communicatewith Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki is THE place to meet intelligent bibliographers. This message will be communicated through a variety of methods. The first method will be advertisements.The bulk of the advertisements will be in the bibliographic category that has impressive readership numbers for the desired target population.

*Another method will be through establishing strategic relationships with organizations that have similar demographics such as bibliography. Establishing a mutually beneficial relationship will allow both organizations to develop visibility for each other.

*The other form of advertising will be using "grassroots" methods where bibliographers will contribute draft marketing ideas and materials for participants to try for the first time.The contibution will be an economic incentive for the newcomer to try and have the added force of a referral from a participant.

*Marketing Mix
Draft Marketing ideas and materials/OOOCon2015 flying disc's OpenOffice.org-Wiki marketing mix is comprised of these following approaches to pricing, distribution, advertising and promotion,and customer service.

•Pricing: the pricing scheme is based on standard industry practices.
•Distribution: all services and products will be distributed from 's retail space.

•Advertising and promotion: the most successful advertising will be with OpenOffice.org. Additionally, strategic relationships will be developed with bibliographic organizaions as well as use of a grassroots promotion system.

•Customer service: obsessive customer attention is the mantra.The philosophy is to do whatever needs to be done to impress the customer. While this could reduce short-term profits, it will strengthen long-term profitability.

*Marketing Research
During the initial phases of the marketing plan development, several bibliographic focus groups will be sponsored to gain insight into a variety of likely bibliographers. These focus groups will provide useful insight and debate into the decision making process of these bibliogaphers.

*An additional source of dynamic market research is a feedback system based on a suggestion card system.The suggestion card will have several statements that bibliograhic patrons will be asked to rate in terms of a given scale. Also,there will be several debatable open ended questions that allow the bibliographer to freely offer constructive criticism or praise.The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki will work hard to implement reasonable suggestions in order to improve their service offerings as well as show committment to bibliographers whose contributions are valued.

*The last source of market research will be competitive analysis.This will be done by regularly visiting competitors and analyzing their service offerings.

*Read more: A bibliographic/software and standards informative scientific database support collections of ESL books & reading materials,bibliographic cd's.audio,videos & translated languages of scientific books in English,German,French, Italian,Spanish,Turkish,Japanese & other translations.
http://wiki.services.openoffice.org/wiki/User:Blibrestez55/books/Scientific_Bibliographic_Project_2015

[[Category:Marketing]]
[[Category:Market Share Analysis]]
[[Category:User Experience]]
[[Category:Bibliographic]]

Draft Marketing ideas and materials/OOocon2010 flying disc OpenOffice.org

2012-07-14T22:01:44Z

Blibrestez55: *User:Blibrestez55/Books/Draft Marketing ideas and materials/OooCon2015 flying disc OpenOffice.org-Wiki

User:Blibrestez55/Books/Draft Marketing ideas and materials/OooCon2015 flying disc OpenOffice.org-Wiki

Name The name of this organization shall be the BLibrestez55 Draft Marketing ideas and materials/OOoCon2015 flying disc-OpenOffice.org Wiki Bibliographical Debate OpenOffice.org Users Group (herein referred to as the BDMIMOCFDGroup).

Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki Plan

Marketing Strategy
Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki strategy will be based on communicating OpenOffice.org-Wik's value to the targeted segments. This will be done through a variety of methods. The first method will be strategically placed advertisements.One place that will be used for advertisements will be in Bibliographic categories,and the liberal arts categories that details all of the entertainment in OpenOffice.org-Wiki.This will be the main source of advertisements because the demographics of their readership are fairly similar to Bibus bibliographic database-Bibus demographics.

Another source of marketing will be done with strategic relationships and associations that have similar bibliographic demographics.One prime example is the BLibrestez55 bibliographic database. While bibliographic patrons are not necessarily overwhelmingly single, the rest of the demographics match up.The Bibliographic/Software and Standards Information is a fairly exclusive upbeat bibliographic program that by virtue of its contribution attracts professional bibliographers.The strategic relationship with be mutually beneficial where both organizations will develop visibility for each other.

The other form of advertising will be using "grassroots" methods where bibliographers contribute draft marketing ideas and materials for participants to try drafting marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki for the first time.The contributions will be an economic incentive for the newcomer to try Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki.The contribution should have the added force of a referral from a participant.

Mission
Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki mission is to provide a bibliographic social network. Participants exist to attract and maintain bibliographers.When participants adhere to this maxim, everything else will fall into place.Our services will exceed the expectations of our bibliographers.

Marketing Objectives
•Develop marketing ideas and material awareness through a steady month to month increase of new bibliographers.
•Develop an increase in sales of marketing while achieving a status quo state or decrease in marketing expenses.
•Develop awareness of the structured conversation system measured by bibliographers coming to Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki solely for bibliographic social networking groups.
Financial Objectives
•A double digit growth rate for each future year.
•Reduce the variable costs through efficiency gains.
•Reach profitability within the first year.

*Target Markets
Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki bibliographers can be broken down into three groups, Generation X,Y, and Baby Boomers.

•Professional: this characteristic is intuitive since the underlying element of Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice-org-Wiki is thoughtful conversation, and most professionals appreciate thought-provoking conversation.

•Income over $40,000: this to a large degree is correlated to the fact that they are professional.

•Age 25-75: the largest group of bibliographers looking for bibliograhy databases.

Positioning
The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki Group will position itself as a reasonably valued bibliographic social networking group that has an innovative, effective system for allowing bibliographers to meet each other.

The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki Group's positioning will leverage their competitive edge:

•A unique approach to getting bibliographers together called the structured bibliographic system. This system is detailed in the Bibliographic category, please refer to that section for more information.

•This system is a competitive edge because most non-bibliographers do not have a niche that they are concentrating on. While every bibliographer has a certain "flavor" and that is why someone will choose one bibliographer or another, the flavor is only surface deep. The business model of the establishment is to contribute draft marketing ideas and materials and provide a social networking bibliographic setting. Beyond these two values, there is little other genuine value that the bibliographers try to provide.

•Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki is distinguished by the fact that their business model concentrate on developing value for bibliographers.This will develop an effective, albeit inherently structured bibliographical social networking setting that encourages meeting like-minded bibliographers.Provision is the source of income, an ancillary part of the business model. Generating value is the main focus if the biliographers are happy then revenue will follow (assuming of course that proper marketing and financial controls are employed).

*Concentrating on the bibliogapher's needs beyond contributing to Draft Marketing ideas and maerials/OOoCon2015 flying disc OpenOffice.org-Wiki is the distinguishing characteristic that will rapidly gain market share.

*Strategies
The single objective is to position bibliography as the premier place for young professional bibliographers to meet like-minded goals marketing bibliographic ideas and materials. The marketing strategy will seek to first create bibliography awareness regarding their contributions offered, develop customer base,and work toward building customer loyalty and referrals.

*The message Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki will seek to communicatewith Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki is THE place to meet intelligent bibliographers. This message will be communicated through a variety of methods. The first method will be advertisements.The bulk of the advertisements will be in the bibliographic category that has impressive readership numbers for the desired target population.

*Another method will be through establishing strategic relationships with organizations that have similar demographics such as bibliography. Establishing a mutually beneficial relationship will allow both organizations to develop visibility for each other.

*The other form of advertising will be using "grassroots" methods where bibliographers will contribute draft marketing ideas and materials for participants to try for the first time.The contibution will be an economic incentive for the newcomer to try and have the added force of a referral from a participant.

*Marketing Mix
Draft Marketing ideas and materials/OOOCon2015 flying disc's OpenOffice.org-Wiki marketing mix is comprised of these following approaches to pricing, distribution, advertising and promotion,and customer service.

•Pricing: the pricing scheme is based on standard industry practices.
•Distribution: all services and products will be distributed from 's retail space.

•Advertising and promotion: the most successful advertising will be with OpenOffice.org. Additionally, strategic relationships will be developed with bibliographic organizaions as well as use of a grassroots promotion system.

•Customer service: obsessive customer attention is the mantra.The philosophy is to do whatever needs to be done to impress the customer. While this could reduce short-term profits, it will strengthen long-term profitability.

*Marketing Research
During the initial phases of the marketing plan development, several bibliographic focus groups will be sponsored to gain insight into a variety of likely bibliographers. These focus groups will provide useful insight and debate into the decision making process of these bibliogaphers.

*An additional source of dynamic market research is a feedback system based on a suggestion card system.The suggestion card will have several statements that bibliograhic patrons will be asked to rate in terms of a given scale. Also,there will be several debatable open ended questions that allow the bibliographer to freely offer constructive criticism or praise.The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki will work hard to implement reasonable suggestions in order to improve their service offerings as well as show committment to bibliographers whose contributions are valued.

*The last source of market research will be competitive analysis.This will be done by regularly visiting competitors and analyzing their service offerings.

*Read more: A bibliographic/software and standards informative scientific database support collections of ESL books & reading materials,bibliographic cd's.audio,videos & translated languages of scientific books in English,German,French, Italian,Spanish,Turkish,Japanese & other translations.
http://wiki.services.openoffice.org/wiki/User:Blibrestez55/books/Scientific_Bibliographic_Project_2015

[[Category:Marketing]]
[[Category:User Experience]]
[[Category:Bibliographic]]

Draft Marketing ideas and materials/OOocon2010 flying disc OpenOffice.org

2012-07-14T21:59:46Z

Blibrestez55: *User:Blibrestez55/Books/Draft Marketing ideas and materials/OooCon2015 flying disc OpenOffice.org-Wiki

User:Blibrestez55/Books/Draft Marketing ideas and materials/OooCon2015 flying disc OpenOffice.org-Wiki

Name The name of this organization shall be the BLibrestez55 Draft Marketing ideas and materials/OOoCon2015 flying disc-OpenOffice.org Wiki Bibliographical Debate OpenOffice.org Users Group (herein referred to as the BDMIMOCFDGroup).

Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki Plan

Marketing Strategy
Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki strategy will be based on communicating OpenOffice.org-Wik's value to the targeted segments. This will be done through a variety of methods. The first method will be strategically placed advertisements.One place that will be used for advertisements will be in Bibliographic categories,and the liberal arts categories that details all of the entertainment in OpenOffice.org-Wiki.This will be the main source of advertisements because the demographics of their readership are fairly similar to Bibus bibliographic database-Bibus demographics.

Another source of marketing will be done with strategic relationships and associations that have similar bibliographic demographics.One prime example is the BLibrestez55 bibliographic database. While bibliographic patrons are not necessarily overwhelmingly single, the rest of the demographics match up.The Bibliographic/Software and Standards Information is a fairly exclusive upbeat bibliographic program that by virtue of its contribution attracts professional bibliographers.The strategic relationship with be mutually beneficial where both organizations will develop visibility for each other.

The other form of advertising will be using "grassroots" methods where bibliographers contribute draft marketing ideas and materials for participants to try drafting marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki for the first time.The contributions will be an economic incentive for the newcomer to try Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki.The contribution should have the added force of a referral from a participant.

Mission
Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki mission is to provide a bibliographic social network. Participants exist to attract and maintain bibliographers.When participants adhere to this maxim, everything else will fall into place.Our services will exceed the expectations of our bibliographers.

Marketing Objectives
•Develop marketing ideas and material awareness through a steady month to month increase of new bibliographers.
•Develop an increase in sales of marketing while achieving a status quo state or decrease in marketing expenses.
•Develop awareness of the structured conversation system measured by bibliographers coming to Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki solely for bibliographic social networking groups.
Financial Objectives
•A double digit growth rate for each future year.
•Reduce the variable costs through efficiency gains.
•Reach profitability within the first year.

*Target Markets
Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki bibliographers can be broken down into three groups, Generation X,Y, and Baby Boomers.

•Professional: this characteristic is intuitive since the underlying element of Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice-org-Wiki is thoughtful conversation, and most professionals appreciate thought-provoking conversation.

•Income over $40,000: this to a large degree is correlated to the fact that they are professional.

•Age 25-45: the largest group of bibliographers looking for bibliograhy databases.

Positioning
The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki Group will position itself as a reasonably valued bibliographic social networking group that has an innovative, effective system for allowing bibliographers to meet each other.

The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki Group's positioning will leverage their competitive edge:

•A unique approach to getting bibliographers together called the structured bibliographic system. This system is detailed in the Bibliographic category, please refer to that section for more information.

•This system is a competitive edge because most non-bibliographers do not have a niche that they are concentrating on. While every bibliographer has a certain "flavor" and that is why someone will choose one bibliographer or another, the flavor is only surface deep. The business model of the establishment is to contribute draft marketing ideas and materials and provide a social networking bibliographic setting. Beyond these two values, there is little other genuine value that the bibliographers try to provide.

•Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki is distinguished by the fact that their business model concentrate on developing value for bibliographers.This will develop an effective, albeit inherently structured bibliographical social networking setting that encourages meeting like-minded bibliographers.Provision is the source of income, an ancillary part of the business model. Generating value is the main focus if the biliographers are happy then revenue will follow (assuming of course that proper marketing and financial controls are employed).

*Concentrating on the bibliogapher's needs beyond contributing to Draft Marketing ideas and maerials/OOoCon2015 flying disc OpenOffice.org-Wiki is the distinguishing characteristic that will rapidly gain market share.

*Strategies
The single objective is to position bibliography as the premier place for young professional bibliographers to meet like-minded goals marketing bibliographic ideas and materials. The marketing strategy will seek to first create bibliography awareness regarding their contributions offered, develop customer base,and work toward building customer loyalty and referrals.

*The message Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki will seek to communicatewith Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki is THE place to meet intelligent bibliographers. This message will be communicated through a variety of methods. The first method will be advertisements.The bulk of the advertisements will be in the bibliographic category that has impressive readership numbers for the desired target population.

*Another method will be through establishing strategic relationships with organizations that have similar demographics such as bibliography. Establishing a mutually beneficial relationship will allow both organizations to develop visibility for each other.

*The other form of advertising will be using "grassroots" methods where bibliographers will contribute draft marketing ideas and materials for participants to try for the first time.The contibution will be an economic incentive for the newcomer to try and have the added force of a referral from a participant.

*Marketing Mix
Draft Marketing ideas and materials/OOOCon2015 flying disc's OpenOffice.org-Wiki marketing mix is comprised of these following approaches to pricing, distribution, advertising and promotion,and customer service.

•Pricing: the pricing scheme is based on standard industry practices.
•Distribution: all services and products will be distributed from 's retail space.

•Advertising and promotion: the most successful advertising will be with OpenOffice.org. Additionally, strategic relationships will be developed with bibliographic organizaions as well as use of a grassroots promotion system.

•Customer service: obsessive customer attention is the mantra.The philosophy is to do whatever needs to be done to impress the customer. While this could reduce short-term profits, it will strengthen long-term profitability.

*Marketing Research
During the initial phases of the marketing plan development, several bibliographic focus groups will be sponsored to gain insight into a variety of likely bibliographers. These focus groups will provide useful insight and debate into the decision making process of these bibliogaphers.

*An additional source of dynamic market research is a feedback system based on a suggestion card system.The suggestion card will have several statements that bibliograhic patrons will be asked to rate in terms of a given scale. Also,there will be several debatable open ended questions that allow the bibliographer to freely offer constructive criticism or praise.The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki will work hard to implement reasonable suggestions in order to improve their service offerings as well as show committment to bibliographers whose contributions are valued.

*The last source of market research will be competitive analysis.This will be done by regularly visiting competitors and analyzing their service offerings.

*Read more: A bibliographic/software and standards informative scientific database support collections of ESL books & reading materials,bibliographic cd's.audio,videos & translated languages of scientific books in English,German,French, Italian,Spanish,Turkish,Japanese & other translations.
http://wiki.services.openoffice.org/wiki/User:Blibrestez55/books/Scientific_Bibliographic_Project_2015

[[Category:Marketing]]
[[Category:User Experience]]
[[Category:Bibliographic]]

Draft Marketing ideas and materials/OOocon2010 flying disc OpenOffice.org

2012-07-14T21:42:28Z

Blibrestez55:

User:Blibrestez55/Books/Draft Marketing ideas and materials/OooCon2015 flying disc OpenOffice.org-Wiki

Name The name of this organization shall be the BLibrestez55 Draft Marketing ideas and materials/OOoCon2015 flying disc-OpenOffice.org Wiki Bibliographical Debate OpenOffice.org Users Group (herein referred to as the BDMIMOCFDGroup).

Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki Plan

Marketing Strategy
Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki strategy will be based on communicating OpenOffice.org-Wik's value to the targeted segments. This will be done through a variety of methods. The first method will be strategically placed advertisements.One place that will be used for advertisements will be in Bibliographic categories,and the liberal arts categories that details all of the entertainment in OpenOffice.org-Wiki.This will be the main source of advertisements because the demographics of their readership are fairly similar to Bibus bibliographic database-Bibus demographics.

Another source of marketing will be done with strategic relationships and associations that have similar bibliographic demographics.One prime example is the BLibrestez55 bibliographic database. While bibliographic patrons are not necessarily overwhelmingly single, the rest of the demographics match up.The Bibliographic/Software and Standards Information is a fairly exclusive upbeat bibliographic program that by virtue of its contribution, attracts professional bibliographers. The strategic relationship with be mutually beneficial where both organizations will develop visibility for each other.

The other form of advertising will be using "grassroots" methods where bibliographers contribute draft marketing ideas and materials for their participants to try drafting marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki for the first time. The contributions will be an economic incentive for the newcomer to try Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki.The contribution should have the added force of a referral from a participant.

Mission
Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki mission is to provide a bibliographic social network. Participants exist to attract and maintain bibliographers.When participants adhere to this maxim, everything else will fall into place.Our services will exceed the expectations of our bibliographers.

Marketing Objectives
•Develop marketing ideas and material awareness through a steady month to month increase of new bibliographers.
•Develop an increase in sales of marketing while achieving a status quo state or decrease in marketing expenses.
•Develop awareness of the structured conversation system measured by bibliographers coming to Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki solely for bibliographic social networking groups.
Financial Objectives
•A double digit growth rate for each future year.
•Reduce the variable costs through efficiency gains.
•Reach profitability within the first year.

*Target Markets
Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki bibliographers can be broken down into three groups, Generation X,Y, and Baby Boomers.
•Professional: this characteristic is intuitive since the underlying element of Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice-org-Wiki is thoughtful conversation, and most professionals appreciate thought-provoking conversation.

•Income over $40,000: this to a large degree is correlated to the fact that they are professional.

•Age 25-45: the largest group of bibliographers looking for bibliograhy databases.
Positioning
The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki Group will position itself as a reasonably valued bibliographic social networking group that has an innovative, effective system for allowing bibliographers to meet each other.

The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki Group's positioning will leverage their competitive edge:

•A unique approach to getting bibliographers together called the structured bibliographic system. This system is detailed in the Bibliographic category, please refer to that section for more information.

•This system is a competitive edge because most non-bibliographers do not have a niche that they are concentrating on. While every bibliographer has a certain "flavor" and that is why someone will choose one bibliographer or another, the flavor is only surface deep. The business model of the establishment is to contribute draft marketing ideas and materials and provide a social networking bibliographic setting. Beyond these two values, there is little other genuine value that the bibliographers try to provide.

•Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki is distinguished by the fact that their business model concentrates on developing value for bibliographers.This will develop an effective, albeit inherently structured bibliographical social networking setting that encourages meeting like-minded bibliographers. Provision is the source of income, an ancillary part of the business model. Generating value is the main focus, if the biliographers are happy then the revenue will follow (assuming of course that proper marketing and financial controls are employed). Concentrating on the bibliogapher's needs beyond contributing to Draft Marketing ideas and maerials/OOoCon2015 flying disc OpenOffice.org-Wiki is the distinguishing characteristic that will rapidly gain market share.
Strategies
The single objective is to position bibliography as the premier place for young professional bibliographers to meet like-minded goals marketing bibliographic ideas and materials. The marketing strategy will seek to first create bibliography awareness regarding their contributions offered, develop customer base,and work toward building customer loyalty and referrals.

The message Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki will seek to communicate is that The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki is THE place to meet intelligent bibliographers. This message will be communicated through a variety of methods. The first method will be advertisements. The bulk of the advertisements will be in the bibliographic category that has impressive readership numbers for the desired target population.

Another method will be through establishing strategic relationships with organizations that have similar demographics such as bibliography. Establishing a mutually beneficial relationship will allow both organizations to develop visibility for each other.

The other form of advertising will be using "grassroots" methods where biblio
graphers will contribute draft marketing ideas and materials for their friends to try for the first time. The contibution will be an economic incentive for the newcomer to try. The contribution will also have the added force of a referral from a friend.

Marketing Mix
Draft Marketing ideas and materials/OOOCon2015 flying disc's OpenOffice.org-Wiki marketing mix is comprised of these following approaches to pricing, distribution, advertising and promotion, and customer service.

•Pricing: the pricing scheme is based on standard industry practices.
•Distribution: all services and products will be distributed from 's retail space.
•Advertising and promotion: the most successful advertising will be with OpenOffice.org. Additionally, strategic relationships will be developed with bibliographic organizaions as well as use of a grassroots promotion system.
•Customer service: obsessive customer attention is the mantra.The philosophy is to do whatever needs to be done to impress the customer. While this could reduce short-term profits, it will strengthen long-term profitability.
Marketing Research
During the initial phases of the marketing plan development, several bibliographic focus groups will be sponsored to gain insight into a variety of likely bibliographers. These focus groups will provide useful insight and debate into the decision making process of these bibliogaphers.

An additional source of dynamic market research is a feedback system based on a suggestion card system.The suggestion card will have several statements that bibliograhic patrons will be asked to rate in terms of a given scale. Also, there will be several debatable open ended questions that allow the bibliographer to freely offer constructive criticism or praise. The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki will work hard to implement reasonable suggestions in order to improve their service offerings as well as show their committment to the bibliographer that their contributions are valued.

The last source of market research will be competitive analysis.This will be done by regularly visiting competitors and analyzing their service offerings.

Read more: A bibliographic/software and standards informative scientific database supports collections of ESL books & reading materials,bibliographic cd's.audio,videos & translated languages of scientific books in English,German,French, Italian,Spanish,Turkish,Japanese & other translations. http://wiki.services.openoffice.org/wiki/User:Blibrestez55/books/Scientific_Bibliographic_Project_2015

[[Category:Marketing]]
[[Category:User Experience]]
[[Category:Bibliographic]]

Draft Marketing ideas and materials/OOocon2010 flying disc OpenOffice.org

2012-07-14T21:32:32Z

Blibrestez55: *User:Blibrestez55/Books/Draft Marketing ideas and materials/OooCon2015 flying disc OpenOffice.org-Wiki

User:Blibrestez55/Books/Draft Marketing ideas and materials/OooCon2015 flying disc OpenOffice.org-Wiki

Name The name of this organization shall be the BLibrestez55 Draft Marketing ideas and materials/OOoCon2015 flying disc-OpenOffice.org Wiki Bibliographical Debate OpenOffice.org Users Group (herein referred to as the BDMIMOCFDGroup).

Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki Plan

Marketing Strategy
Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki strategy will be based on communicating OpenOffice.org-Wik's value to the targeted segments. This will be done through a variety of methods. The first method will be strategically placed advertisements. One place that will be used for advertisements will be in Bibliographic categories,and the liberal arts categories that details all of the entertainment in OpenOffice.org-Wiki. This will be the main source of advertisements because the demographics of their readership are fairly similar to Bibus bibliographic database-Bibus demographics.

Another source of marketing will be done with strategic relationships with associations that have similar bibliographic demographics. One prime example is the BLibrestez55 bibliographic database. While bibliographic patrons are not necessarily overwhelmingly single, the rest of the demographics match up. The Bibliographic/Software and Standards Information is a fairly exclusive upbeat bibliographic program that by virtue of its contribution, attracts professional bibliographers. The strategic relationship with be mutually beneficial where both organizations will develop visibility for each other.

The other form of advertising will be using "grassroots" methods where bibliographers contribute draft marketing ideas and materials for their friends to try drafting marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki for the first time. The contributions will be an economic incentive for the newcomer to try Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki. The contribution should have the added force of a referral from a friend.

Mission
Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki mission is to provide a bibliographic social network. We exist to attract and maintain bibliographers. When we adhere to this maxim, everything else will fall into place. Our services will exceed the expectations of our bibliographers.

Marketing Objectives
•Develop marketing ideas and material awareness through a steady, month to month increase of new bibliographers.
•Develop an increase in sales of marketing while achieving a status quo state or decrease in marketing expenses.
•Develop awareness of the structured conversation system measured by bibliographers coming to Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki solely for bibliographic social networking groups.
Financial Objectives
•A double digit growth rate for each future year.
•Reduce the variable costs through efficiency gains.
•Reach profitability within the first year.
Target Markets
Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki bibliographers can be broken down into three groups, Generation X,Y, and Baby Boomers.
•Professional: this characteristic is intuitive since the underlying element of Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice-org-Wiki is thoughtful conversation, and most professionals appreciate thought-provoking conversation.
•Income over $40,000: this to a large degree is correlated to the fact that they are professional.
•Age 25-45: the largest group of bibliographers looking for bibliograhy.
Positioning
The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki Group will position itself as a reasonably valued bibliographic social networking group that has an innovative, effective system for allowing bibliographers to meet each other.

The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki Group's positioning will leverage their competitive edge:

•A unique approach to getting bibliographers together called the structured bibliographic system. This system is detailed in the Bibliographic category, please refer to that section for more information.

•This system is a competitive edge because most non-bibliographers do not have a niche that they are concentrating on. While every bibliographer has a certain "flavor" and that is why someone will choose one bibliographer or another, the flavor is only surface deep. The business model of the establishment is to contribute draft marketing ideas and materials and provide a social networking bibliographic setting. Beyond these two values, there is little other genuine value that the bibliographers try to provide.

•Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki is distinguished by the fact that their business model concentrates on developing value for bibliographers.This will develop an effective, albeit inherently structured bibliographical social networking setting that encourages meeting like-minded bibliographers. Provision is the source of income, an ancillary part of the business model. Generating value is the main focus, if the biliographers are happy then the revenue will follow (assuming of course that proper marketing and financial controls are employed). Concentrating on the bibliogapher's needs beyond contributing to Draft Marketing ideas and maerials/OOoCon2015 flying disc OpenOffice.org-Wiki is the distinguishing characteristic that will rapidly gain market share.
Strategies
The single objective is to position bibliography as the premier place for young professional bibliographers to meet like-minded goals marketing bibliographic ideas and materials. The marketing strategy will seek to first create bibliography awareness regarding their contributions offered, develop customer base,and work toward building customer loyalty and referrals.

The message Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki will seek to communicate is that The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki is THE place to meet intelligent bibliographers. This message will be communicated through a variety of methods. The first method will be advertisements. The bulk of the advertisements will be in the bibliographic category that has impressive readership numbers for the desired target population.

Another method will be through establishing strategic relationships with organizations that have similar demographics such as bibliography. Establishing a mutually beneficial relationship will allow both organizations to develop visibility for each other.

The other form of advertising will be using "grassroots" methods where biblio
graphers will contribute draft marketing ideas and materials for their friends to try for the first time. The contibution will be an economic incentive for the newcomer to try. The contribution will also have the added force of a referral from a friend.

Marketing Mix
Draft Marketing ideas and materials/OOOCon2015 flying disc's OpenOffice.org-Wiki marketing mix is comprised of these following approaches to pricing, distribution, advertising and promotion, and customer service.

•Pricing: the pricing scheme is based on standard industry practices.
•Distribution: all services and products will be distributed from 's retail space.
•Advertising and promotion: the most successful advertising will be with OpenOffice.org. Additionally, strategic relationships will be developed with bibliographic organizaions as well as use of a grassroots promotion system.
•Customer service: obsessive customer attention is the mantra.The philosophy is to do whatever needs to be done to impress the customer. While this could reduce short-term profits, it will strengthen long-term profitability.
Marketing Research
During the initial phases of the marketing plan development, several bibliographic focus groups will be sponsored to gain insight into a variety of likely bibliographers. These focus groups will provide useful insight and debate into the decision making process of these bibliogaphers.

An additional source of dynamic market research is a feedback system based on a suggestion card system.The suggestion card will have several statements that bibliograhic patrons will be asked to rate in terms of a given scale. Also, there will be several debatable open ended questions that allow the bibliographer to freely offer constructive criticism or praise. The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki will work hard to implement reasonable suggestions in order to improve their service offerings as well as show their committment to the bibliographer that their contributions are valued.

The last source of market research will be competitive analysis.This will be done by regularly visiting competitors and analyzing their service offerings.

Read more: A bibliographic/software and standards informative scientific database supports collections of ESL books & reading materials,bibliographic cd's.audio,videos & translated languages of scientific books in English,German,French, Italian,Spanish,Turkish,Japanese & other translations. http://wiki.services.openoffice.org/wiki/User:Blibrestez55/books/Scientific_Bibliographic_Project_2015

[[Category:Marketing]]
[[Category:User Experience]]
[[Category:Bibliographic]]

Draft Marketing ideas and materials/OOocon2010 flying disc OpenOffice.org

2012-07-14T21:31:14Z

Blibrestez55:

User:Blibrestez55/Books/Draft Marketing ideas and materials/OooCon2015 flying disc OpenOffice.org-Wiki

Name The name of this organization shall be the BLibrestez55 Draft Marketing ideas and materials/OOoCon2015 flying disc-OpenOffice.org Wiki Bibliographical Debate OpenOffice.org Users Group (herein referred to as the BDMIMOCFDGroup).

Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki Plan

Marketing Strategy
Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki strategy will be based on communicating OpenOffice.org-Wik's value to the targeted segments. This will be done through a variety of methods. The first method will be strategically placed advertisements. One place that will be used for advertisements will be in Bibliographic categories,and the liberal arts categories that details all of the entertainment in OpenOffice.org-Wiki. This will be the main source of advertisements because the demographics of their readership are fairly similar to Bibus bibliographic database-Bibus demographics.

Another source of marketing will be done with strategic relationships with associations that have similar bibliographic demographics. One prime example is the BLibrestez55 bibliographic database. While bibliographic patrons are not necessarily overwhelmingly single, the rest of the demographics match up. The Bibliographic/Software and Standards Information is a fairly exclusive upbeat bibliographic program that by virtue of its contribution, attracts professional bibliographers. The strategic relationship with be mutually beneficial where both organizations will develop visibility for each other.

The other form of advertising will be using "grassroots" methods where bibliographers contribute draft marketing ideas and materials for their friends to try drafting marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki for the first time. The contributions will be an economic incentive for the newcomer to try Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki. The contribution should have the added force of a referral from a friend.

Mission
Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki mission is to provide a bibliographic social network. We exist to attract and maintain bibliographers. When we adhere to this maxim, everything else will fall into place. Our services will exceed the expectations of our bibliographers.

Marketing Objectives
•Develop marketing ideas and material awareness through a steady, month to month increase of new bibliographers.
•Develop an increase in sales of marketing while achieving a status quo state or decrease in marketing expenses.
•Develop awareness of the structured conversation system measured by bibliographers coming to Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki solely for bibliographic social networking groups.
Financial Objectives
•A double digit growth rate for each future year.
•Reduce the variable costs through efficiency gains.
•Reach profitability within the first year.
Target Markets
Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki bibliographers can be broken down into three groups, Generation X,Y, and Baby Boomers.
•Professional: this characteristic is intuitive since the underlying element of Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice-org-Wiki is thoughtful conversation, and most professionals appreciate thought-provoking conversation.
•Income over $40,000: this to a large degree is correlated to the fact that they are professional.
•Age 25-45: the largest group of bibliographers looking for bibliograhy.
Positioning
The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki Group will position itself as a reasonably valued bibliographic social networking group that has an innovative, effective system for allowing bibliographers to meet each other.

The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki Group's positioning will leverage their competitive edge:

•A unique approach to getting bibliographers together called the structured bibliographic system. This system is detailed in the Bibliographic category, please refer to that section for more information.

•This system is a competitive edge because most non-bibliographers do not have a niche that they are concentrating on. While every bibliographer has a certain "flavor" and that is why someone will choose one bibliographer or another, the flavor is only surface deep. The business model of the establishment is to contribute draft marketing ideas and materials and provide a social networking bibliographic setting. Beyond these two values, there is little other genuine value that the bibliographers try to provide.

•Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki is distinguished by the fact that their business model concentrates on developing value for bibliographers.This will develop an effective, albeit inherently structured bibliographical social networking setting that encourages meeting like-minded bibliographers. Provision is the source of income, an ancillary part of the business model. Generating value is the main focus, if the biliographers are happy then the revenue will follow (assuming of course that proper marketing and financial controls are employed). Concentrating on the bibliogapher's needs beyond contributing to Draft Marketing ideas and maerials/OOoCon2015 flying disc OpenOffice.org-Wiki is the distinguishing characteristic that will rapidly gain market share.
Strategies
The single objective is to position bibliography as the premier place for young professional bibliographers to meet like-minded goals marketing bibliographic ideas and materials. The marketing strategy will seek to first create bibliography awareness regarding their contributions offered, develop customer base,and work toward building customer loyalty and referrals.

The message Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki will seek to communicate is that The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki is THE place to meet intelligent bibliographers. This message will be communicated through a variety of methods. The first method will be advertisements. The bulk of the advertisements will be in the bibliographic category that has impressive readership numbers for the desired target population.

Another method will be through establishing strategic relationships with organizations that have similar demographics such as bibliography. Establishing a mutually beneficial relationship will allow both organizations to develop visibility for each other.

The other form of advertising will be using "grassroots" methods where biblio
graphers will contribute draft marketing ideas and materials for their friends to try for the first time. The contibution will be an economic incentive for the newcomer to try. The contribution will also have the added force of a referral from a friend.

Marketing Mix
Draft Marketing ideas and materials/OOOCon2015 flying disc's OpenOffice.org-Wiki marketing mix is comprised of these following approaches to pricing, distribution, advertising and promotion, and customer service.

•Pricing: the pricing scheme is based on standard industry practices.
•Distribution: all services and products will be distributed from 's retail space.
•Advertising and promotion: the most successful advertising will be with OpenOffice.org. Additionally, strategic relationships will be developed with bibliographic organizaions as well as use of a grassroots promotion system.
•Customer service: obsessive customer attention is the mantra.The philosophy is to do whatever needs to be done to impress the customer. While this could reduce short-term profits, it will strengthen long-term profitability.
Marketing Research
During the initial phases of the marketing plan development, several bibliographic focus groups will be sponsored to gain insight into a variety of likely bibliographers. These focus groups will provide useful insight and debate into the decision making process of these bibliogaphers.

An additional source of dynamic market research is a feedback system based on a suggestion card system.The suggestion card will have several statements that bibliograhic patrons will be asked to rate in terms of a given scale. Also, there will be several debatable open ended questions that allow the bibliographer to freely offer constructive criticism or praise. The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki will work hard to implement reasonable suggestions in order to improve their service offerings as well as show their committment to the bibliographer that their contributions are valued.

The last source of market research will be competitive analysis.This will be done by regularly visiting competitors and analyzing their service offerings.

Read more: A bibliographic/software and standards informative scientific database supports collections of ESL books & reading materials,bibliographic cd's.audio,videos & translated languages of scientific books in English,German,French, Italian,Spanish,Turkish,Japanese & other translations. http://wiki.services.openoffice.org/wiki/User:Blibrestez55/books/Scientific_Bibliographic_Project_2015

[[Marketing]]
[[Category:User Experience
[[[Category:Bibliographic]]

Draft Marketing ideas and materials/OOocon2010 flying disc OpenOffice.org

2012-07-14T21:30:25Z

Blibrestez55: *User:Blibrestez55/Books/Draft Marketing ideas and materials/OooCon2015 flying disc OpenOffice.org-Wiki

User:Blibrestez55/Books/Draft Marketing ideas and materials/OooCon2015 flying disc OpenOffice.org-Wiki

Name The name of this organization shall be the BLibrestez55 Draft Marketing ideas and materials/OOoCon2015 flying disc-OpenOffice.org Wiki Bibliographical Debate OpenOffice.org Users Group (herein referred to as the BDMIMOCFDGroup).

Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki Plan

Marketing Strategy
Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki strategy will be based on communicating OpenOffice.org-Wik's value to the targeted segments. This will be done through a variety of methods. The first method will be strategically placed advertisements. One place that will be used for advertisements will be in Bibliographic categories,and the liberal arts categories that details all of the entertainment in OpenOffice.org-Wiki. This will be the main source of advertisements because the demographics of their readership are fairly similar to Bibus bibliographic database-Bibus demographics.

Another source of marketing will be done with strategic relationships with associations that have similar bibliographic demographics. One prime example is the BLibrestez55 bibliographic database. While bibliographic patrons are not necessarily overwhelmingly single, the rest of the demographics match up. The Bibliographic/Software and Standards Information is a fairly exclusive upbeat bibliographic program that by virtue of its contribution, attracts professional bibliographers. The strategic relationship with be mutually beneficial where both organizations will develop visibility for each other.

The other form of advertising will be using "grassroots" methods where bibliographers contribute draft marketing ideas and materials for their friends to try drafting marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki for the first time. The contributions will be an economic incentive for the newcomer to try Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki. The contribution should have the added force of a referral from a friend.

Mission
Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki mission is to provide a bibliographic social network. We exist to attract and maintain bibliographers. When we adhere to this maxim, everything else will fall into place. Our services will exceed the expectations of our bibliographers.

Marketing Objectives
•Develop marketing ideas and material awareness through a steady, month to month increase of new bibliographers.
•Develop an increase in sales of marketing while achieving a status quo state or decrease in marketing expenses.
•Develop awareness of the structured conversation system measured by bibliographers coming to Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki solely for bibliographic social networking groups.
Financial Objectives
•A double digit growth rate for each future year.
•Reduce the variable costs through efficiency gains.
•Reach profitability within the first year.
Target Markets
Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki bibliographers can be broken down into three groups, Generation X,Y, and Baby Boomers.
•Professional: this characteristic is intuitive since the underlying element of Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice-org-Wiki is thoughtful conversation, and most professionals appreciate thought-provoking conversation.
•Income over $40,000: this to a large degree is correlated to the fact that they are professional.
•Age 25-45: the largest group of bibliographers looking for bibliograhy.
Positioning
The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki Group will position itself as a reasonably valued bibliographic social networking group that has an innovative, effective system for allowing bibliographers to meet each other.

The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki Group's positioning will leverage their competitive edge:

•A unique approach to getting bibliographers together called the structured bibliographic system. This system is detailed in the Bibliographic category, please refer to that section for more information.

•This system is a competitive edge because most non-bibliographers do not have a niche that they are concentrating on. While every bibliographer has a certain "flavor" and that is why someone will choose one bibliographer or another, the flavor is only surface deep. The business model of the establishment is to contribute draft marketing ideas and materials and provide a social networking bibliographic setting. Beyond these two values, there is little other genuine value that the bibliographers try to provide.

•Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki is distinguished by the fact that their business model concentrates on developing value for bibliographers.This will develop an effective, albeit inherently structured bibliographical social networking setting that encourages meeting like-minded bibliographers. Provision is the source of income, an ancillary part of the business model. Generating value is the main focus, if the biliographers are happy then the revenue will follow (assuming of course that proper marketing and financial controls are employed). Concentrating on the bibliogapher's needs beyond contributing to Draft Marketing ideas and maerials/OOoCon2015 flying disc OpenOffice.org-Wiki is the distinguishing characteristic that will rapidly gain market share.
Strategies
The single objective is to position bibliography as the premier place for young professional bibliographers to meet like-minded goals marketing bibliographic ideas and materials. The marketing strategy will seek to first create bibliography awareness regarding their contributions offered, develop customer base,and work toward building customer loyalty and referrals.

The message Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki will seek to communicate is that The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki is THE place to meet intelligent bibliographers. This message will be communicated through a variety of methods. The first method will be advertisements. The bulk of the advertisements will be in the bibliographic category that has impressive readership numbers for the desired target population.

Another method will be through establishing strategic relationships with organizations that have similar demographics such as bibliography. Establishing a mutually beneficial relationship will allow both organizations to develop visibility for each other.

The other form of advertising will be using "grassroots" methods where biblio
graphers will contribute draft marketing ideas and materials for their friends to try for the first time. The contibution will be an economic incentive for the newcomer to try. The contribution will also have the added force of a referral from a friend.

Marketing Mix
Draft Marketing ideas and materials/OOOCon2015 flying disc's OpenOffice.org-Wiki marketing mix is comprised of these following approaches to pricing, distribution, advertising and promotion, and customer service.

•Pricing: the pricing scheme is based on standard industry practices.
•Distribution: all services and products will be distributed from 's retail space.
•Advertising and promotion: the most successful advertising will be with OpenOffice.org. Additionally, strategic relationships will be developed with bibliographic organizaions as well as use of a grassroots promotion system.
•Customer service: obsessive customer attention is the mantra.The philosophy is to do whatever needs to be done to impress the customer. While this could reduce short-term profits, it will strengthen long-term profitability.
Marketing Research
During the initial phases of the marketing plan development, several bibliographic focus groups will be sponsored to gain insight into a variety of likely bibliographers. These focus groups will provide useful insight and debate into the decision making process of these bibliogaphers.

An additional source of dynamic market research is a feedback system based on a suggestion card system.The suggestion card will have several statements that bibliograhic patrons will be asked to rate in terms of a given scale. Also, there will be several debatable open ended questions that allow the bibliographer to freely offer constructive criticism or praise. The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki will work hard to implement reasonable suggestions in order to improve their service offerings as well as show their committment to the bibliographer that their contributions are valued.

The last source of market research will be competitive analysis.This will be done by regularly visiting competitors and analyzing their service offerings.

Read more: A bibliographic/software and standards informative scientific database supports collections of ESL books & reading materials,bibliographic cd's.audio,videos & translated languages of scientific books in English,German,French, Italian,Spanish,Turkish,Japanese & other translations. http://wiki.services.openoffice.org/wiki/User:Blibrestez55/books/Scientific_Bibliographic_Project_2015

[[Marketing]]
[[Category:User Experience
[[[Category:Bibliographic]]
[[Category:User:Blibrestez55/Books/Draft Marketing ideas and materials/OooCon2015 flying disc OpenOffice.org-Wiki]]

Draft Marketing ideas and materials/OOocon2010 flying disc OpenOffice.org

2012-07-14T21:27:49Z

Blibrestez55: *User:Blibrestez55/Books/Draft Marketing ideas and materials/OooCon2015 flying disc OpenOffice.org-Wiki

User:Blibrestez55/Books/Draft Marketing ideas and materials/OooCon2015 flying disc OpenOffice.org-Wiki

Name The name of this organization shall be the BLibrestez55 Draft Marketing ideas and materials/OOoCon2015 flying disc-OpenOffice.org Wiki Bibliographical Debate OpenOffice.org Users Group (herein referred to as the BDMIMOCFDGroup).

Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki Plan

Marketing Strategy
Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki strategy will be based on communicating OpenOffice.org-Wik's value to the targeted segments. This will be done through a variety of methods. The first method will be strategically placed advertisements. One place that will be used for advertisements will be in Bibliographic categories,and the liberal arts categories that details all of the entertainment in OpenOffice.org-Wiki. This will be the main source of advertisements because the demographics of their readership are fairly similar to Bibus bibliographic database-Bibus demographics.

Another source of marketing will be done with strategic relationships with associations that have similar bibliographic demographics. One prime example is the BLibrestez55 bibliographic database. While bibliographic patrons are not necessarily overwhelmingly single, the rest of the demographics match up. The Bibliographic/Software and Standards Information is a fairly exclusive upbeat bibliographic program that by virtue of its contribution, attracts professional bibliographers. The strategic relationship with be mutually beneficial where both organizations will develop visibility for each other.

The other form of advertising will be using "grassroots" methods where bibliographers contribute draft marketing ideas and materials for their friends to try drafting marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki for the first time. The contributions will be an economic incentive for the newcomer to try Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki. The contribution should have the added force of a referral from a friend.

Mission
Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki mission is to provide a bibliographic social network. We exist to attract and maintain bibliographers. When we adhere to this maxim, everything else will fall into place. Our services will exceed the expectations of our bibliographers.

Marketing Objectives
•Develop marketing ideas and material awareness through a steady, month to month increase of new bibliographers.
•Develop an increase in sales of marketing while achieving a status quo state or decrease in marketing expenses.
•Develop awareness of the structured conversation system measured by bibliographers coming to Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki solely for bibliographic social networking groups.
Financial Objectives
•A double digit growth rate for each future year.
•Reduce the variable costs through efficiency gains.
•Reach profitability within the first year.
Target Markets
Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki bibliographers can be broken down into three groups, Generation X,Y, and Baby Boomers.
•Professional: this characteristic is intuitive since the underlying element of Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice-org-Wiki is thoughtful conversation, and most professionals appreciate thought-provoking conversation.
•Income over $40,000: this to a large degree is correlated to the fact that they are professional.
•Age 25-45: the largest group of bibliographers looking for bibliograhy.
Positioning
The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki Group will position itself as a reasonably valued bibliographic social networking group that has an innovative, effective system for allowing bibliographers to meet each other.

The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki Group's positioning will leverage their competitive edge:

•A unique approach to getting bibliographers together called the structured bibliographic system. This system is detailed in the Bibliographic category, please refer to that section for more information.

•This system is a competitive edge because most non-bibliographers do not have a niche that they are concentrating on. While every bibliographer has a certain "flavor" and that is why someone will choose one bibliographer or another, the flavor is only surface deep. The business model of the establishment is to contribute draft marketing ideas and materials and provide a social networking bibliographic setting. Beyond these two values, there is little other genuine value that the bibliographers try to provide.

•Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki is distinguished by the fact that their business model concentrates on developing value for bibliographers.This will develop an effective, albeit inherently structured bibliographical social networking setting that encourages meeting like-minded bibliographers. Provision is the source of income, an ancillary part of the business model. Generating value is the main focus, if the biliographers are happy then the revenue will follow (assuming of course that proper marketing and financial controls are employed). Concentrating on the bibliogapher's needs beyond contributing to Draft Marketing ideas and maerials/OOoCon2015 flying disc OpenOffice.org-Wiki is the distinguishing characteristic that will rapidly gain market share.
Strategies
The single objective is to position bibliography as the premier place for young professional bibliographers to meet like-minded goals marketing bibliographic ideas and materials. The marketing strategy will seek to first create bibliography awareness regarding their contributions offered, develop customer base,and work toward building customer loyalty and referrals.

The message Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki will seek to communicate is that The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki is THE place to meet intelligent bibliographers. This message will be communicated through a variety of methods. The first method will be advertisements. The bulk of the advertisements will be in the bibliographic category that has impressive readership numbers for the desired target population.

Another method will be through establishing strategic relationships with organizations that have similar demographics such as bibliography. Establishing a mutually beneficial relationship will allow both organizations to develop visibility for each other.

The other form of advertising will be using "grassroots" methods where biblio
graphers will contribute draft marketing ideas and materials for their friends to try for the first time. The contibution will be an economic incentive for the newcomer to try. The contribution will also have the added force of a referral from a friend.

Marketing Mix
Draft Marketing ideas and materials/OOOCon2015 flying disc's OpenOffice.org-Wiki marketing mix is comprised of these following approaches to pricing, distribution, advertising and promotion, and customer service.

•Pricing: the pricing scheme is based on standard industry practices.
•Distribution: all services and products will be distributed from 's retail space.
•Advertising and promotion: the most successful advertising will be with OpenOffice.org. Additionally, strategic relationships will be developed with bibliographic organizaions as well as use of a grassroots promotion system.
•Customer service: obsessive customer attention is the mantra.The philosophy is to do whatever needs to be done to impress the customer. While this could reduce short-term profits, it will strengthen long-term profitability.
Marketing Research
During the initial phases of the marketing plan development, several bibliographic focus groups will be sponsored to gain insight into a variety of likely bibliographers. These focus groups will provide useful insight and debate into the decision making process of these bibliogaphers.

An additional source of dynamic market research is a feedback system based on a suggestion card system.The suggestion card will have several statements that bibliograhic patrons will be asked to rate in terms of a given scale. Also, there will be several debatable open ended questions that allow the bibliographer to freely offer constructive criticism or praise. The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki will work hard to implement reasonable suggestions in order to improve their service offerings as well as show their committment to the bibliographer that their contributions are valued.

The last source of market research will be competitive analysis.This will be done by regularly visiting competitors and analyzing their service offerings.

Read more: A bibliographic/software and standards informative scientific database supports collections of ESL books & reading materials,bibliographic cd's.audio,videos & translated languages of scientific books in English,German,French, Italian,Spanish,Turkish,Japanese & other translations. http://wiki.services.openoffice.org/wiki/User:Blibrestez55/books/Scientific_Bibliographic_Project_2015

[[Category:User Experience
[[[Category:Bibliographic]]
[[Category: PDL License]]
[[Category:Documentation]]
[[Category:Developer's Guide]]
[[Category:Drawing]]
[[Category:Documents]]
[[Category:Presentation Documents]]

Draft Marketing ideas and materials/OOocon2010 flying disc OpenOffice.org

2012-07-14T21:17:53Z

Blibrestez55: *User:Blibrestez55/Books/Draft Marketing ideas and materials/OooCon2015 flying disc OpenOffice.org-Wiki

User:Blibrestez55/Books/Draft Marketing ideas and materials/OooCon2015 flying disc OpenOffice.org-Wiki

Name The name of this organization shall be the BLibrestez55 Draft Marketing ideas and materials/OOoCon2015 flying disc-OpenOffice.org Wiki Bibliographical Debate OpenOffice.org Users Group (herein referred to as the BDMIMOCFDGroup).

Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki Plan

Marketing Strategy
Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki strategy will be based on communicating OpenOffice.org-Wik's value to the targeted segments. This will be done through a variety of methods. The first method will be strategically placed advertisements. One place that will be used for advertisements will be in Bibliographic categories,and the liberal arts categories that details all of the entertainment in OpenOffice.org-Wiki. This will be the main source of advertisements because the demographics of their readership are fairly similar to Bibus bibliographic database-Bibus demographics.

Another source of marketing will be done with strategic relationships with associations that have similar bibliographic demographics. One prime example is the BLibrestez55 bibliographic database. While bibliographic patrons are not necessarily overwhelmingly single, the rest of the demographics match up. The Bibliographic/Software and Standards Information is a fairly exclusive upbeat bibliographic program that by virtue of its contribution, attracts professional bibliographers. The strategic relationship with be mutually beneficial where both organizations will develop visibility for each other.

The other form of advertising will be using "grassroots" methods where bibliographers contribute draft marketing ideas and materials for their friends to try drafting marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki for the first time. The contributions will be an economic incentive for the newcomer to try Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki. The contribution should have the added force of a referral from a friend.

Mission
Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki mission is to provide a bibliographic social network. We exist to attract and maintain bibliographers. When we adhere to this maxim, everything else will fall into place. Our services will exceed the expectations of our bibliographers.

Marketing Objectives
•Develop marketing ideas and material awareness through a steady, month to month increase of new bibliographers.
•Develop an increase in sales of marketing while achieving a status quo state or decrease in marketing expenses.
•Develop awareness of the structured conversation system measured by bibliographers coming to Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki solely for bibliographic social networking groups.
Financial Objectives
•A double digit growth rate for each future year.
•Reduce the variable costs through efficiency gains.
•Reach profitability within the first year.
Target Markets
Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki bibliographers can be broken down into three groups, Generation X,Y, and Baby Boomers.
•Professional: this characteristic is intuitive since the underlying element of Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice-org-Wiki is thoughtful conversation, and most professionals appreciate thought-provoking conversation.
•Income over $40,000: this to a large degree is correlated to the fact that they are professional.
•Age 25-45: the largest group of bibliographers looking for bibliograhy.
Positioning
The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki Group will position itself as a reasonably valued bibliographic social networking group that has an innovative, effective system for allowing bibliographers to meet each other.

The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki Group's positioning will leverage their competitive edge:

•A unique approach to getting bibliographers together called the structured bibliographic system. This system is detailed in the Bibliographic category, please refer to that section for more information.

•This system is a competitive edge because most non-bibliographers do not have a niche that they are concentrating on. While every bibliographer has a certain "flavor" and that is why someone will choose one bibliographer or another, the flavor is only surface deep. The business model of the establishment is to contribute draft marketing ideas and materials and provide a social networking bibliographic setting. Beyond these two values, there is little other genuine value that the bibliographers try to provide.

•Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki is distinguished by the fact that their business model concentrates on developing value for bibliographers.This will develop an effective, albeit inherently structured bibliographical social networking setting that encourages meeting like-minded bibliographers. Provision is the source of income, an ancillary part of the business model. Generating value is the main focus, if the biliographers are happy then the revenue will follow (assuming of course that proper marketing and financial controls are employed). Concentrating on the bibliogapher's needs beyond contributing to Draft Marketing ideas and maerials/OOoCon2015 flying disc OpenOffice.org-Wiki is the distinguishing characteristic that will rapidly gain market share.
Strategies
The single objective is to position bibliography as the premier place for young professional bibliographers to meet like-minded goals marketing bibliographic ideas and materials. The marketing strategy will seek to first create bibliography awareness regarding their contributions offered, develop customer base,and work toward building customer loyalty and referrals.

The message Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki will seek to communicate is that The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki is THE place to meet intelligent bibliographers. This message will be communicated through a variety of methods. The first method will be advertisements. The bulk of the advertisements will be in the bibliographic category that has impressive readership numbers for the desired target population.

Another method will be through establishing strategic relationships with organizations that have similar demographics such as bibliography. Establishing a mutually beneficial relationship will allow both organizations to develop visibility for each other.

The other form of advertising will be using "grassroots" methods where biblio
graphers will contribute draft marketing ideas and materials for their friends to try for the first time. The contibution will be an economic incentive for the newcomer to try. The contribution will also have the added force of a referral from a friend.

Marketing Mix
Draft Marketing ideas and materials/OOOCon2015 flying disc's OpenOffice.org-Wiki marketing mix is comprised of these following approaches to pricing, distribution, advertising and promotion, and customer service.

•Pricing: the pricing scheme is based on standard industry practices.
•Distribution: all services and products will be distributed from 's retail space.
•Advertising and promotion: the most successful advertising will be with OpenOffice.org. Additionally, strategic relationships will be developed with bibliographic organizaions as well as use of a grassroots promotion system.
•Customer service: obsessive customer attention is the mantra.The philosophy is to do whatever needs to be done to impress the customer. While this could reduce short-term profits, it will strengthen long-term profitability.
Marketing Research
During the initial phases of the marketing plan development, several bibliographic focus groups will be sponsored to gain insight into a variety of likely bibliographers. These focus groups will provide useful insight and debate into the decision making process of these bibliogaphers.

An additional source of dynamic market research is a feedback system based on a suggestion card system.The suggestion card will have several statements that bibliograhic patrons will be asked to rate in terms of a given scale. Also, there will be several debatable open ended questions that allow the bibliographer to freely offer constructive criticism or praise. The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki will work hard to implement reasonable suggestions in order to improve their service offerings as well as show their committment to the bibliographer that their contributions are valued.

The last source of market research will be competitive analysis.This will be done by regularly visiting competitors and analyzing their service offerings.

Read more: A bibliographic/software and standards informative scientific database supports collections of ESL books & reading materials,bibliographic cd's.audio,videos & translated languages of scientific books in English,German,French, Italian,Spanish,Turkish,Japanese & other translations. http://wiki.services.openoffice.org/wiki/User:Blibrestez55/books/Scientific_Bibliographic_Project_2015

[[Category:Niche Marketing]]
[[Category:Bibliographic]]
[[Category: PDL License]]
[[Category:Documentation]]
[[Category:Developer's Guide]]
[[Category:Drawing]]
[[Category:Documents and Presentation Documents]]

Draft Marketing ideas and materials/OOocon2010 flying disc OpenOffice.org

2012-07-14T21:15:59Z

Blibrestez55: *User:Blibrestez55/Books/Draft Marketing ideas and materials/OooCon2015 flying disc OpenOffice.org-Wiki

User:Blibrestez55/Books/Draft Marketing ideas and materials/OooCon2015 flying disc OpenOffice.org-Wiki

Name The name of this organization shall be the BLibrestez55 Draft Marketing ideas and materials/OOoCon2015 flying disc-OpenOffice.org Wiki Bibliographical Debate OpenOffice.org Users Group (herein referred to as the BDMIMOCFDGroup).

Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki Plan

Marketing Strategy
Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki strategy will be based on communicating OpenOffice.org-Wik's value to the targeted segments. This will be done through a variety of methods. The first method will be strategically placed advertisements. One place that will be used for advertisements will be in Bibliographic categories,and the liberal arts categories that details all of the entertainment in OpenOffice.org-Wiki. This will be the main source of advertisements because the demographics of their readership are fairly similar to Bibus bibliographic database-Bibus demographics.

Another source of marketing will be done with strategic relationships with associations that have similar bibliographic demographics. One prime example is the BLibrestez55 bibliographic database. While bibliographic patrons are not necessarily overwhelmingly single, the rest of the demographics match up. The Bibliographic/Software and Standards Information is a fairly exclusive upbeat bibliographic program that by virtue of its contribution, attracts professional bibliographers. The strategic relationship with be mutually beneficial where both organizations will develop visibility for each other.

The other form of advertising will be using "grassroots" methods where bibliographers contribute draft marketing ideas and materials for their friends to try drafting marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki for the first time. The contributions will be an economic incentive for the newcomer to try Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki. The contribution should have the added force of a referral from a friend.

Mission
Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki mission is to provide a bibliographic social network. We exist to attract and maintain bibliographers. When we adhere to this maxim, everything else will fall into place. Our services will exceed the expectations of our bibliographers.

Marketing Objectives
•Develop marketing ideas and material awareness through a steady, month to month increase of new bibliographers.
•Develop an increase in sales of marketing while achieving a status quo state or decrease in marketing expenses.
•Develop awareness of the structured conversation system measured by bibliographers coming to Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki solely for bibliographic social networking groups.
Financial Objectives
•A double digit growth rate for each future year.
•Reduce the variable costs through efficiency gains.
•Reach profitability within the first year.
Target Markets
Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki bibliographers can be broken down into three groups, Generation X,Y, and Baby Boomers.
•Professional: this characteristic is intuitive since the underlying element of Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice-org-Wiki is thoughtful conversation, and most professionals appreciate thought-provoking conversation.
•Income over $40,000: this to a large degree is correlated to the fact that they are professional.
•Age 25-45: the largest group of bibliographers looking for bibliograhy.
Positioning
The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki Group will position itself as a reasonably valued bibliographic social networking group that has an innovative, effective system for allowing bibliographers to meet each other.

The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki Group's positioning will leverage their competitive edge:

•A unique approach to getting bibliographers together called the structured bibliographic system. This system is detailed in the Bibliographic category, please refer to that section for more information.

•This system is a competitive edge because most non-bibliographers do not have a niche that they are concentrating on. While every bibliographer has a certain "flavor" and that is why someone will choose one bibliographer or another, the flavor is only surface deep. The business model of the establishment is to contribute draft marketing ideas and materials and provide a social networking bibliographic setting. Beyond these two values, there is little other genuine value that the bibliographers try to provide.

•Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki is distinguished by the fact that their business model concentrates on developing value for bibliographers.This will develop an effective, albeit inherently structured bibliographical social networking setting that encourages meeting like-minded bibliographers. Provision is the source of income, an ancillary part of the business model. Generating value is the main focus, if the biliographers are happy then the revenue will follow (assuming of course that proper marketing and financial controls are employed). Concentrating on the bibliogapher's needs beyond contributing to Draft Marketing ideas and maerials/OOoCon2015 flying disc OpenOffice.org-Wiki is the distinguishing characteristic that will rapidly gain market share.
Strategies
The single objective is to position bibliography as the premier place for young professional bibliographers to meet like-minded goals marketing bibliographic ideas and materials. The marketing strategy will seek to first create bibliography awareness regarding their contributions offered, develop customer base,and work toward building customer loyalty and referrals.

The message Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki will seek to communicate is that The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki is THE place to meet intelligent bibliographers. This message will be communicated through a variety of methods. The first method will be advertisements. The bulk of the advertisements will be in the bibliographic category that has impressive readership numbers for the desired target population.

Another method will be through establishing strategic relationships with organizations that have similar demographics such as bibliography. Establishing a mutually beneficial relationship will allow both organizations to develop visibility for each other.

The other form of advertising will be using "grassroots" methods where biblio
graphers will contribute draft marketing ideas and materials for their friends to try for the first time. The contibution will be an economic incentive for the newcomer to try. The contribution will also have the added force of a referral from a friend.

Marketing Mix
Draft Marketing ideas and materials/OOOCon2015 flying disc's OpenOffice.org-Wiki marketing mix is comprised of these following approaches to pricing, distribution, advertising and promotion, and customer service.

•Pricing: the pricing scheme is based on standard industry practices.
•Distribution: all services and products will be distributed from 's retail space.
•Advertising and promotion: the most successful advertising will be with OpenOffice.org. Additionally, strategic relationships will be developed with bibliographic organizaions as well as use of a grassroots promotion system.
•Customer service: obsessive customer attention is the mantra.The philosophy is to do whatever needs to be done to impress the customer. While this could reduce short-term profits, it will strengthen long-term profitability.
Marketing Research
During the initial phases of the marketing plan development, several bibliographic focus groups will be sponsored to gain insight into a variety of likely bibliographers. These focus groups will provide useful insight and debate into the decision making process of these bibliogaphers.

An additional source of dynamic market research is a feedback system based on a suggestion card system.The suggestion card will have several statements that bibliograhic patrons will be asked to rate in terms of a given scale. Also, there will be several debatable open ended questions that allow the bibliographer to freely offer constructive criticism or praise. The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki will work hard to implement reasonable suggestions in order to improve their service offerings as well as show their committment to the bibliographer that their contributions are valued.

The last source of market research will be competitive analysis.This will be done by regularly visiting competitors and analyzing their service offerings.

Read more: A bibliographic/software and standards informative scientific database supports collections of ESL books & reading materials,bibliographic cd's.audio,videos & translated languages of scientific books in English,German,French, Italian,Spanish,Turkish,Japanese & other translations. http://wiki.services.openoffice.org/wiki/User:Blibrestez55/books/Scientific_Bibliographic_Project_2015

[[Category:Niche Marketing]]
[[Category:Bibliographic]]
[[Category: PDL License]]
[[Category:Documentation]]
[[Category:Developer's Guide]]
[[Category:Drawing Documents and Presentation Documents]]

Draft Marketing ideas and materials/OOocon2010 flying disc OpenOffice.org

2012-07-14T21:12:05Z

Blibrestez55: *User:Blibrestez55/Books/Draft Marketing ideas and materials/OooCon2015 flying disc OpenOffice.org-Wiki

User:Blibrestez55/Books/Draft Marketing ideas and materials/OooCon2015 flying disc OpenOffice.org-Wiki

Name The name of this organization shall be the BLibrestez55 Draft Marketing ideas and materials/OOoCon2015 flying disc-OpenOffice.org Wiki Bibliographical Debate OpenOffice.org Users Group (herein referred to as the BDMIMOCFDGroup).

Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki Plan

Marketing Strategy
Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki strategy will be based on communicating OpenOffice.org-Wik's value to the targeted segments. This will be done through a variety of methods. The first method will be strategically placed advertisements. One place that will be used for advertisements will be in Bibliographic categories,and the liberal arts categories that details all of the entertainment in OpenOffice.org-Wiki. This will be the main source of advertisements because the demographics of their readership are fairly similar to Bibus bibliographic database-Bibus demographics.

Another source of marketing will be done with strategic relationships with associations that have similar bibliographic demographics. One prime example is the BLibrestez55 bibliographic database. While bibliographic patrons are not necessarily overwhelmingly single, the rest of the demographics match up. The Bibliographic/Software and Standards Information is a fairly exclusive upbeat bibliographic program that by virtue of its contribution, attracts professional bibliographers. The strategic relationship with be mutually beneficial where both organizations will develop visibility for each other.

The other form of advertising will be using "grassroots" methods where bibliographers contribute draft marketing ideas and materials for their friends to try drafting marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki for the first time. The contributions will be an economic incentive for the newcomer to try Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki. The contribution should have the added force of a referral from a friend.

Mission
Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki mission is to provide a bibliographic social network. We exist to attract and maintain bibliographers. When we adhere to this maxim, everything else will fall into place. Our services will exceed the expectations of our bibliographers.

Marketing Objectives
•Develop marketing ideas and material awareness through a steady, month to month increase of new bibliographers.
•Develop an increase in sales of marketing while achieving a status quo state or decrease in marketing expenses.
•Develop awareness of the structured conversation system measured by bibliographers coming to Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki solely for bibliographic social networking groups.
Financial Objectives
•A double digit growth rate for each future year.
•Reduce the variable costs through efficiency gains.
•Reach profitability within the first year.
Target Markets
Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki bibliographers can be broken down into three groups, Generation X,Y, and Baby Boomers.
•Professional: this characteristic is intuitive since the underlying element of Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice-org-Wiki is thoughtful conversation, and most professionals appreciate thought-provoking conversation.
•Income over $40,000: this to a large degree is correlated to the fact that they are professional.
•Age 25-45: the largest group of bibliographers looking for bibliograhy.
Positioning
The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki Group will position itself as a reasonably valued bibliographic social networking group that has an innovative, effective system for allowing bibliographers to meet each other.

The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki Group's positioning will leverage their competitive edge:

•A unique approach to getting bibliographers together called the structured bibliographic system. This system is detailed in the Bibliographic category, please refer to that section for more information.

•This system is a competitive edge because most non-bibliographers do not have a niche that they are concentrating on. While every bibliographer has a certain "flavor" and that is why someone will choose one bibliographer or another, the flavor is only surface deep. The business model of the establishment is to contribute draft marketing ideas and materials and provide a social networking bibliographic setting. Beyond these two values, there is little other genuine value that the bibliographers try to provide.

•Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki is distinguished by the fact that their business model concentrates on developing value for bibliographers.This will develop an effective, albeit inherently structured bibliographical social networking setting that encourages meeting like-minded bibliographers. Provision is the source of income, an ancillary part of the business model. Generating value is the main focus, if the biliographers are happy then the revenue will follow (assuming of course that proper marketing and financial controls are employed). Concentrating on the bibliogapher's needs beyond contributing to Draft Marketing ideas and maerials/OOoCon2015 flying disc OpenOffice.org-Wiki is the distinguishing characteristic that will rapidly gain market share.
Strategies
The single objective is to position bibliography as the premier place for young professional bibliographers to meet like-minded goals marketing bibliographic ideas and materials. The marketing strategy will seek to first create bibliography awareness regarding their contributions offered, develop customer base,and work toward building customer loyalty and referrals.

The message Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki will seek to communicate is that The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki is THE place to meet intelligent bibliographers. This message will be communicated through a variety of methods. The first method will be advertisements. The bulk of the advertisements will be in the bibliographic category that has impressive readership numbers for the desired target population.

Another method will be through establishing strategic relationships with organizations that have similar demographics such as bibliography. Establishing a mutually beneficial relationship will allow both organizations to develop visibility for each other.

The other form of advertising will be using "grassroots" methods where biblio
graphers will contribute draft marketing ideas and materials for their friends to try for the first time. The contibution will be an economic incentive for the newcomer to try. The contribution will also have the added force of a referral from a friend.

Marketing Mix
Draft Marketing ideas and materials/OOOCon2015 flying disc's OpenOffice.org-Wiki marketing mix is comprised of these following approaches to pricing, distribution, advertising and promotion, and customer service.

•Pricing: the pricing scheme is based on standard industry practices.
•Distribution: all services and products will be distributed from 's retail space.
•Advertising and promotion: the most successful advertising will be with OpenOffice.org. Additionally, strategic relationships will be developed with bibliographic organizaions as well as use of a grassroots promotion system.
•Customer service: obsessive customer attention is the mantra.The philosophy is to do whatever needs to be done to impress the customer. While this could reduce short-term profits, it will strengthen long-term profitability.
Marketing Research
During the initial phases of the marketing plan development, several bibliographic focus groups will be sponsored to gain insight into a variety of likely bibliographers. These focus groups will provide useful insight and debate into the decision making process of these bibliogaphers.

An additional source of dynamic market research is a feedback system based on a suggestion card system.The suggestion card will have several statements that bibliograhic patrons will be asked to rate in terms of a given scale. Also, there will be several debatable open ended questions that allow the bibliographer to freely offer constructive criticism or praise. The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki will work hard to implement reasonable suggestions in order to improve their service offerings as well as show their committment to the bibliographer that their contributions are valued.

The last source of market research will be competitive analysis.This will be done by regularly visiting competitors and analyzing their service offerings.

Read more: A bibliographic/software and standards informative scientific database supports collections of ESL books & reading materials,bibliographic cd's.audio,videos & translated languages of scientific books in English,German,French, Italian,Spanish,Turkish,Japanese & other translations. http://wiki.services.openoffice.org/wiki/User:Blibrestez55/books/Scientific_Bibliographic_Project_2015

[[Category:Bibliographic]]
[[Categories: PDL License | Documentation/Developer's Guide/Drawing Documents and Presentation Documents]]

User:Blibrestez55/Books/Dokumentation Tos/Calc:/Statistics Project2015

2012-06-04T12:16:08Z

Blibrestez55: /* BLibrestez55 Statistics TOS/Calc: Derivation of Financial Formulas Survey Project */

{{saved_book}}

== BLibrestez55 Statistics Project ==
=== BLibrestez55 Statistics Survey Project ===
;BLibrestez55 Derivation of Financial Formulas Project
:[[Documentation/How Tos/Calc: COUPDAYSNC function]]
:[[Documentation/How Tos/Calc: COUPPCD function]]
:[[Documentation/How Tos/Calc: Derivation of Financial Formulas]]
:[[Documentation/How Tos/Calc: Financial functions]]
:[[Documentation/How Tos/Calc: ODDFPRICE function]]
:[[Documentation/How Tos/Calc: ODDFYIELD function]]
:[[Documentation/How Tos/Calc: ODDLPRICE function]]
:[[Documentation/How Tos/Calc: ODDLYIELD function]]
:[[Documentation/How Tos/Calc: PRICE function]]
:[[Documentation/How Tos/Calc: PRICEMAT function]]
:[[Documentation/How Tos/Calc: YIELDMAT function]]
:[[JA/translation/User Survey 2]]
:[[Major OpenOffice.org Deployments]]
:[[Wiki/statistics]]
:[[Documentation/How Tos/Calc: Date & Time functions]]
:[[Category:Documentation/Reference/Calc]]
:[[Category:Documentation/Reference]]
:[[Category:Documentation]]
:[[Category:MainIndex]]
:[[Category:Project]]
:[[SVG Import Source Code]]
:[[Category:SVG]]
:[[Category:Build System]]
:[[Category:Development]]
:[[Category:Tools]]

[[Category:Books|Statistics Project2015]]

User:Blibrestez55/Books/Dokumentation Tos/Calc:/Statistics Project2015

2012-06-04T06:04:42Z

Blibrestez55: Created page with "{{saved_book}} == BLibrestez55 Statistics Project == === BLibrestez55 Statistics Survey Project === ;BLibrestez55 Deriiation of Financial Formulas Project :[[Documentation/How T…"

{{saved_book}}

== BLibrestez55 Statistics Project ==
=== BLibrestez55 Statistics Survey Project ===
;BLibrestez55 Deriiation of Financial Formulas Project
:[[Documentation/How Tos/Calc: COUPDAYSNC function]]
:[[Documentation/How Tos/Calc: COUPPCD function]]
:[[Documentation/How Tos/Calc: Derivation of Financial Formulas]]
:[[Documentation/How Tos/Calc: Financial functions]]
:[[Documentation/How Tos/Calc: ODDFPRICE function]]
:[[Documentation/How Tos/Calc: ODDFYIELD function]]
:[[Documentation/How Tos/Calc: ODDLPRICE function]]
:[[Documentation/How Tos/Calc: ODDLYIELD function]]
:[[Documentation/How Tos/Calc: PRICE function]]
:[[Documentation/How Tos/Calc: PRICEMAT function]]
:[[Documentation/How Tos/Calc: YIELDMAT function]]
:[[JA/translation/User Survey 2]]
:[[Major OpenOffice.org Deployments]]
:[[Wiki/statistics]]
:[[Documentation/How Tos/Calc: Date & Time functions]]
:[[Category:Documentation/Reference/Calc]]
:[[Category:Documentation/Reference]]
:[[Category:Documentation]]
:[[Category:MainIndex]]
:[[Category:Project]]
:[[SVG Import Source Code]]
:[[Category:SVG]]
:[[Category:Build System]]
:[[Category:Development]]
:[[Category:Tools]]

[[Category:Books|Statistics Project2015]]

User:Blibrestez55/Books/Stratistics Project 2015

2012-06-04T05:55:09Z

Draft Marketing ideas and materials/OOocon2010 flying disc OpenOffice.org

2012-02-08T01:10:06Z

Blibrestez55: *Blibrestez55 Draft Marketing ideas and materials/OOocon2010-2020

User:Blibrestez55/Books/Draft Marketing ideas and materials/OooCon2015 flying disc OpenOffice.org-Wiki

Name The name of this organization shall be the BLibrestez55 Draft Marketing ideas and materials/OOoCon2015 flying disc-OpenOffice.org Wiki Bibliographical Debate OpenOffice.org Users Group (herein referred to as the BDMIMOCFDGroup).

Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki Plan

Marketing Strategy
Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki strategy will be based on communicating OpenOffice.org-Wik's value to the targeted segments. This will be done through a variety of methods. The first method will be strategically placed advertisements. One place that will be used for advertisements will be in Bibliographic categories,and the liberal arts categories that details all of the entertainment in OpenOffice.org-Wiki. This will be the main source of advertisements because the demographics of their readership are fairly similar to Bibus bibliographic database-Bibus demographics.

Another source of marketing will be done with strategic relationships with associations that have similar bibliographic demographics. One prime example is the BLibrestez55 bibliographic database. While bibliographic patrons are not necessarily overwhelmingly single, the rest of the demographics match up. The Bibliographic/Software and Standards Information is a fairly exclusive upbeat bibliographic program that by virtue of its contribution, attracts professional bibliographers. The strategic relationship with be mutually beneficial where both organizations will develop visibility for each other.

The other form of advertising will be using "grassroots" methods where bibliographers contribute draft marketing ideas and materials for their friends to try drafting marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki for the first time. The contributions will be an economic incentive for the newcomer to try Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki. The contribution should have the added force of a referral from a friend.

Mission
Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki mission is to provide a bibliographic social network. We exist to attract and maintain bibliographers. When we adhere to this maxim, everything else will fall into place. Our services will exceed the expectations of our bibliographers.

Marketing Objectives
•Develop marketing ideas and material awareness through a steady, month to month increase of new bibliographers.
•Develop an increase in sales of marketing while achieving a status quo state or decrease in marketing expenses.
•Develop awareness of the structured conversation system measured by bibliographers coming to Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki solely for bibliographic social networking groups.
Financial Objectives
•A double digit growth rate for each future year.
•Reduce the variable costs through efficiency gains.
•Reach profitability within the first year.
Target Markets
Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki bibliographers can be broken down into three groups, Generation X,Y, and Baby Boomers.
•Professional: this characteristic is intuitive since the underlying element of Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice-org-Wiki is thoughtful conversation, and most professionals appreciate thought-provoking conversation.
•Income over $40,000: this to a large degree is correlated to the fact that they are professional.
•Age 25-45: the largest group of bibliographers looking for bibliograhy.
Positioning
The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki Group will position itself as a reasonably valued bibliographic social networking group that has an innovative, effective system for allowing bibliographers to meet each other.

The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki Group's positioning will leverage their competitive edge:

•A unique approach to getting bibliographers together called the structured bibliographic system. This system is detailed in the Bibliographic category, please refer to that section for more information.

•This system is a competitive edge because most non-bibliographers do not have a niche that they are concentrating on. While every bibliographer has a certain "flavor" and that is why someone will choose one bibliographer or another, the flavor is only surface deep. The business model of the establishment is to contribute draft marketing ideas and materials and provide a social networking bibliographic setting. Beyond these two values, there is little other genuine value that the bibliographers try to provide.

•Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki is distinguished by the fact that their business model concentrates on developing value for bibliographers.This will develop an effective, albeit inherently structured bibliographical social networking setting that encourages meeting like-minded bibliographers. Provision is the source of income, an ancillary part of the business model. Generating value is the main focus, if the biliographers are happy then the revenue will follow (assuming of course that proper marketing and financial controls are employed). Concentrating on the bibliogapher's needs beyond contributing to Draft Marketing ideas and maerials/OOoCon2015 flying disc OpenOffice.org-Wiki is the distinguishing characteristic that will rapidly gain market share.
Strategies
The single objective is to position bibliography as the premier place for young professional bibliographers to meet like-minded goals marketing bibliographic ideas and materials. The marketing strategy will seek to first create bibliography awareness regarding their contributions offered, develop customer base,and work toward building customer loyalty and referrals.

The message Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki will seek to communicate is that The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki is THE place to meet intelligent bibliographers. This message will be communicated through a variety of methods. The first method will be advertisements. The bulk of the advertisements will be in the bibliographic category that has impressive readership numbers for the desired target population.

Another method will be through establishing strategic relationships with organizations that have similar demographics such as bibliography. Establishing a mutually beneficial relationship will allow both organizations to develop visibility for each other.

The other form of advertising will be using "grassroots" methods where biblio
graphers will contribute draft marketing ideas and materials for their friends to try for the first time. The contibution will be an economic incentive for the newcomer to try. The contribution will also have the added force of a referral from a friend.

Marketing Mix
Draft Marketing ideas and materials/OOOCon2015 flying disc's OpenOffice.org-Wiki marketing mix is comprised of these following approaches to pricing, distribution, advertising and promotion, and customer service.

•Pricing: the pricing scheme is based on standard industry practices.
•Distribution: all services and products will be distributed from 's retail space.
•Advertising and promotion: the most successful advertising will be with OpenOffice.org. Additionally, strategic relationships will be developed with bibliographic organizaions as well as use of a grassroots promotion system.
•Customer service: obsessive customer attention is the mantra.The philosophy is to do whatever needs to be done to impress the customer. While this could reduce short-term profits, it will strengthen long-term profitability.
Marketing Research
During the initial phases of the marketing plan development, several bibliographic focus groups will be sponsored to gain insight into a variety of likely bibliographers. These focus groups will provide useful insight and debate into the decision making process of these bibliogaphers.

An additional source of dynamic market research is a feedback system based on a suggestion card system.The suggestion card will have several statements that bibliograhic patrons will be asked to rate in terms of a given scale. Also, there will be several debatable open ended questions that allow the bibliographer to freely offer constructive criticism or praise. The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki will work hard to implement reasonable suggestions in order to improve their service offerings as well as show their committment to the bibliographer that their contributions are valued.

The last source of market research will be competitive analysis.This will be done by regularly visiting competitors and analyzing their service offerings.

Read more: A bibliographic/software and standards informative scientific database supports collections of ESL books & reading materials,bibliographic cd's.audio,videos & translated languages of scientific books in English,German,French, Italian,Spanish,Turkish,Japanese & other translations. http://wiki.services.openoffice.org/wiki/User:Blibrestez55/books/Scientific_Bibliographic_Project_2015

[[Category:Bibliographic]]

User:Blibrestez55/Books/Certification Theories

2012-02-01T07:15:17Z

Blibrestez55: Created page with "{{saved_book}} == BLibrestez55 Certification Courses == === BLibrestez55 Certification Reports === ;Blibrestez55 Certification Composition :Certification/1 General [[Catego…"

{{saved_book}}

== BLibrestez55 Certification Courses ==
=== BLibrestez55 Certification Reports ===
;Blibrestez55 Certification Composition
:[[Certification/1 General]]

[[Category:Books|Certification Theories]]

Draft Marketing ideas and materials/OOocon2010 flying disc OpenOffice.org

2011-10-01T15:17:13Z

Blibrestez55: *BLibrestez55 Draft Marketing ideas and materials/OOoCon2015 flying disc-OpenOffice.org Wiki Bibliographical Debate OpenOffice.org Users Group (herein referred to as the BDMIMOCFDGroup).

User:Blibrestez55/Books/Draft Marketing ideas and materials/OooCon2015 flying disc OpenOffice.org-Wiki

Name The name of this organization shall be the BLibrestez55 Draft Marketing ideas and materials/OOoCon2015 flying disc-OpenOffice.org Wiki Bibliographical Debate OpenOffice.org Users Group (herein referred to as the BDMIMOCFDGroup).

Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki Plan

Marketing Strategy
Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki strategy will be based on communicating OpenOffice.org-Wik's value to the targeted segments. This will be done through a variety of methods. The first method will be strategically placed advertisements. One place that will be used for advertisements will be in Bibliographic categories,and the liberal arts categories that details all of the entertainment in OpenOffice.org-Wiki. This will be the main source of advertisements because the demographics of their readership are fairly similar to Bibus bibliographic database-Bibus demographics.

Another source of marketing will be done with strategic relationships with associations that have similar bibliographic demographics. One prime example is the BLibrestez55 bibliographic database. While bibliographic patrons are not necessarily overwhelmingly single, the rest of the demographics match up. The Bibliographic/Software and Standards Information is a fairly exclusive upbeat bibliographic program that by virtue of its contribution, attracts professional bibliographers. The strategic relationship with be mutually beneficial where both organizations will develop visibility for each other.

The other form of advertising will be using "grassroots" methods where bibliographers contribute draft marketing ideas and materials for their friends to try drafting marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki for the first time. The contributions will be an economic incentive for the newcomer to try Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki. The contribution should have the added force of a referral from a friend.

Mission
Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki mission is to provide a bibliographic social network. We exist to attract and maintain bibliographers. When we adhere to this maxim, everything else will fall into place. Our services will exceed the expectations of our bibliographers.

Marketing Objectives
•Develop marketing ideas and material awareness through a steady, month to month increase of new bibliographers.
•Develop an increase in sales of marketing while achieving a status quo state or decrease in marketing expenses.
•Develop awareness of the structured conversation system measured by bibliographers coming to Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki solely for bibliographic social networking groups.
Financial Objectives
•A double digit growth rate for each future year.
•Reduce the variable costs through efficiency gains.
•Reach profitability within the first year.
Target Markets
Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki bibliographers can be broken down into three groups, Generation X,Y, and Baby Boomers.
•Professional: this characteristic is intuitive since the underlying element of Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice-org-Wiki is thoughtful conversation, and most professionals appreciate thought-provoking conversation.
•Income over $40,000: this to a large degree is correlated to the fact that they are professional.
•Age 25-45: the largest group of bibliographers looking for bibliograhy.
Positioning
The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki Group will position itself as a reasonably valued bibliographic social networking group that has an innovative, effective system for allowing bibliographers to meet each other.

The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki Group's positioning will leverage their competitive edge:

•A unique approach to getting bibliographers together called the structured bibliographic system. This system is detailed in the Bibliographic category, please refer to that section for more information.

•This system is a competitive edge because most non-bibliographers do not have a niche that they are concentrating on. While every bibliographer has a certain "flavor" and that is why someone will choose one bibliographer or another, the flavor is only surface deep. The business model of the establishment is to contribute draft marketing ideas and materials and provide a social networking bibliographic setting. Beyond these two values, there is little other genuine value that the bibliographers try to provide.

•Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki is distinguished by the fact that their business model concentrates on developing value for bibliographers.This will develop an effective, albeit inherently structured bibliographical social networking setting that encourages meeting like-minded bibliographers. Providing is the source of income, an ancillary part of the business model. Generating value for the is the main focus, if the biliographers are happy then the revenue will follow (assuming of course that proper marketing and financial controls are employed). Concentrating on the bibliogapher's needs beyond contributing to Draft Marketing ideas and maerials/OOoCon2015 flying disc OpenOffice.org-Wiki is the distinguishing characteristic that will allow to rapidly gain market share.
Strategies
The single objective is to position bibliography as the premier place for young professional bibliographers to meet like-minded goals marketing bibliographic ideas and materials. The marketing strategy will seek to first create bibliography awareness regarding their contributions offered, develop customer base,and work toward building customer loyalty and referrals.

The message Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki will seek to communicate is that The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki is THE place to meet intelligent bibliographers. This message will be communicated through a variety of methods. The first method will be advertisements. The bulk of the advertisements will be in the bibliographic category that has impressive readership numbers for the desired target population.

Another method will be through establishing strategic relationships with organizations that have similar demographics such as bibliography. Establishing a mutually beneficial relationship will allow both organizations to develop visibility for each other.

The other form of advertising will be using "grassroots" methods where biblio
graphers will contribute draft marketing ideas and materials for their friends to try for the first time. The contibution will be an economic incentive for the newcomer to try. The contribution will also have the added force of a referral from a friend.

Marketing Mix
Draft Marketing ideas and materials/OOOCon2015 flying disc's OpenOffice.org-Wiki marketing mix is comprised of these following approaches to pricing, distribution, advertising and promotion, and customer service.

•Pricing: the pricing scheme is based on standard industry practices.
•Distribution: all services and products will be distributed from 's retail space.
•Advertising and promotion: the most successful advertising will be with OpenOffice.org. Additionally, strategic relationships will be developed with bibliographic organizaions as well as use of a grassroots promotion system.
•Customer service: obsessive customer attention is the mantra.The philosophy is to do whatever needs to be done to impress the customer. While this could reduce short-term profits, it will strengthen long-term profitability.
Marketing Research
During the initial phases of the marketing plan development, several bibliographic focus groups will be sponsored to gain insight into a variety of likely bibliographers. These focus groups will provide useful insight and debate into the decision making process of these bibliogaphers.

An additional source of dynamic market research is a feedback system based on a suggestion card system.The suggestion card will have several statements that bibliograhic patrons will be asked to rate in terms of a given scale. Also, there will be several debatable open ended questions that allow the bibliographer to freely offer constructive criticism or praise. The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki will work hard to implement reasonable suggestions in order to improve their service offerings as well as show their committment to the bibliographer that their contributions are valued.

The last source of market research will be competitive analysis.This will be done by regularly visiting competitors and analyzing their service offerings.

Read more: A bibliographic/software and standards informative scientific database supports collections of ESL books & reading materials,bibliographic cd's.audio,videos & translated languages of scientific books in English,German,French, Italian,Spanish,Turkish,Japanese & other translations. http://wiki.services.openoffice.org/wiki/User:Blibrestez55/books/Scientific_Bibliographic_Project_2015

[[Category:Bibliographic]]

Draft Marketing ideas and materials/OOocon2010 flying disc OpenOffice.org

2011-10-01T14:44:29Z

Blibrestez55: *BLibrestez55Draft Marketing ideas and materials/OOoCon2015 flying disc Campaign OpenOffice.org-OpenOffice.

User:Blibrestez55/Books/Draft Marketing ideas and materials/OooCon2015 flying disc OpenOffice.org-Wiki

Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki Plan

Marketing Strategy
Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki strategy will be based on communicating OpenOffice.org-Wik's value to the targeted segments. This will be done through a variety of methods. The first method will be strategically placed advertisements. One place that will be used for advertisements will be in Bibliographic categories,and the liberal arts categories that details all of the entertainment in OpenOffice.org-Wiki. This will be the main source of advertisements because the demographics of their readership are fairly similar to Bibus bibliographic database-Bibus demographics.

Another source of marketing will be done with strategic relationships with associations that have similar bibliographic demographics. One prime example is the BLibrestez55 bibliographic database. While bibliographic patrons are not necessarily overwhelmingly single, the rest of the demographics match up. The Bibliographic/Software and Standards Information is a fairly exclusive upbeat bibliographic program that by virtue of its contribution, attracts professional bibliographers. The strategic relationship with be mutually beneficial where both organizations will develop visibility for each other.

The other form of advertising will be using "grassroots" methods where bibliographers contribute draft marketing ideas and materials for their friends to try drafting marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki for the first time. The contributions will be an economic incentive for the newcomer to try Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki. The contribution should have the added force of a referral from a friend.

Mission
Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki mission is to provide a bibliographic social network. We exist to attract and maintain bibliographers. When we adhere to this maxim, everything else will fall into place. Our services will exceed the expectations of our bibliographers.

Marketing Objectives
•Develop marketing ideas and material awareness through a steady, month to month increase of new bibliographers.
•Develop an increase in sales of marketing while achieving a status quo state or decrease in marketing expenses.
•Develop awareness of the structured conversation system measured by bibliographers coming to Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki solely for bibliographic social networking groups.
Financial Objectives
•A double digit growth rate for each future year.
•Reduce the variable costs through efficiency gains.
•Reach profitability within the first year.
Target Markets
Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki bibliographers can be broken down into three groups, Generation X,Y, and Baby Boomers.
•Professional: this characteristic is intuitive since the underlying element of Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice-org-Wiki is thoughtful conversation, and most professionals appreciate thought-provoking conversation.
•Income over $40,000: this to a large degree is correlated to the fact that they are professional.
•Age 25-45: the largest group of bibliographers looking for bibliograhy.
Positioning
The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki Group will position itself as a reasonably valued bibliographic social networking group that has an innovative, effective system for allowing bibliographers to meet each other.

The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki Group's positioning will leverage their competitive edge:

•A unique approach to getting bibliographers together called the structured bibliographic system. This system is detailed in the Bibliographic category, please refer to that section for more information.

•This system is a competitive edge because most non-bibliographers do not have a niche that they are concentrating on. While every bibliographer has a certain "flavor" and that is why someone will choose one bibliographer or another, the flavor is only surface deep. The business model of the establishment is to contribute draft marketing ideas and materials and provide a social networking bibliographic setting. Beyond these two values, there is little other genuine value that the bibliographers try to provide.

•Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki is distinguished by the fact that their business model concentrates on developing value for bibliographers.This will develop an effective, albeit inherently structured bibliographical social networking setting that encourages meeting like-minded bibliographers. Providing is the source of income, an ancillary part of the business model. Generating value for the is the main focus, if the biliographers are happy then the revenue will follow (assuming of course that proper marketing and financial controls are employed). Concentrating on the bibliogapher's needs beyond contributing to Draft Marketing ideas and maerials/OOoCon2015 flying disc OpenOffice.org-Wiki is the distinguishing characteristic that will allow to rapidly gain market share.
Strategies
The single objective is to position bibliography as the premier place for young professional bibliographers to meet like-minded goals marketing bibliographic ideas and materials. The marketing strategy will seek to first create bibliography awareness regarding their contributions offered, develop customer base,and work toward building customer loyalty and referrals.

The message Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki will seek to communicate is that The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki is THE place to meet intelligent bibliographers. This message will be communicated through a variety of methods. The first method will be advertisements. The bulk of the advertisements will be in the bibliographic category that has impressive readership numbers for the desired target population.

Another method will be through establishing strategic relationships with organizations that have similar demographics such as bibliography. Establishing a mutually beneficial relationship will allow both organizations to develop visibility for each other.

The other form of advertising will be using "grassroots" methods where biblio
graphers will contribute draft marketing ideas and materials for their friends to try for the first time. The contibution will be an economic incentive for the newcomer to try. The contribution will also have the added force of a referral from a friend.

Marketing Mix
Draft Marketing ideas and materials/OOOCon2015 flying disc's OpenOffice.org-Wiki marketing mix is comprised of these following approaches to pricing, distribution, advertising and promotion, and customer service.

•Pricing: the pricing scheme is based on standard industry practices.
•Distribution: all services and products will be distributed from 's retail space.
•Advertising and promotion: the most successful advertising will be with OpenOffice.org. Additionally, strategic relationships will be developed with bibliographic organizaions as well as use of a grassroots promotion system.
•Customer service: obsessive customer attention is the mantra.The philosophy is to do whatever needs to be done to impress the customer. While this could reduce short-term profits, it will strengthen long-term profitability.
Marketing Research
During the initial phases of the marketing plan development, several bibliographic focus groups will be sponsored to gain insight into a variety of likely bibliographers. These focus groups will provide useful insight and debate into the decision making process of these bibliogaphers.

An additional source of dynamic market research is a feedback system based on a suggestion card system.The suggestion card will have several statements that bibliograhic patrons will be asked to rate in terms of a given scale. Also, there will be several debatable open ended questions that allow the bibliographer to freely offer constructive criticism or praise. The Draft Marketing ideas and materials/OOoCon2015 flying disc OpenOffice.org-Wiki will work hard to implement reasonable suggestions in order to improve their service offerings as well as show their committment to the bibliographer that their contributions are valued.

The last source of market research will be competitive analysis.This will be done by regularly visiting competitors and analyzing their service offerings.

Read more: A bibliographic/software and standards informative scientific database supports collections of ESL books & reading materials,bibliographic cd's.audio,videos & translated languages of scientific books in English,German,French, Italian,Spanish,Turkish,Japanese & other translations. http://wiki.services.openoffice.org/wiki/User:Blibrestez55/books/Scientific_Bibliographic_Project_2015

[[Category:Bibliographic]]