Showing:

Annotations
Attributes
Diagrams
Instances
Model
Properties
Source
Used by
Element diggs:SpecificationRegistryEntry
Namespace http://diggsml.org/schemas/3
Annotations
 
One registration in a specification registry: the canonical
                diggs:Specification for a standard - or for a named part, clause or procedure of a
                standard - together with the metadata that governs how it may be cited.

                This object exists so that the registered diggs:Specification can stay exactly what
                it always was. It substitutes nothing and appears nowhere except inside a registry,
                so no consuming application ever meets it where it expected a Specification. A
                reference into a registry resolves to the contained Specification, not to this
                entry.

                CHOOSING gml:id ON THE CONTAINED SPECIFICATION. The Specification's gml:id is the
                citation token - it is what appears after the '#' in every xlink:href - so it should
                track the standard's own identifier as closely as XML permits. gml:id is an XML ID
                and therefore an NCName: it may not begin with a digit and may not contain a space,
                a slash or a colon. So "ASTM D1143" becomes astm_d1143 and "BS 8006-1:2010" becomes
                bs_8006_1_2010. Use lower snake case throughout, and keep the token stable forever
                once published - a registry whose identifiers churn is worse than no registry,
                because existing citations silently break.

                SUBMETHODS. A named procedure within a standard is its own entry, not a variant of
                one: ASTM D1143 Procedure A gets its own SpecificationRegistryEntry whose
                Specification carries its own gml:id (astm_d1143_proc_a), repeats the parent's
                standardReferenceNumber, and is distinguished by standardClause, standardPart or
                shortMethodName. Because those are structured properties rather than free text, a
                consumer can group every Specification sharing a standardReferenceNumber under its
                parent standard mechanically. That grouping is the only reason to prefer registering
                a submethod over inventing an ad hoc code for it.
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#AbstractGMLTypegml3_2Profile_diggs_xsd_Attribute_gml_id.tmp#idAbstractTypes_xsd_Complex_Type_diggs_AbstractDiggsType.tmp#AbstractDiggsTypegml3_2Profile_diggs_xsd_Element_gml_description.tmp#descriptiongml3_2Profile_diggs_xsd_Element_gml_identifier.tmp#identifierAbstractTypes_xsd_Complex_Type_diggs_AbstractObjectBaseType.tmp#AbstractObjectBaseTypegml3_2Profile_diggs_xsd_Element_gml_name.tmp#nameCommon_xsd_Element_diggs_status.tmp#statusAbstractTypes_xsd_Complex_Type_diggs_AbstractObjectType.tmp#AbstractObjectType_remarkAbstractTypes_xsd_Complex_Type_diggs_AbstractObjectType.tmp#AbstractObjectTypeSpecificationRegistry_xsd_Complex_Type_diggs_SpecificationRegistryEntryType.tmp#SpecificationRegistryEntryType_specificationSpecificationRegistry_xsd_Complex_Type_diggs_SpecificationRegistryEntryType.tmp#SpecificationRegistryEntryType_domainSpecificationRegistry_xsd_Complex_Type_diggs_SpecificationRegistryEntryType.tmp#SpecificationRegistryEntryType_authoritySpecificationRegistry_xsd_Complex_Type_diggs_SpecificationRegistryEntryType.tmp#SpecificationRegistryEntryType_referenceSpecificationRegistry_xsd_Complex_Type_diggs_SpecificationRegistryEntryType.tmp#SpecificationRegistryEntryType_registryStatusSpecificationRegistry_xsd_Complex_Type_diggs_SpecificationRegistryEntryType.tmp#SpecificationRegistryEntryType_supersededByRefSpecificationRegistry_xsd_Complex_Type_diggs_SpecificationRegistryEntryType.tmp#SpecificationRegistryEntryType_occurrencesSpecificationRegistry_xsd_Complex_Type_diggs_SpecificationRegistryEntryType.tmp#SpecificationRegistryEntryType
Type diggs:SpecificationRegistryEntryType
Type hierarchy
Properties
content complex
Used by
Model
Children diggs:authority, diggs:domain, diggs:occurrences, diggs:reference, diggs:registryStatus, diggs:remark, diggs:specification, diggs:status, diggs:supersededByRef, gml:description, gml:identifier, gml:name
Instance
 
<diggs:SpecificationRegistryEntry 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:identifier codeSpace="">{0,1}</gml:identifier>
  <gml:name codeSpace="">{0,unbounded}</gml:name>
  <diggs:status codeSpace="">{0,1}</diggs:status>
  <diggs:remark>{0,unbounded}</diggs:remark>
  <diggs:specification owns="false">{1,1}</diggs:specification>
  <diggs:domain codeSpace="">{1,unbounded}</diggs:domain>
  <diggs:authority>{0,1}</diggs:authority>
  <diggs:reference>{0,1}</diggs:reference>
  <diggs:registryStatus>{0,1}</diggs:registryStatus>
  <diggs:supersededByRef xlink:href="" identifierRef="" nilReason="" owns="false">{0,1}</diggs:supersededByRef>
  <diggs:occurrences>{0,1}</diggs:occurrences>
</diggs:SpecificationRegistryEntry>
Attributes
QName Type Use Annotation
gml:id ID required 
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="SpecificationRegistryEntry" type="diggs:SpecificationRegistryEntryType">
  <annotation>
    <documentation>One registration in a specification registry: the canonical diggs:Specification for a standard - or for a named part, clause or procedure of a standard - together with the metadata that governs how it may be cited. This object exists so that the registered diggs:Specification can stay exactly what it always was. It substitutes nothing and appears nowhere except inside a registry, so no consuming application ever meets it where it expected a Specification. A reference into a registry resolves to the contained Specification, not to this entry. CHOOSING gml:id ON THE CONTAINED SPECIFICATION. The Specification's gml:id is the citation token - it is what appears after the '#' in every xlink:href - so it should track the standard's own identifier as closely as XML permits. gml:id is an XML ID and therefore an NCName: it may not begin with a digit and may not contain a space, a slash or a colon. So "ASTM D1143" becomes astm_d1143 and "BS 8006-1:2010" becomes bs_8006_1_2010. Use lower snake case throughout, and keep the token stable forever once published - a registry whose identifiers churn is worse than no registry, because existing citations silently break. SUBMETHODS. A named procedure within a standard is its own entry, not a variant of one: ASTM D1143 Procedure A gets its own SpecificationRegistryEntry whose Specification carries its own gml:id (astm_d1143_proc_a), repeats the parent's standardReferenceNumber, and is distinguished by standardClause, standardPart or shortMethodName. Because those are structured properties rather than free text, a consumer can group every Specification sharing a standardReferenceNumber under its parent standard mechanically. That grouping is the only reason to prefer registering a submethod over inventing an ad hoc code for it.</documentation>
  </annotation>
</element>
XML Schema documentation generated by ® XML Editor.