Schema documentation for component diggs:DesignProductionSequence

The order in which the work of a whole program is to be carried out across all of its designs: columns installed, boreholes drilled, samples taken, measurements made. One object holds one order, so whether one feature is produced after a second and before a third is answered from a single series of numbers, wherever the three are designed. Declare it in the program's design slot, after the designs it orders. A diggs:ClearanceConstraint on the program (a minimum spacing to fresh work, a minimum age before adjacent work) attaches through programSpecificationRef.

<diggs:DesignProductionSequence 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:step dimension="2" xlink:href="" sequenceNumber="">{1,unbounded}</diggs:step>
</diggs:DesignProductionSequence>

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="DesignProductionSequence" type="diggs:DesignProductionSequenceType" substitutionGroup="diggs:AbstractProgramDesign"> <annotation> <documentation>The order in which the work of a whole program is to be carried out across all of its designs: columns installed, boreholes drilled, samples taken, measurements made. One object holds one order, so whether one feature is produced after a second and before a third is answered from a single series of numbers, wherever the three are designed. Declare it in the program's design slot, after the designs it orders. A diggs:ClearanceConstraint on the program (a minimum spacing to fresh work, a minimum age before adjacent work) attaches through programSpecificationRef.</documentation> </annotation> </element>

Showing: