Schema documentation for component diggs:AbstractObjectNoDescriptionType

Base type for all objects without description field. This is the fundamental abstract type for component objects (non-feature objects) in DIGGS, providing core properties including identifier,status, remark, and xml:lang, but excluding the description field. Used as a base for specialized objects where descriptions are not required or are provided through alternative mechanisms. Component objects typically represent supporting information like equipment, procedures, and metadata rather than primary geotechnical features.

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.

<complexType name="AbstractObjectNoDescriptionType" mixed="false" abstract="true">
  <annotation>
    <documentation>Base type for all objects without description field. This is the fundamental abstract type for component objects (non-feature objects) in DIGGS, providing core properties including identifier,status, remark, and xml:lang, but excluding the description field. Used as a base for specialized objects where descriptions are not required or are provided through alternative mechanisms. Component objects typically represent supporting information like equipment, procedures, and metadata rather than primary geotechnical features.</documentation>
  </annotation>
  <complexContent>
    <extension base="diggs:AbstractDiggsType">
      <sequence>
        <sequence>
          <element minOccurs="0" ref="gml:identifier"/>
          <element minOccurs="0" ref="diggs:status">
            <annotation>
              <documentation>A text string to provide information about the status of the object to be used to track QA/QC controls, review or release status, etc. The values used are intended to come from a controlled list of terms maintained by an organization.</documentation>
            </annotation>
          </element>
          <element maxOccurs="unbounded" minOccurs="0" ref="diggs:remark"/>
        </sequence>
      </sequence>
    </extension>
  </complexContent>
</complexType>

Showing: