Schema documentation for component diggs:RIColumnSpecification

The specification the rigid inclusion columns must satisfy: the constraints the work is judged against, as distinct from the design prepared to satisfy them. It is deliberately thin. Most of what a column specification says is limits (position tolerance, verticality tolerance, minimum embedment into the bearing stratum, permitted diameter and length ranges), and each is a diggs:DesignConformanceCriterion or diggs:PerformanceCriterion declared as a sibling under the specification slot of the program, with an operator, a limit with min, value and max and units, a statistic, and a basis that can express "two times the diameter" as readily as an absolute length. What remains here is the non-limit content: what technique is permitted and what material specification governs. It is also a single stable reference target: a diggs:RIColumn and a design cite it through programSpecificationRef, and each criterion cites it through basedOnRef, which is a within-head chain and therefore legal.

<diggs:RIColumnSpecification 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:columnType codeSpace="">{0,1}</diggs:columnType>
  <diggs:riInstallationMethod>{0,1}</diggs:riInstallationMethod>
  <diggs:groutSpecificationRef xlink:href="" identifierRef="" nilReason="" owns="false">{0,unbounded}</diggs:groutSpecificationRef>
</diggs:RIColumnSpecification>

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="RIColumnSpecification" type="diggs:RIColumnSpecificationType" substitutionGroup="diggs:AbstractProgramSpecification"> <annotation> <documentation>The specification the rigid inclusion columns must satisfy: the constraints the work is judged against, as distinct from the design prepared to satisfy them. It is deliberately thin. Most of what a column specification says is limits (position tolerance, verticality tolerance, minimum embedment into the bearing stratum, permitted diameter and length ranges), and each is a diggs:DesignConformanceCriterion or diggs:PerformanceCriterion declared as a sibling under the specification slot of the program, with an operator, a limit with min, value and max and units, a statistic, and a basis that can express "two times the diameter" as readily as an absolute length. What remains here is the non-limit content: what technique is permitted and what material specification governs. It is also a single stable reference target: a diggs:RIColumn and a design cite it through programSpecificationRef, and each criterion cites it through basedOnRef, which is a within-head chain and therefore legal.</documentation> </annotation> </element>

Showing: