Schema documentation for component diggs:projectRef

The gml:identifier value of the referenced feature, as a fully qualified value. It gives an alternative to the gml:id in xlink:href for finding the referenced feature, mainly to reference a feature by a globally unique identifier and where naming conflicts occur with gml:id when accessing data in external files.

<element name="projectRef" type="diggs:FeatureReferenceType" minOccurs="1"> <annotation> <documentation>The project this sample is associated with. Required: every sample belongs to a project, which gives it its organizational and geographical context.</documentation> </annotation> </element>

Abstract base type for samples. A sample is physical material collected from a sampling feature during a sampling activity, or made by aggregating other samples. Samples link field investigations (sampling features) to laboratory testing (specimens and material tests), and record their collection location, parent sampling feature, collection method and physical characteristics. A sample can be subdivided into specimens for laboratory testing or aggregated from several source samples.

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="AbstractSampleType" abstract="true">
  <annotation>
    <documentation>Abstract base type for samples. A sample is physical material collected from a sampling feature during a sampling activity, or made by aggregating other samples. Samples link field investigations (sampling features) to laboratory testing (specimens and material tests), and record their collection location, parent sampling feature, collection method and physical characteristics. A sample can be subdivided into specimens for laboratory testing or aggregated from several source samples.</documentation>
  </annotation>
  <complexContent>
    <extension base="diggs:AbstractNamedFeatureType">
      <sequence>
        <element name="projectRef" type="diggs:FeatureReferenceType" minOccurs="1">
          <annotation>
            <documentation>The project this sample is associated with. Required: every sample belongs to a project, which gives it its organizational and geographical context.</documentation>
          </annotation>
        </element>
        <element ref="diggs:samplingActivityRef"/>
        <element minOccurs="0" ref="diggs:programRef">
          <annotation>
            <documentation>The program this sample is associated with. Where stated, this is the authoritative program for the sample; where absent, the program is that of the sampling activity, reached through samplingActivityRef. State it only where the program of the sample genuinely differs from that of its sampling activity, for example a sample re-tested under a later, separate testing program.</documentation>
          </annotation>
        </element>
        <element minOccurs="0" maxOccurs="unbounded" ref="diggs:programSpecificationRef">
          <annotation>
            <documentation>The program specification objects this sample must satisfy. The same override and fallback rule applies as for programRef.</documentation>
          </annotation>
        </element>
        <element ref="diggs:sampleProducedRef"/>
        <element minOccurs="0" maxOccurs="unbounded" ref="diggs:sampleGroupRef"/>
      </sequence>
    </extension>
  </complexContent>
</complexType>

Showing: