XML Schema defining XML ContextObject Format. Validated with XML Spy v.5.3 on September 27th 2003. This XML Schema is available at http://www.openurl.info/registry/docs/info:ofi/fmt:xml:xsd:ctx XML ContextObject Format NISO Committee AX, OpenURL Standard Committee Herbert Van de Sompel This XML Schema defines a format to express one or more ContextObjects as an XML document. http://www.openurl.info/registry/docs/info:ofi/fmt:xml:xsd:ctx info:ofi/fmt:xml:xsd:ctx 2004-01-01 The 'context-objects' element is a wrapper holding one or more autonomous XML ContextObjects. The 'context-objects' element is a wrapper holding one or more autonomous ContextObjects. The 'context-objects' element has an optional administrative child element to hold Community-specific administrative data. The name of that element is 'administration'. The ContextObject is an information construct to represent an Entity that is referenced in a networked environment (the Referent) along with Entities that constitute the context in which the Referent is referenced. In the ContextObject, the Entities that describe the context are: the ReferringEntity, the Requester, the Resolver, the ServiceType, the Referrer. The ContextObject is represented by the 'context-object' element in this XML ContextObject Format The ContextObject represented using the XML ContextObject Format contains descriptions of the following Entities: (1) exactly one Referent, (2) zero or one ReferringEntity, (3) zero or one Requester, (4) zero or more ServiceTypes, (5) zero or more Resolvers, and (6) zero or one Referrer. In the XML ContextObject Format, these Entities are represented by the elements 'referent', 'referring-entity', 'requester', 'service-type', 'resolver', and 'referrer', respectively. Each ContextObject has the following optional administrative attributes: (1) 'version' attribute - version of the ContextObject - fixed value Z39.88-2004 (optional), (2) 'identifier' attribute - identifier of the ContextObject (optional), and (3) 'timestamp' attribute - date/time of creation of the ContextObject (optional). The 'context-object' element has an optional administrative child element to hold Community-specific administrative data. The name of that element is 'administration'. In the XML ContextObject Format, each Entity of the ContextObject can be described by means of the following Descriptors: (1) zero or more Identifier Descriptors, (2) zero or more By-Value Metadata Descriptors, (3) zero or more By-Reference Metadata Descriptors, and (4) zero or more Private Data Descriptors. In the XML ContextObject Format, these Descriptors are contained in the elements 'identifier', 'metadata-by-val', 'metadata-by-ref', and 'private-data', respectively. Identifiers in the OpenURL Framework are URIs By-Value Metadata is provided through an XML description embedded in the ContextObject. The By-Value Metadata is provided as the combination of (1) a 'format' element, which identifies the Metadata Format of the By-Value Metadata, and (2) a 'metadata' element in which the metadata corresponding to the identified Metadata Format is contained. By-Reference Metadata is provided by means of the network-location of a document that contains the metadata. By-Reference Metadata is provided as the combination of (1) a 'format' element, which identifies the Metadata Format of the By-Reference Metadata, and (2) a 'location' element that specifies the network-location of the By-Reference Metadata Private Data is provided through an XML description that declares its XML Namespace URI and schemaLocation. Metadata Formats in the OpenURL Framework are identified by means of URIs. Registered Metadata Formats have a URI in the info:ofi/fmt: namespace, whereas Unregistered Metadata Formats have a URI in another URI namespace. Both URIs are dereferencable to a document defining the Metadata Format The content of the network-location element is a URL specifying the network location of the By-Reference Metadata Description Administrative information can be attached to the 'context-objects' and/or the 'context-object' element. Its content can be defined by communities of implementers. Valid values follow the ISO 8601 YYYY-MM-DD or YYYY-MM-DDTHH:MM:SSZ notation.