An early draft of an ISO2146 schema to promote discussion. This is intended as an alternative to that currently published on the draft ISO2146 web site. It is based on experience from the pilot collection and services registry developed under the APSR ORCA project (see http://www.apsr.edu.au/orca/index.htm). The schema structure has been based on the PREMIS approach where the core objects are provided their own schema. This may be useful in a maintenance context, a usability context, in establishing focussed working groups, and even swapping out alternative models should better representations of core entities become available in the future. I have feeling it may be useful in allowing more targetted processing and data exchange but I have no use cases to back this up. Each sub-schema represents one of the object sub-types. While there are commonalities across the different entities, the content model of a property such as Name for example may be better controlled/tailored if they are tied to their object type (e.g. name of an activity has a different model than a person name). In this schema I have moved the common elements to their different entities, this will allow different rules (content models) to be imposed on how they are expressed. While at a theoretical level this is redundant (and theoreticians may shudder!) I expect in practice this will be needed and is likely to make an implementors job a little easier. Change history v0.1 - 7 Dec 2007 * Initial Draft v0.2 - 4 Feb 2008 (ORCA developer meeting) * enumeration values moved to external vocabularies * dateCreated attribute added to all repository objects * type attribute added to description element * collection/service relation model applied to party, activity * profile element removed * type library created and imports added to object schemas * type attribute added to collection element v0.3 - 20 Feb 2008 * Added group attribute to registry objects v0.4 - 29 Feb 2008 (Review feedback during ORCA redevelopment) * Removed dateRangeType and converted to attribute group * Registry object wrapper element and relocation of key element and common attributes * Remove type attribute from common attributes (in support of object wrapper element) * Change relation type element from NMTOKENS to xsd:string to support simpler processing of relations * Electronic address element type attribute now optional * Removed type attribute from relatedObjectType * Removed uri element from relatedObjectType * Add type attribute to complexNameType * Drop uri element from electronicAddressType, add value element in its place * Remove args element from relatedObject * Add description element and type attribute to relation element