Diagram
| Target Namespace | http://ands.org.au/standards/rif-cs/registryObjects |
|---|---|
| Version | 1.0.1 |
| Element and Attribute Namespaces |
|
| Schema Composition |
|
| Documentation | Type library for Registry Schema |
| Prefix | Namespace |
|---|---|
| Default namespace | http://ands.org.au/standards/rif-cs/registryObjects |
| xml | http://www.w3.org/XML/1998/namespace |
| xsd | http://www.w3.org/2001/XMLSchema |
| Name | collectionAttributes |
|---|
'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/).'
"
| Name | dateRangeAttributes |
|---|---|
| Used by (from the same schema document) | Complex Type nameType , Complex Type locationType |
'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/).'
"
| Name | objectAttributes |
|---|
'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.'
"
| Name | registryObjectAttributes |
|---|
'A string available for grouping of repository objects, typically by organisation.'
"
| Super-types: | xsd:string < descriptionType (by extension) |
|---|---|
| Sub-types: | None |
| Name | descriptionType |
|---|---|
| Abstract | no |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | electronicAddressType |
|---|---|
| Used by (from the same schema document) | Complex Type locationType |
| Abstract | no |
| Documentation | 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>. |
'A value taken from a controlled vocabulary indicating the type of electronic address.'
">'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.'
"> [0..*]
| Super-types: | xsd:string < identifierType (by extension) |
|---|---|
| Sub-types: | None |
| Name | identifierType |
|---|---|
| Abstract | no |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | locationType |
|---|---|
| Abstract | no |
| Documentation | 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. |
'A value taken from a controlled vocabulary indicating the type of location being described.'
"'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/).'
">
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | nameType |
|---|---|
| Abstract | no |
'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 value taken from a controlled vocabulary indicating the type of name.'
"'A value taken from a controlled vocabulary indicating the type of electronic address.'
"> [1..*]'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.'
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | physicalAddressType |
|---|---|
| Used by (from the same schema document) | Complex Type locationType |
| Abstract | no |
| Super-types: | None |
|---|---|
| Sub-types: | None |
| Name | relatedObjectType |
|---|---|
| Abstract | no |
'Element holding a key which uniquely identifies a related registry object.'
'A value taken from a controlled vocabulary indicating the type of relation.'
"> [1..*]'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.'
| Super-types: | xsd:string < spatialType (by extension) |
|---|---|
| Sub-types: | None |
| Name | spatialType |
|---|---|
| Used by (from the same schema document) | Complex Type locationType |
| Abstract | no |
| Super-types: | xsd:string < subjectType (by extension) |
|---|---|
| Sub-types: | None |
| Name | subjectType |
|---|---|
| Abstract | no |
| Super-types: | Address < AusAddress (by extension) |
|---|---|
| Sub-types: |
|
| Name | AusAddress |
|---|---|
| Abstract | no |
The XML Instance Representation table above shows the schema component's content as an XML instance.
Abstract (Applies to complex type definitions and element declarations). An abstract element or complex type cannot used to validate an element instance. If there is a reference to an abstract element, only element declarations that can substitute the abstract element can be used to validate the instance. For references to abstract type definitions, only derived types can be used.
All Model Group Child elements can be provided in any order in instances. See: http://www.w3.org/TR/xmlschema-1/#element-all.
Choice Model Group Only one from the list of child elements and model groups can be provided in instances. See: http://www.w3.org/TR/xmlschema-1/#element-choice.
Collapse Whitespace Policy Replace tab, line feed, and carriage return characters with space character (Unicode character 32). Then, collapse contiguous sequences of space characters into single space character, and remove leading and trailing space characters.
Disallowed Substitutions
(Applies to element declarations). If substitution is specified, then substitution group members cannot be used in place of the given element declaration to validate element instances. If derivation methods, e.g. extension, restriction, are specified, then the given element declaration will not validate element instances that have types derived from the element declaration's type using the specified derivation methods. Normally, element instances can override their declaration's type by specifying an xsi:type attribute.
Key Constraint Like Uniqueness Constraint, but additionally requires that the specified value(s) must be provided. See: http://www.w3.org/TR/xmlschema-1/#cIdentity-constraint_Definitions.
Key Reference Constraint Ensures that the specified value(s) must match value(s) from a Key Constraint or Uniqueness Constraint. See: http://www.w3.org/TR/xmlschema-1/#cIdentity-constraint_Definitions.
Model Group Groups together element content, specifying the order in which the element content can occur and the number of times the group of element content may be repeated. See: http://www.w3.org/TR/xmlschema-1/#Model_Groups.
Nillable
(Applies to element declarations). If an element declaration is nillable, instances can use the xsi:nil attribute. The xsi:nil attribute is the boolean attribute, nil, from the http://www.w3.org/2001/XMLSchema-instance namespace. If an element instance has an xsi:nil attribute set to true, it can be left empty, even though its element declaration may have required content.
Notation A notation is used to identify the format of a piece of data. Values of elements and attributes that are of type, NOTATION, must come from the names of declared notations. See: http://www.w3.org/TR/xmlschema-1/#cNotation_Declarations.
Preserve Whitespace Policy Preserve whitespaces exactly as they appear in instances.
Prohibited Derivations (Applies to type definitions). Derivation methods that cannot be used to create sub-types from a given type definition.
Prohibited Substitutions (Applies to complex type definitions). Prevents sub-types that have been derived using the specified derivation methods from validating element instances in place of the given type definition.
Replace Whitespace Policy Replace tab, line feed, and carriage return characters with space character (Unicode character 32).
Sequence Model Group Child elements and model groups must be provided in the specified order in instances. See: http://www.w3.org/TR/xmlschema-1/#element-sequence.
Substitution Group Elements that are members of a substitution group can be used wherever the head element of the substitution group is referenced.
Substitution Group Exclusions (Applies to element declarations). Prohibits element declarations from nominating themselves as being able to substitute a given element declaration, if they have types that are derived from the original element's type using the specified derivation methods.
Target Namespace The target namespace identifies the namespace that components in this schema belongs to. If no target namespace is provided, then the schema components do not belong to any namespace.
Uniqueness Constraint Ensures uniqueness of an element/attribute value, or a combination of values, within a specified scope. See: http://www.w3.org/TR/xmlschema-1/#cIdentity-constraint_Definitions.