A Ownership Electronic Documentation Structures

B Intellectual Property Royalties

C Copyright

D Part of larger coding structure

E Objectives of coding structure

a	There are four aspects of Intellectual Property for documentation

	1	creating the document.  

		If a document has been created by an Author then that author is entitled
		to Royalties for creating a unique document.

		If a document is created by somebody to record a process and that Author
		has not been paid by a Client or a Sponsor then that Author is entitled
		to Royalties.

		If a document has been created by somebody who has been paid an agreed
		sum to create that document by a Client or Sponsor then that document
		is owned by the Client or Sponsor who are then entitled to Royalties.  
 
		If a document has been paid for by a Government Department and Published 
		as a tender it is classified as in the Public Domain as it has been paid for
		by rate and tax-payers.

	2	rendering the document accessible electronically

		One of the major advantages of the Internet is the ability to reference
		information and documents electronically so that is easily accessible
		to a number of potential interested parties.

		The act of rendering the document accessible electronically using htm
		rather than as an electronic version of a hard-copy document requires time
		and expertise to render that document accessible

	3	developing the Expertise

		The expertise has been provided by the Research into the RUBAC Electronic
		Information Management Code over the 5 years to assist a number of organisation
		to work together to submit worthy responses to complex Government tenders 

	4	purpose of Electronic Association Information Management Codes [EAIM]

		the purpose of developing EAIM is to provide a Good Governance process for
		Associations and their members for access to electronic information over a 
		number of integrated modules including

		Electronic Committee Information Management [ECIM]

		Electronic Event Information Management [EEIM]

		Electronic Member Information Management [EMIM]

b	EAIM was prototyped as a live application for the Open Interchange Consortium
	(OIC).  

c	The initial funding was provided by Tom KOLTAI Ourworld Global Network, Stephan SMYDZUK 
	Commonwealth Bank, David KOHN AIDC and James WILSON Optus

d	The EAIM Electronic Information processes utilises the RUBAC [Rational Universal 
	Business Automation Code] Electronic Information Interchange [EII] methodology.

e	The RUBAC Information Management Coding methodology is owned by the Hamme Family Trust.

f	The RUBAC Codes are used to enable the Document Structure and linkages to be used
	on the Internet.

g	The Web Research and Development IPR Organisation beneficiaries are:

	The coding structure was researched and developed by 6 members of the OIC:

	1	Hamme Family Trust		HFT
	2	GMB & Associates		GMB
	3	Aiyom Pty Ltd			APL
4	Collins Information Services	CIS
	5	Halisa NSW Partnership		HNP

h	The Research and Development IPR Individual beneficiaries are:

	1	Hamme Family Trust		HFT
	2	Guy BLOMBERG			GMB
	3	Stevan GILLMORE			APL
	4	Patricia COLLINS		PAC
	5	Stephen GOULD			HNP

a	There is an established eCredits remuneration structure for Intellectual Property
	Royalties agreed by members of the Open Interchange Consortium

b	This eCredits Remuneration Structure was proposed, developed and implemented by
	members	of the OIC XLM & E-commerce Special Interest Group [XZIG]

c	This eCredits remuneration Structure is based on 8 eCredits

	1	Accommodation
	2	Entertainment
	3	Financial
	4	Health
	5	Learning
	6	Nourishment
	7	Travel
	8	Other

d	One eCredit is awarded every time a web-page of EAIM is accessed

e	The eDebit is allocated against the Wed-page Sponsors and as a percentage
	fee if any products/services are ordered electronically.

a	The copyright for the codes is owned by the organisation and the parties who
	researched and develop the code for a specific application, function or process.

b	Other organisations wishing to use the foundation codes to develop coding structures 
	for similar/other applications and information management processes must e-mail: 
	RUBACcodes@halisa-eu.net to check to see if those applications have not been developed.

c	If this Research is found to have been used in manual and electronic processes 
	without confirmation, legal action may be taken 

a	The coding structure used to provide Electronic Association Information Management 
	[EAIM] is part of the RUBAC [Rational Universal Business Automation Code] 
	Electronic Information Interchange [EII] Methodology.

b	Further details on the RUBAC methodology and its value for E-commerce can be reviewed on
	RUBAC & Electronic Information Management.

a	The RUBAC methodology was researched to achieve a number of objectives including 

	1	the automation of management metrics

	2	synchronisation of distributed information repositories

	3	automatically index and file electronic information

	4	minimise transmission time and cost

	5	provide a standard structure for information retrieval