Schema documentation for component diggs:DesignConformanceCriterion

An acceptance criterion on a geometric, constructional or compositional property measured against its design intent, such as position, verticality, diameter, length, cut-off elevation, binding material content or a water/binding-material ratio. It is a tolerance: it asks whether what was built matches what was designed, not whether it performs. The parameterName of limit/AuthorizedParameter identifies the design property; its mandatory codeSpace should resolve against designProperty.xml. The schema does not enforce which dictionary is used. Where the requirement is on a measured physical property, use diggs:PerformanceCriterion.

<diggs:DesignConformanceCriterion 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:internalIdentifier codeSpace="">{0,1}</diggs:internalIdentifier>
  <diggs:status codeSpace="">{0,1}</diggs:status>
  <diggs:implementationStatus codeSpace="">{0,1}</diggs:implementationStatus>
  <diggs:associatedFile xlink:href="" nilReason="" owns="false">{0,unbounded}</diggs:associatedFile>
  <diggs:role>{0,unbounded}</diggs:role>
  <diggs:remark>{0,unbounded}</diggs:remark>
  <diggs:basedOnRef xlink:href="" identifierRef="" nilReason="" owns="false">{0,1}</diggs:basedOnRef>
  <diggs:basisRef xlink:href="" identifierRef="" nilReason="" owns="false">{0,1}</diggs:basisRef>
  <diggs:appliesToZone xlink:href="" nilReason="" owns="false">{0,1}</diggs:appliesToZone>
  <diggs:appliesToFeatureType codeSpace="">{0,1}</diggs:appliesToFeatureType>
  <diggs:statistic>{0,1}</diggs:statistic>
  <diggs:percentileValue>{0,1}</diggs:percentileValue>
  <diggs:statisticScope>{0,1}</diggs:statisticScope>
  <diggs:operator>{1,1}</diggs:operator>
  <diggs:limit>{1,1}</diggs:limit>
  <diggs:basis codeSpace="">{0,1}</diggs:basis>
  <diggs:baseLength howDetermined="" qualifier="" uom="">{0,1}</diggs:baseLength>
  <diggs:evidenceCondition>{0,unbounded}</diggs:evidenceCondition>
  <diggs:sourceSpecRef xlink:href="" identifierRef="" nilReason="" owns="false">{0,1}</diggs:sourceSpecRef>
  <diggs:partOfSpecificationRef xlink:href="" identifierRef="" nilReason="" owns="false">{0,1}</diggs:partOfSpecificationRef>
</diggs:DesignConformanceCriterion>

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.

<element name="DesignConformanceCriterion" type="diggs:AbstractAcceptanceCriterionType" substitutionGroup="diggs:AbstractAcceptanceCriterion"> <annotation> <documentation>An acceptance criterion on a geometric, constructional or compositional property measured against its design intent, such as position, verticality, diameter, length, cut-off elevation, binding material content or a water/binding-material ratio. It is a tolerance: it asks whether what was built matches what was designed, not whether it performs. The parameterName of limit/AuthorizedParameter identifies the design property; its mandatory codeSpace should resolve against designProperty.xml. The schema does not enforce which dictionary is used. Where the requirement is on a measured physical property, use diggs:PerformanceCriterion.</documentation> </annotation> </element>

Showing: