Showing:

Annotations
Attributes
Diagrams
Instances
Model
Properties
Source
Used by
Element diggs:AbstractProgramSpecificationType / diggs:appliesToZone
Namespace http://diggsml.org/schemas/3
Annotations
 
The region this specification applies to, as a plan-view polygon or,
where the region is discontinuous, several polygons. A check, not a
membership test: it does not establish which features the
specification governs, which is asserted only from the realized side
through programSpecificationRef, or from a design that adopts the
specification. Where stated, every feature so established is
expected to have its referencePoint within the region (a node on the
boundary counts as inside); one that does not is a finding, not a
reason to exclude it. Where absent, no spatial check applies.
Independent of the scope of any citing design: a specification
shared across designs, or cited directly by a feature, has no single
design scope to inherit the check from.
Diagram
Diagramgml3_2Profile_diggs_xsd_Attribute_Group_gml_OwnershipAttributeGroup.tmp#OwnershipAttributeGroupgml3_2Profile_diggs_xsd_Attribute_Group_gml_AssociationAttributeGroup.tmp#AssociationAttributeGroupCore_xsd_Element_diggs_PlanarSurface.tmp#PlanarSurfaceCore_xsd_Element_diggs_MultiSurface.tmp#MultiSurfaceCore_xsd_Complex_Type_diggs_PlanarSurfaceOrMultiSurfacePropertyType.tmp#PlanarSurfaceOrMultiSurfacePropertyType
Type diggs:PlanarSurfaceOrMultiSurfacePropertyType
Properties
content complex
minOccurs 0
Model
Children diggs:MultiSurface, diggs:PlanarSurface
Instance
 
<diggs:appliesToZone xlink:href="" nilReason="" owns="false" xmlns:diggs="http://diggsml.org/schemas/3">
  <diggs:PlanarSurface axisLabels="" gml:id="" srsDimension="" srsName="" uomLabels="">{1,1}</diggs:PlanarSurface>
  <diggs:MultiSurface aggregationType="" axisLabels="" gml:id="" srsDimension="" srsName="" uomLabels="">{1,1}</diggs:MultiSurface>
</diggs:appliesToZone>
Attributes
QName Type Default Use
nilReason gml:NilReasonType optional
owns boolean false optional
xlink:href anyURI optional
Source
 
<element minOccurs="0" name="appliesToZone" type="diggs:PlanarSurfaceOrMultiSurfacePropertyType">
  <annotation>
    <documentation>The region this specification applies to, as a plan-view polygon or, where the region is discontinuous, several polygons. A check, not a membership test: it does not establish which features the specification governs, which is asserted only from the realized side through programSpecificationRef, or from a design that adopts the specification. Where stated, every feature so established is expected to have its referencePoint within the region (a node on the boundary counts as inside); one that does not is a finding, not a reason to exclude it. Where absent, no spatial check applies. Independent of the scope of any citing design: a specification shared across designs, or cited directly by a feature, has no single design scope to inherit the check from.</documentation>
  </annotation>
</element>
Element diggs:AbstractProgramSpecificationType / diggs:appliesToFeatureType
Namespace http://diggsml.org/schemas/3
Annotations
 
The kind of feature this specification applies to, for example
"ri_column" or "load_transfer_platform". The same kind of check as
appliesToZone: every feature established as a member through
programSpecificationRef or an adopting design is expected to be of
this type; one that is not is a finding. Where absent, no type check
applies. The codeSpace is required. For a specification whose
subject is a construction activity, the kind of feature the activity
builds or acts on. Use the DIGGS dictionary samplingFeatureTypes.xml
for the list of values.
Diagram
Diagramgml3_2Profile_diggs_xsd_Complex_Type_gml_CodeType.tmp#CodeType_codeSpacegml3_2Profile_diggs_xsd_Complex_Type_gml_CodeType.tmp#CodeTypegml3_2Profile_diggs_xsd_Complex_Type_gml_CodeWithAuthorityType.tmp#CodeWithAuthorityType_codeSpacegml3_2Profile_diggs_xsd_Complex_Type_gml_CodeWithAuthorityType.tmp#CodeWithAuthorityType
Type gml:CodeWithAuthorityType
Type hierarchy
Properties
content complex
minOccurs 0
Attributes
QName Type Use
codeSpace anyURI required
Source
 
<element minOccurs="0" name="appliesToFeatureType" type="gml:CodeWithAuthorityType">
  <annotation>
    <documentation>The kind of feature this specification applies to, for example "ri_column" or "load_transfer_platform". The same kind of check as appliesToZone: every feature established as a member through programSpecificationRef or an adopting design is expected to be of this type; one that is not is a finding. Where absent, no type check applies. The codeSpace is required. For a specification whose subject is a construction activity, the kind of feature the activity builds or acts on. Use the DIGGS dictionary samplingFeatureTypes.xml for the list of values.</documentation>
  </annotation>
</element>
Complex Type diggs:AbstractProgramSpecificationType
Namespace http://diggsml.org/schemas/3
Annotations
 
Abstract base type for detailed program specifications that define technical
requirements and acceptance criteria: references to specific standards (for example
ASTM or AASHTO), numerical acceptance criteria, testing methods and frequencies, and
quality control requirements. Unlike designs, specifications are typically
contractual and establish enforceable requirements. basedOnRef cites a more general
specification of the same kind that this one specializes; an acceptance criterion
cites the specification it elaborates through diggs:partOfSpecificationRef instead,
which is a component relationship rather than specialization. basisRef cites the
basis the requirements were derived from.
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_Complex_Type_gml_AbstractFeatureType.tmp#AbstractFeatureTypegml3_2Profile_diggs_xsd_Attribute_gml_id.tmp#idgml3_2Profile_diggs_xsd_Element_gml_description.tmp#descriptiongml3_2Profile_diggs_xsd_Element_gml_identifier.tmp#identifierAbstractTypes_xsd_Complex_Type_diggs_AbstractFeatureBaseType.tmp#AbstractFeatureBaseTypegml3_2Profile_diggs_xsd_Element_gml_name.tmp#nameCommon_xsd_Element_diggs_internalIdentifier.tmp#internalIdentifierCommon_xsd_Element_diggs_status.tmp#statusCommon_xsd_Element_diggs_implementationStatus.tmp#implementationStatusAbstractTypes_xsd_Complex_Type_diggs_AbstractFeatureType.tmp#http___diggsml.org_schemas_3_AbstractFeatureType_associatedFileAbstractTypes_xsd_Complex_Type_diggs_AbstractFeatureType.tmp#http___diggsml.org_schemas_3_AbstractFeatureType_roleAbstractTypes_xsd_Complex_Type_diggs_AbstractFeatureType.tmp#http___diggsml.org_schemas_3_AbstractFeatureType_remarkAbstractTypes_xsd_Complex_Type_diggs_AbstractFeatureType.tmp#http___diggsml.org_schemas_3_AbstractFeatureTypeAbstractTypes_xsd_Complex_Type_diggs_AbstractProgramModuleType.tmp#AbstractProgramModuleTypeCommon_xsd_Element_diggs_basedOnRef.tmp#basedOnRefCommon_xsd_Element_diggs_basisRef.tmp#basisRefAbstractTypes_xsd_Complex_Type_diggs_AbstractProgramSpecificationType.tmp#AbstractProgramSpecificationType_appliesToZoneAbstractTypes_xsd_Complex_Type_diggs_AbstractProgramSpecificationType.tmp#AbstractProgramSpecificationType_appliesToFeatureType
Type extension of diggs:AbstractProgramModuleType
Type hierarchy
Properties
abstract true
Used by
Model
Children diggs:appliesToFeatureType, diggs:appliesToZone, diggs:associatedFile, diggs:basedOnRef, diggs:basisRef, diggs:implementationStatus, diggs:internalIdentifier, diggs:remark, diggs:role, diggs:status, gml:description, gml:identifier, gml:name
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
 
<complexType abstract="true" name="AbstractProgramSpecificationType">
  <annotation>
    <documentation>Abstract base type for detailed program specifications that define technical requirements and acceptance criteria: references to specific standards (for example ASTM or AASHTO), numerical acceptance criteria, testing methods and frequencies, and quality control requirements. Unlike designs, specifications are typically contractual and establish enforceable requirements. basedOnRef cites a more general specification of the same kind that this one specializes; an acceptance criterion cites the specification it elaborates through diggs:partOfSpecificationRef instead, which is a component relationship rather than specialization. basisRef cites the basis the requirements were derived from.</documentation>
  </annotation>
  <complexContent>
    <extension base="diggs:AbstractProgramModuleType">
      <sequence>
        <element minOccurs="0" ref="diggs:basedOnRef"/>
        <element minOccurs="0" maxOccurs="1" ref="diggs:basisRef">
          <annotation>
            <documentation>The basis this specification's requirements were derived from: one, the most specific that applies. More general bases are reached through that basis's own basedOnRef chain.</documentation>
          </annotation>
        </element>
        <element minOccurs="0" name="appliesToZone" type="diggs:PlanarSurfaceOrMultiSurfacePropertyType">
          <annotation>
            <documentation>The region this specification applies to, as a plan-view polygon or, where the region is discontinuous, several polygons. A check, not a membership test: it does not establish which features the specification governs, which is asserted only from the realized side through programSpecificationRef, or from a design that adopts the specification. Where stated, every feature so established is expected to have its referencePoint within the region (a node on the boundary counts as inside); one that does not is a finding, not a reason to exclude it. Where absent, no spatial check applies. Independent of the scope of any citing design: a specification shared across designs, or cited directly by a feature, has no single design scope to inherit the check from.</documentation>
          </annotation>
        </element>
        <element minOccurs="0" name="appliesToFeatureType" type="gml:CodeWithAuthorityType">
          <annotation>
            <documentation>The kind of feature this specification applies to, for example "ri_column" or "load_transfer_platform". The same kind of check as appliesToZone: every feature established as a member through programSpecificationRef or an adopting design is expected to be of this type; one that is not is a finding. Where absent, no type check applies. The codeSpace is required. For a specification whose subject is a construction activity, the kind of feature the activity builds or acts on. Use the DIGGS dictionary samplingFeatureTypes.xml for the list of values.</documentation>
          </annotation>
        </element>
      </sequence>
    </extension>
  </complexContent>
</complexType>
XML Schema documentation generated by ® XML Editor.