Schema documentation for component diggs:RIColumnConstruction

The act of constructing one rigid inclusion column: drilling and, where the method grouts through the auger stem, grouting. It carries the real-time telemetry record. The method followed over each part of the column and the events recorded while it was formed are stated through the constructionMethod and constructionEvent properties inherited from diggs:AbstractConstructionActivity; where they disagree with the record, the record governs. The inherited samplingFeatureRef must target a diggs:RIColumn; XSD cannot say so, because the particle is declared on the abstract base type and an extension cannot narrow it, so the reference-validation module checks it. The activity is scoped to column construction only: its content model (installationRecord, terminationOutcome, toeEmbedment, the embedment-layer choice, riInstallationMethod, groutLevelCorrectiveAction) is meaningless for a platform. Load transfer platform construction is compaction, not drilling or grouting, and has no activity object, because nothing is routinely observed during LTP construction and its results (lift structure, material, thickness) are recorded on the as-built diggs:LoadTransferPlatform feature. A non-conformance cannot be carried by a construction activity, since a feature may have none: diggs:NonConformance is carried by diggs:AbstractSamplingFeatureType and diggs:AbstractSampleType.

<diggs:RIColumnConstruction 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:investigationTarget>{0,unbounded}</diggs:investigationTarget>
  <diggs:projectRef xlink:href="" identifierRef="" nilReason="" owns="false">{1,unbounded}</diggs:projectRef>
  <diggs:samplingFeatureRef xlink:href="" identifierRef="" nilReason="" owns="false">{1,1}</diggs:samplingFeatureRef>
  <diggs:programRef xlink:href="" identifierRef="" nilReason="" owns="false">{0,1}</diggs:programRef>
  <diggs:programDesignRef xlink:href="" identifierRef="" nilReason="" owns="false">{0,unbounded}</diggs:programDesignRef>
  <diggs:programSpecificationRef xlink:href="" identifierRef="" nilReason="" owns="false">{0,unbounded}</diggs:programSpecificationRef>
  <diggs:constructionMethod xlink:href="" nilReason="" owns="false">{0,unbounded}</diggs:constructionMethod>
  <diggs:constructionEvent>{0,unbounded}</diggs:constructionEvent>
  <diggs:constructionEnvironment xlink:href="" nilReason="" owns="false">{0,unbounded}</diggs:constructionEnvironment>
  <diggs:equipment xlink:href="" nilReason="" owns="false">{0,unbounded}</diggs:equipment>
  <diggs:otherConstructionActivityProperty>{0,unbounded}</diggs:otherConstructionActivityProperty>
  <diggs:activityDateTime>{0,1}</diggs:activityDateTime>
  <diggs:delay>{0,unbounded}</diggs:delay>
  <diggs:installationRecord index="">{0,unbounded}</diggs:installationRecord>
  <diggs:terminationOutcome>{0,1}</diggs:terminationOutcome>
  <diggs:toeEmbedment howDetermined="" qualifier="" uom="">{0,1}</diggs:toeEmbedment>
  <diggs:embedmentLayer>{1,1}</diggs:embedmentLayer>
  <diggs:embedmentLayerRef xlink:href="" identifierRef="" nilReason="" owns="false">{1,1}</diggs:embedmentLayerRef>
  <diggs:riInstallationMethod>{0,1}</diggs:riInstallationMethod>
  <diggs:groutLevelCorrectiveAction>{0,1}</diggs:groutLevelCorrectiveAction>
</diggs:RIColumnConstruction>

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="RIColumnConstruction" type="diggs:RIColumnConstructionType" substitutionGroup="diggs:AbstractConstructionActivity"> <annotation> <documentation>The act of constructing one rigid inclusion column: drilling and, where the method grouts through the auger stem, grouting. It carries the real-time telemetry record. The method followed over each part of the column and the events recorded while it was formed are stated through the constructionMethod and constructionEvent properties inherited from diggs:AbstractConstructionActivity; where they disagree with the record, the record governs. The inherited samplingFeatureRef must target a diggs:RIColumn; XSD cannot say so, because the particle is declared on the abstract base type and an extension cannot narrow it, so the reference-validation module checks it. The activity is scoped to column construction only: its content model (installationRecord, terminationOutcome, toeEmbedment, the embedment-layer choice, riInstallationMethod, groutLevelCorrectiveAction) is meaningless for a platform. Load transfer platform construction is compaction, not drilling or grouting, and has no activity object, because nothing is routinely observed during LTP construction and its results (lift structure, material, thickness) are recorded on the as-built diggs:LoadTransferPlatform feature. A non-conformance cannot be carried by a construction activity, since a feature may have none: diggs:NonConformance is carried by diggs:AbstractSamplingFeatureType and diggs:AbstractSampleType.</documentation> </annotation> </element>

Showing: