Showing:

Annotations
Attributes
Diagrams
Instances
Properties
Source
Used by
Included schema service.xsd
Namespace http://ands.org.au/standards/rif-cs/registryObjects
Annotations
 
Schema for an ISO2146 collections and services registry Service object.
 
Services really need some work in order to determine how we can represent them best for both human and machine-usable consumption. This really needs some real-world use cases.
 
Many of the ISO2146 Service object properties have been excluded from this schema. Use cases need to be developed to address this. The assumption at the moment is that Function, Product, Service Times, Access Policy, Policy Combining Algorithm, Service Description and Protocol Information if important would be included in a the 'description' element. I'm not sure the registry would carry out a lot of service execution or simply direct the user/automaton to the correct location.
 
Services can be supported at a higher level than a collection. For example in DSpace OAI-PMH is supported at a repository level however individual collections within the repository can be harvested. What needs to be exposed at a collection level? In the example a link to the default DC implementation is provided for a collection, however if a service user wanted to know about the data source and what metadata prefixes are supported it's the repository level response which provides this information.
Properties
attribute form default: unqualified
element form default: qualified
version: 1.3
Element service
Namespace http://ands.org.au/standards/rif-cs/registryObjects
Annotations
 
Wrapper element for descriptive and administrative metadata for a service registry object.
Diagram
Diagram registryTypes_xsd.tmp#id91 service_xsd.tmp#id138 service_xsd.tmp#id139 service_xsd.tmp#id140 service_xsd.tmp#id141 service_xsd.tmp#id142 service_xsd.tmp#id143 service_xsd.tmp#id144 service_xsd.tmp#id145 service_xsd.tmp#id146 service_xsd.tmp#id147 service_xsd.tmp#id148
Properties
content: complex
Used by
Model identifier* | name* | location* | coverage* | relatedObject* | subject* | description* | accessPolicy* | rights* | existenceDates* | relatedInfo*
Children accessPolicy, coverage, description, existenceDates, identifier, location, name, relatedInfo, relatedObject, rights, subject
Instance
 
<service dateModified="" type="">
  <identifier type="">{0,unbounded}</identifier>
  <name dateFrom="" dateTo="" xml:lang="" type="">{0,unbounded}</name>
  <location dateFrom="" dateTo="" type="">{0,unbounded}</location>
  <coverage>{0,unbounded}</coverage>
  <relatedObject>{0,unbounded}</relatedObject>
  <subject xml:lang="" termIdentifier="" type="">{0,unbounded}</subject>
  <description xml:lang="" type="">{0,unbounded}</description>
  <accessPolicy>{0,unbounded}</accessPolicy>
  <rights>{0,unbounded}</rights>
  <existenceDates>{0,unbounded}</existenceDates>
  <relatedInfo type="">{0,unbounded}</relatedInfo>
</service>
Attributes
QName Type Fixed Default Use Annotation
dateModified xsd:dateTime optional 
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.
type xsd:string required 
A value taken from a controlled vocabulary indicating the type of
object being described
Source
 
<xsd:element name="service">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">Wrapper element for descriptive and administrative metadata for a service registry object.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:choice minOccurs="0" maxOccurs="unbounded">
      <xsd:element name="identifier" type="identifierType" minOccurs="0" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">Primary and alternative identifiers for a service. The value of the <key> element may be repeated, or any additional (local or global) identifiers described. Each identifier must be represented in its own identifier element.</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
      <xsd:element name="name" type="nameType" minOccurs="0" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">The name of the party in either a simple or compound form.</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
      <xsd:element name="location" type="locationType" minOccurs="0" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">Location(s) relevant to the service. A location element should contain information about a single location (e.g. service point).</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
      <xsd:element name="coverage" type="coverageType" minOccurs="0" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">Service coverage information.</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
      <xsd:element name="relatedObject" type="relatedObjectType" minOccurs="0" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">Element for holding information about a related registry object.</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
      <xsd:element name="subject" type="subjectType" minOccurs="0" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">A subject category into which the service falls or the service is related. Multiple subjects must be represented via separate subject elements.</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
      <xsd:element name="description" type="descriptionType" minOccurs="0" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">A textual description or URI resolving to a description relevant to the service.</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
      <xsd:element name="accessPolicy" type="xsd:anyURI" minOccurs="0" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">A URI pointing to information describing the access policy of the service.</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
      <xsd:element name="rights" type="rightsType" minOccurs="0" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">Rights(s) relevant to the collection.</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
      <xsd:element name="existenceDates" type="existenceDateType" minOccurs="0" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">Element for holding a start date and end date.</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
      <xsd:element name="relatedInfo" type="relatedInfoType" minOccurs="0" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation xml:lang="en">A URI pointing to information related to the service.</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
    </xsd:choice>
    <xsd:attributeGroup ref="objectAttributes"/>
  </xsd:complexType>
</xsd:element>
Element service / identifier
Namespace http://ands.org.au/standards/rif-cs/registryObjects
Annotations
 
Primary and alternative identifiers for a service. The value of the <key> element may be repeated, or any additional (local or global) identifiers described. Each identifier must be represented in its own identifier element.
Diagram
Diagram registryTypes_xsd.tmp#id15 registryTypes_xsd.tmp#id14
Type identifierType
Properties
content: complex
minOccurs: 0
maxOccurs: unbounded
Attributes
QName Type Fixed Default Use Annotation
type xsd:string required 
A value taken from a controlled vocabulary indicating the
type of identifier.
Source
 
<xsd:element name="identifier" type="identifierType" minOccurs="0" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">Primary and alternative identifiers for a service. The value of the <key> element may be repeated, or any additional (local or global) identifiers described. Each identifier must be represented in its own identifier element.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
Element service / name
Namespace http://ands.org.au/standards/rif-cs/registryObjects
Annotations
 
The name of the party in either a simple or compound form.
Diagram
Diagram registryTypes_xsd.tmp#id20 registryTypes_xsd.tmp#id23 xml_xsd.tmp#id24 registryTypes_xsd.tmp#id18 registryTypes_xsd.tmp#id17
Type nameType
Properties
content: complex
minOccurs: 0
maxOccurs: unbounded
Model namePart+
Children namePart
Instance
 
<name dateFrom="" dateTo="" xml:lang="" type="">
  <namePart type="">{1,unbounded}</namePart>
</name>
Attributes
QName Type Fixed Default Use Annotation
dateFrom xsd:dateTime optional 
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/).
dateTo xsd:dateTime optional 
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/).
type xsd:string optional 
A value taken from a controlled vocabulary indicating the type of
name.
xml:lang restriction of xs:token optional 
<div>
  <h3>lang (as an attribute name)</h3>
  <p>denotes an attribute whose value
       is a language code for the natural language of the content of
       any element; its value is inherited.  This name is reserved
       by virtue of its definition in the XML specification.</p>
</div>
<div>
  <h4>Notes</h4>
  <p>Attempting to install the relevant ISO 2- and 3-letter
      codes as the enumerated possible values is probably never
      going to be a realistic possibility.</p>
  <p>See BCP 47 at
    <a href="http://www.rfc-editor.org/rfc/bcp/bcp47.txt">http://www.rfc-editor.org/rfc/bcp/bcp47.txt</a>and the IANA language subtag registry at
    <a href="http://www.iana.org/assignments/language-subtag-registry">http://www.iana.org/assignments/language-subtag-registry</a>for further information.</p>
  <p>The union allows for the 'un-declaration' of xml:lang with
      the empty string.</p>
</div>
Source
 
<xsd:element name="name" type="nameType" minOccurs="0" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">The name of the party in either a simple or compound form.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
Element service / location
Namespace http://ands.org.au/standards/rif-cs/registryObjects
Annotations
 
Location(s) relevant to the service. A location element should contain information about a single location (e.g. service point).
Diagram
Diagram registryTypes_xsd.tmp#id20 registryTypes_xsd.tmp#id44 registryTypes_xsd.tmp#id27 registryTypes_xsd.tmp#id41 registryTypes_xsd.tmp#id26
Type locationType
Properties
content: complex
minOccurs: 0
maxOccurs: unbounded
Model address* , spatial*
Children address, spatial
Instance
 
<location dateFrom="" dateTo="" type="">
  <address>{0,unbounded}</address>
  <spatial xml:lang="" type="">{0,unbounded}</spatial>
</location>
Attributes
QName Type Fixed Default Use Annotation
dateFrom xsd:dateTime optional 
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/).
dateTo xsd:dateTime optional 
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/).
type xsd:string optional 
This attribute is not currently used
Source
 
<xsd:element name="location" type="locationType" minOccurs="0" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">Location(s) relevant to the service. A location element should contain information about a single location (e.g. service point).</xsd:documentation>
  </xsd:annotation>
</xsd:element>
Element service / coverage
Namespace http://ands.org.au/standards/rif-cs/registryObjects
Annotations
 
Service coverage information.
Diagram
Diagram registryTypes_xsd.tmp#id47 registryTypes_xsd.tmp#id48 registryTypes_xsd.tmp#id46
Type coverageType
Properties
content: complex
minOccurs: 0
maxOccurs: unbounded
Model spatial* | temporal*
Children spatial, temporal
Instance
 
<coverage>
  <spatial xml:lang="" type="">{0,unbounded}</spatial>
  <temporal>{0,unbounded}</temporal>
</coverage>
Source
 
<xsd:element name="coverage" type="coverageType" minOccurs="0" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">Service coverage information.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
Element service / relatedObject
Namespace http://ands.org.au/standards/rif-cs/registryObjects
Annotations
 
Element for holding information about a related registry object.
Diagram
Diagram registryTypes_xsd.tmp#id56 registryTypes_xsd.tmp#id57 registryTypes_xsd.tmp#id55
Type relatedObjectType
Properties
content: complex
minOccurs: 0
maxOccurs: unbounded
Model key , relation+
Children key, relation
Instance
 
<relatedObject>
  <key>{1,1}</key>
  <relation type="">{1,unbounded}</relation>
</relatedObject>
Source
 
<xsd:element name="relatedObject" type="relatedObjectType" minOccurs="0" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">Element for holding information about a related registry object.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
Element service / subject
Namespace http://ands.org.au/standards/rif-cs/registryObjects
Annotations
 
A subject category into which the service falls or the service is related. Multiple subjects must be represented via separate subject elements.
Diagram
Diagram registryTypes_xsd.tmp#id64 registryTypes_xsd.tmp#id65 xml_xsd.tmp#id24 registryTypes_xsd.tmp#id63
Type subjectType
Properties
content: complex
minOccurs: 0
maxOccurs: unbounded
Attributes
QName Type Fixed Default Use Annotation
termIdentifier xsd:string optional 
The value of an association which identifies
the term. This string may be a URI.
type xsd:string required 
A value taken from a controlled vocabulary indicating the
type of subject.
xml:lang restriction of xs:token optional 
<div>
  <h3>lang (as an attribute name)</h3>
  <p>denotes an attribute whose value
       is a language code for the natural language of the content of
       any element; its value is inherited.  This name is reserved
       by virtue of its definition in the XML specification.</p>
</div>
<div>
  <h4>Notes</h4>
  <p>Attempting to install the relevant ISO 2- and 3-letter
      codes as the enumerated possible values is probably never
      going to be a realistic possibility.</p>
  <p>See BCP 47 at
    <a href="http://www.rfc-editor.org/rfc/bcp/bcp47.txt">http://www.rfc-editor.org/rfc/bcp/bcp47.txt</a>and the IANA language subtag registry at
    <a href="http://www.iana.org/assignments/language-subtag-registry">http://www.iana.org/assignments/language-subtag-registry</a>for further information.</p>
  <p>The union allows for the 'un-declaration' of xml:lang with
      the empty string.</p>
</div>
Source
 
<xsd:element name="subject" type="subjectType" minOccurs="0" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">A subject category into which the service falls or the service is related. Multiple subjects must be represented via separate subject elements.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
Element service / description
Namespace http://ands.org.au/standards/rif-cs/registryObjects
Annotations
 
A textual description or URI resolving to a description relevant to the service.
Diagram
Diagram registryTypes_xsd.tmp#id68 xml_xsd.tmp#id24 registryTypes_xsd.tmp#id67
Type descriptionType
Properties
content: complex
minOccurs: 0
maxOccurs: unbounded
Attributes
QName Type Fixed Default Use Annotation
type xsd:string required 
A value taken from a controlled vocabulary indicating the
type of description.
xml:lang restriction of xs:token optional 
<div>
  <h3>lang (as an attribute name)</h3>
  <p>denotes an attribute whose value
       is a language code for the natural language of the content of
       any element; its value is inherited.  This name is reserved
       by virtue of its definition in the XML specification.</p>
</div>
<div>
  <h4>Notes</h4>
  <p>Attempting to install the relevant ISO 2- and 3-letter
      codes as the enumerated possible values is probably never
      going to be a realistic possibility.</p>
  <p>See BCP 47 at
    <a href="http://www.rfc-editor.org/rfc/bcp/bcp47.txt">http://www.rfc-editor.org/rfc/bcp/bcp47.txt</a>and the IANA language subtag registry at
    <a href="http://www.iana.org/assignments/language-subtag-registry">http://www.iana.org/assignments/language-subtag-registry</a>for further information.</p>
  <p>The union allows for the 'un-declaration' of xml:lang with
      the empty string.</p>
</div>
Source
 
<xsd:element name="description" type="descriptionType" minOccurs="0" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">A textual description or URI resolving to a description relevant to the service.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
Element service / accessPolicy
Namespace http://ands.org.au/standards/rif-cs/registryObjects
Annotations
 
A URI pointing to information describing the access policy of the service.
Diagram
Diagram
Type xsd:anyURI
Properties
content: simple
minOccurs: 0
maxOccurs: unbounded
Source
 
<xsd:element name="accessPolicy" type="xsd:anyURI" minOccurs="0" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">A URI pointing to information describing the access policy of the service.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
Element service / rights
Namespace http://ands.org.au/standards/rif-cs/registryObjects
Annotations
 
Rights(s) relevant to the collection.
Diagram
Diagram registryTypes_xsd.tmp#id71 registryTypes_xsd.tmp#id74 registryTypes_xsd.tmp#id78 registryTypes_xsd.tmp#id70
Type rightsType
Properties
content: complex
minOccurs: 0
maxOccurs: unbounded
Model rightsStatement{0,1} | licence{0,1} | accessRights{0,1}
Children accessRights, licence, rightsStatement
Instance
 
<rights>
  <rightsStatement rightsUri="">{0,1}</rightsStatement>
  <licence rightsUri="" type="">{0,1}</licence>
  <accessRights rightsUri="" type="">{0,1}</accessRights>
</rights>
Source
 
<xsd:element name="rights" type="rightsType" minOccurs="0" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">Rights(s) relevant to the collection.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
Element service / existenceDates
Namespace http://ands.org.au/standards/rif-cs/registryObjects
Annotations
 
Element for holding a start date and end date.
Diagram
Diagram registryTypes_xsd.tmp#id81 registryTypes_xsd.tmp#id83 registryTypes_xsd.tmp#id80
Type existenceDateType
Properties
content: complex
minOccurs: 0
maxOccurs: unbounded
Model startDate{0,1} , endDate{0,1}
Children endDate, startDate
Instance
 
<existenceDates>
  <startDate dateFormat="">{0,1}</startDate>
  <endDate dateFormat="">{0,1}</endDate>
</existenceDates>
Source
 
<xsd:element name="existenceDates" type="existenceDateType" minOccurs="0" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">Element for holding a start date and end date.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
Element service / relatedInfo
Namespace http://ands.org.au/standards/rif-cs/registryObjects
Annotations
 
A URI pointing to information related to the service.
Diagram
Diagram registryTypes_xsd.tmp#id90 registryTypes_xsd.tmp#id87 registryTypes_xsd.tmp#id88 registryTypes_xsd.tmp#id89 registryTypes_xsd.tmp#id86
Type relatedInfoType
Properties
content: complex
minOccurs: 0
maxOccurs: unbounded
Model identifier | title{0,1} | notes{0,1}
Children identifier, notes, title
Instance
 
<relatedInfo type="">
  <identifier type="">{1,1}</identifier>
  <title>{0,1}</title>
  <notes>{0,1}</notes>
</relatedInfo>
Attributes
QName Type Fixed Default Use Annotation
type xsd:string optional 
A value taken from a controlled vocabulary indicating the type of
description.
Source
 
<xsd:element name="relatedInfo" type="relatedInfoType" minOccurs="0" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation xml:lang="en">A URI pointing to information related to the service.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
XML Schema documentation generated by ® XML Editor.