Showing:

Annotations
Attributes
Diagrams
Instances
Model
Properties
Source
Element diggs:SpecificationRegistry
Namespace http://diggsml.org/schemas/3
Annotations
 
The root element of a specification registry document. Holds the
                registry's own identity - gml:identifier carrying the registry's canonical URL,
                gml:name, gml:description - inherited from gml:AbstractGMLType, followed by its
                entries.

                A registry document is validated against Diggs.xsd like any other DIGGS document;
                this element is its root, in the same way gml:Dictionary is the root of a code list
                document. It is NOT reachable from diggs:Diggs and must never be embedded in a
                project instance: a registry is published by an authority, and a project cites it.

                ONE UNIFIED REGISTRY IS THE INTENDED SHAPE, NOT ONE PER DOMAIN - see this schema's
                own top-level SCOPE note for why a per-domain split was tried and withdrawn. Say what
                the registry as a whole covers in gml:description; say what one ENTRY covers with its
                own diggs:domain classification (one or more codes) plus its diggs:occurrences
                declarations, which are what actually enforce where a given standard may be
                cited.

                ORDER ENTRIES SO THAT A REFERENCE FOLLOWS ITS ANTECEDENT. Where one entry's
                supersededByRef points at another, the superseding entry must appear first, as
                DIGGS forbids forward references throughout.
Diagram
Diagramgml3_2Profile_diggs_xsd_Attribute_gml_id.tmp#idgml3_2Profile_diggs_xsd_Element_gml_description.tmp#descriptiongml3_2Profile_diggs_xsd_Element_gml_descriptionReference.tmp#descriptionReferencegml3_2Profile_diggs_xsd_Element_gml_identifier.tmp#identifiergml3_2Profile_diggs_xsd_Element_gml_name.tmp#namegml3_2Profile_diggs_xsd_Element_Group_gml_StandardObjectProperties.tmp#StandardObjectPropertiesgml3_2Profile_diggs_xsd_Complex_Type_gml_AbstractGMLType.tmp#AbstractGMLTypeSpecificationRegistry_xsd_Complex_Type_diggs_SpecificationRegistryType.tmp#SpecificationRegistryType_registryEntrySpecificationRegistry_xsd_Complex_Type_diggs_SpecificationRegistryType.tmp#SpecificationRegistryType
Type diggs:SpecificationRegistryType
Type hierarchy
Properties
content complex
Model
Children diggs:registryEntry, gml:description, gml:descriptionReference, gml:identifier, gml:name
Instance
 
<diggs:SpecificationRegistry gml:id="" xmlns:diggs="http://diggsml.org/schemas/3" xmlns:gml="http://www.opengis.net/gml/3.2">
  <gml:description xlink:href="" nilReason="">{0,1}</gml:description>
  <gml:descriptionReference xlink:href="" nilReason="" owns="false">{0,1}</gml:descriptionReference>
  <gml:identifier codeSpace="">{0,1}</gml:identifier>
  <gml:name codeSpace="">{0,unbounded}</gml:name>
  <diggs:registryEntry owns="false">{0,unbounded}</diggs:registryEntry>
</diggs:SpecificationRegistry>
Attributes
QName Type Use Annotation
gml:id ID optional 
Database handle for the object. It is of XML type ID, so is constrained to be
unique in the XML document within which it occurs. An external identifier for the object in
the form of a URI may be constructed using standard XML and XPointer methods. This is done
by concatenating the URI for the document, a fragment separator, and the value of the id
attribute.
Source
 
<element name="SpecificationRegistry" type="diggs:SpecificationRegistryType">
  <annotation>
    <documentation>The root element of a specification registry document. Holds the registry's own identity - gml:identifier carrying the registry's canonical URL, gml:name, gml:description - inherited from gml:AbstractGMLType, followed by its entries. A registry document is validated against Diggs.xsd like any other DIGGS document; this element is its root, in the same way gml:Dictionary is the root of a code list document. It is NOT reachable from diggs:Diggs and must never be embedded in a project instance: a registry is published by an authority, and a project cites it. ONE UNIFIED REGISTRY IS THE INTENDED SHAPE, NOT ONE PER DOMAIN - see this schema's own top-level SCOPE note for why a per-domain split was tried and withdrawn. Say what the registry as a whole covers in gml:description; say what one ENTRY covers with its own diggs:domain classification (one or more codes) plus its diggs:occurrences declarations, which are what actually enforce where a given standard may be cited. ORDER ENTRIES SO THAT A REFERENCE FOLLOWS ITS ANTECEDENT. Where one entry's supersededByRef points at another, the superseding entry must appear first, as DIGGS forbids forward references throughout.</documentation>
  </annotation>
</element>
XML Schema documentation generated by ® XML Editor.