Type library for Registry Schema A value taken from a controlled vocabulary indicating the type of identifier. The date element describes a specific date associated with an event in the life cycle of the data collection object. A value taken from a controlled vocabulary indicating the type of date. The format of the date element (from the RIFCS Date Type vocabulary). A value taken from the Temporal Coverage Date Type vocabulary indicating the type of this date. Either a single string (using one <namePart> element) or the name represented in compound form with the content of each namePart being described by the type attribute. A value taken from a controlled vocabulary indicating the type of electronic address. A value taken from a controlled vocabulary indicating the type of name. A value taken from a controlled vocabulary indicating the type of spatial location. A value taken from a controlled vocabulary indicating the type of address part. A value taken from a controlled vocabulary indicating the type of physical address. An electronic address will generally hold an e-mail address or URL pointing to the object being described. However in the case of a service it is possible to describe the service in terms of its base URL using the <value> element and using the <arg> element to describe the service arguments. A separate collection object which supports the service would then provide a URL to its implementation of the service in its <url> element when describing the <relatedObject>. Indicates whether the argument is required (true) or optional (false). A value taken from a controlled vocabulary indicating the type of argument. A value taken from a controlled vocabulary indicating the type of use for the argument. A value taken from a controlled vocabulary indicating the type of electronic address. The location element can hold physical and/or electronic addresses as well as geographical references. Use the <address> element for physical or electronic address and the <spatial> element for geographical references. An electronic address could be a website containing details about the activity or email address whereas physical addresses can be provided for snail mail, billing, enquiries. Physical addresses are split into parts should a more granular division of address be required. This attribute is not currently used The format of the date element. Element holding a key which uniquely identifies a related registry object. A wrapper element containing metadata about the current registry object's relationship to another registry object. A plain text description of the relation. A URI expressing or implementing the relationship. For example if describing a collection's relation to a service, the URL which implements the related service in the collection's context can be represented in this element. A value taken from a controlled vocabulary indicating the type of relation. A value taken from a controlled vocabulary indicating the type of subject. The value of an association which identifies the term. This string may be a URI. A value taken from a controlled vocabulary indicating the type of description. A URI. A URI. A value taken from a controlled vocabulary indicating the type of rights or license. The format of the date element. The format of the date element. A value taken from a controlled vocabulary indicating the type of description. A value taken from a controlled vocabulary indicating the citation style used. THIS ELEMENT IS DEPRECATED AS OF V1.4 (USE 'version' ELEMENT INSTEAD. Either a single string (using one <namePart> element) or the name represented in compound form with the content of each namePart being described by the type attribute. A value taken from a controlled vocabulary indicating the type of namePart. An attribute used to indicate any ordering within *like* contributor types (e.g. in a list of co-authors). Where not specified ordering is left up to the consuming application. It should not be assumed the sequence of contributors will be output in the order they appear within the XML. A value taken from a controlled vocabulary indicating the type of date. A value taken from a controlled vocabulary indicating the type of object being described The date this object’s metadata was last changed. This only refers to the metadata of the registry object itself. For example if a collection has a new item added to it this does not constitute a modification to the object. Where an object's metadata has not changed, this attribute should be set to the object's creation date. The date from which the metadata being described was current. This is only applicable where versions of the same metadata is being provided (e.g. name changes). Should be UTC and of one of the forms described in section 3.2.7 of the W3C's Schema Data Types document (http://www.w3.org/TR/xmlschema-2/). The date the metadata being described was no longer current. This is only applicable where versions of the same metadata is being provided (e.g. name changes). Should be UTC and of one of the forms described in section 3.2.7 of the W3C's Schema Data Types document (http://www.w3.org/TR/xmlschema-2/). A string available for grouping of repository objects, typically by organisation. The date this object was registered in a managed environment. Must be UTC and of one of the forms described in section 3.2.7 of the W3C's Schema Data Types document (http://www.w3.org/TR/xmlschema-2/).