Schema documentation for component diggs:RILTPSpecification

The specification a load transfer platform must satisfy. It is even thinner than diggs:RIColumnSpecification, for the same reason: platform requirements are overwhelmingly limits (minimum thickness, target relative compaction, permitted settlement), and each limit is an acceptance criterion declared as a sibling under the specification slot of the program, citing this object through basedOnRef. The fill gradation envelope is carried here and target compaction is not: target relative compaction is a single limit with an operator, so it is an acceptance criterion, whereas a gradation envelope is a pair of curves and cannot be an operator and limit. The curve pair reuses the shape of diggs:GroutSpecificationType. The shape of the envelope is provisional pending review by the subject matter expert.

<diggs:RILTPSpecification 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:materialType xlink:href="" nilReason="">{0,1}</diggs:materialType>
  <diggs:platformType>{0,1}</diggs:platformType>
  <diggs:aggregateGradationCurveCoarseLimit>{0,1}</diggs:aggregateGradationCurveCoarseLimit>
  <diggs:aggregateGradationCurveFineLimit>{0,1}</diggs:aggregateGradationCurveFineLimit>
</diggs:RILTPSpecification>

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="RILTPSpecification" type="diggs:RILTPSpecificationType" substitutionGroup="diggs:AbstractProgramSpecification"> <annotation> <documentation>The specification a load transfer platform must satisfy. It is even thinner than diggs:RIColumnSpecification, for the same reason: platform requirements are overwhelmingly limits (minimum thickness, target relative compaction, permitted settlement), and each limit is an acceptance criterion declared as a sibling under the specification slot of the program, citing this object through basedOnRef. The fill gradation envelope is carried here and target compaction is not: target relative compaction is a single limit with an operator, so it is an acceptance criterion, whereas a gradation envelope is a pair of curves and cannot be an operator and limit. The curve pair reuses the shape of diggs:GroutSpecificationType. The shape of the envelope is provisional pending review by the subject matter expert.</documentation> </annotation> </element>

Showing: