Schema documentation for component diggs:DesignMeasurement

A design for a measurement: the planned counterpart of a realized diggs:AbstractMeasurement. One type serves every kind of measurement, whether an in-situ test, a laboratory test on a sample, a monitoring campaign, a measurement taken while drilling or a geophysical survey, because what is plannable (what it is done on, where, by what method, how often, how densely, for how long) is common to all of them. A realized measurement cites its design through programDesignRef.

<diggs:DesignMeasurement 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:programSpecificationRef xlink:href="" identifierRef="" nilReason="" owns="false">{0,unbounded}</diggs:programSpecificationRef>
  <diggs:nonConformanceRef xlink:href="" identifierRef="" nilReason="" owns="false">{0,unbounded}</diggs:nonConformanceRef>
  <diggs:progress>{0,1}</diggs:progress>
  <diggs:plannedEquipment xlink:href="" nilReason="" owns="false">{0,unbounded}</diggs:plannedEquipment>
  <diggs:otherDesignProperty>{0,unbounded}</diggs:otherDesignProperty>
  <diggs:measurementKind codeSpace="">{0,1}</diggs:measurementKind>
  <diggs:samplingFeatureDesignRef xlink:href="" identifierRef="" nilReason="" owns="false">{0,unbounded}</diggs:samplingFeatureDesignRef>
  <diggs:sampleDesignRef xlink:href="" identifierRef="" nilReason="" owns="false" percentage="">{0,unbounded}</diggs:sampleDesignRef>
  <diggs:constructionActivityDesignRef xlink:href="" identifierRef="" nilReason="" owns="false">{0,1}</diggs:constructionActivityDesignRef>
  <diggs:measurementLocation owns="false" xlink:href="" nilReason="">{0,1}</diggs:measurementLocation>
  <diggs:measurementMethod xlink:href="" nilReason="" owns="false">{0,unbounded}</diggs:measurementMethod>
  <diggs:plannedProcedure xlink:href="" nilReason="" owns="false">{0,unbounded}</diggs:plannedProcedure>
  <diggs:readingFrequency howDetermined="" qualifier="" uom="">{0,1}</diggs:readingFrequency>
  <diggs:duration howDetermined="" qualifier="" uom="">{0,1}</diggs:duration>
  <diggs:testingDensityPerLength howDetermined="" qualifier="" uom="">{1,1}</diggs:testingDensityPerLength>
  <diggs:testingDensityPerArea howDetermined="" qualifier="" uom="">{1,1}</diggs:testingDensityPerArea>
  <diggs:testingDensityPerElement howDetermined="" qualifier="" uom="">{1,1}</diggs:testingDensityPerElement>
  <diggs:testedFraction howDetermined="" qualifier="" uom="">{0,1}</diggs:testedFraction>
  <diggs:testLoadPercentDesignLoad howDetermined="" qualifier="" uom="">{0,1}</diggs:testLoadPercentDesignLoad>
</diggs:DesignMeasurement>

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="DesignMeasurement" type="diggs:DesignMeasurementType" substitutionGroup="diggs:AbstractMeasurementDesign"> <annotation> <documentation>A design for a measurement: the planned counterpart of a realized diggs:AbstractMeasurement. One type serves every kind of measurement, whether an in-situ test, a laboratory test on a sample, a monitoring campaign, a measurement taken while drilling or a geophysical survey, because what is plannable (what it is done on, where, by what method, how often, how densely, for how long) is common to all of them. A realized measurement cites its design through programDesignRef.</documentation> </annotation> </element>

Showing: