Schema documentation for component diggs:AbstractLaboratoryTestProcedure

Base type for laboratory test procedure objects. A laboratory test procedure is performed on a specimen derived from a sample that was collected from a samplingFeature, and therefore the sample's location is known and relates to a geographic feature of interest. Use of a laboratory test procedure within a Test object does not require that information about the specific sample or specimen is known, only that the source location of the sample is known or recorded. This allows results of a test to be transferred without specific information about the sample or specimen.

<diggs:AbstractLaboratoryTestProcedure gml:id="" xml:lang="" xmlns:diggs="http://diggsml.org/schema-dev" xmlns:gml="http://www.opengis.net/gml/3.2">
  <gml:description xlink:actuate="" xlink:arcrole="" xlink:href="" nilReason="" xlink:role="" xlink:show="" xlink:title="" xlink:type="simple">{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:actuate="" xlink:arcrole="" xlink:href="" nilReason="" owns="false" xlink:role="" xlink:show="" xlink:title="" xlink:type="simple">{0,unbounded}</diggs:associatedFile>
  <diggs:role>{0,unbounded}</diggs:role>
  <diggs:remark>{0,unbounded}</diggs:remark>
  <diggs:testProcedureMethod xlink:actuate="" xlink:arcrole="" xlink:href="" nilReason="" owns="false" xlink:role="" xlink:show="" xlink:title="" xlink:type="simple">{0,unbounded}</diggs:testProcedureMethod>
  <diggs:testProcedureEquipment xlink:actuate="" xlink:arcrole="" xlink:href="" nilReason="" owns="false" xlink:role="" xlink:show="" xlink:title="" xlink:type="simple">{0,unbounded}</diggs:testProcedureEquipment>
  <diggs:testingEnvironment>{0,unbounded}</diggs:testingEnvironment>
  <diggs:otherTestProperty>{0,unbounded}</diggs:otherTestProperty>
  <diggs:testEvent>{0,1}</diggs:testEvent>
  <diggs:specimen xlink:actuate="" xlink:arcrole="" xlink:href="" nilReason="" owns="false" xlink:role="" xlink:show="" xlink:title="" xlink:type="simple">{0,unbounded}</diggs:specimen>
</diggs:AbstractLaboratoryTestProcedure>

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.

<div> <h3>lang (as an attribute name)</h3> <p>denotes an attribute whose value is a language code for the natural language of the content of any element; its value is inherited. This name is reserved by virtue of its definition in the XML specification.</p> </div> <div> <h4>Notes</h4> <p>Attempting to install the relevant ISO 2- and 3-letter codes as the enumerated possible values is probably never going to be a realistic possibility.</p> <p>See BCP 47 at <a href="http://www.rfc-editor.org/rfc/bcp/bcp47.txt">http://www.rfc-editor.org/rfc/bcp/bcp47.txt</a>and the IANA language subtag registry at <a href="http://www.iana.org/assignments/language-subtag-registry">http://www.iana.org/assignments/language-subtag-registry</a>for further information.</p> <p>The union allows for the 'un-declaration' of xml:lang with the empty string.</p> </div>

<element name="AbstractLaboratoryTestProcedure" type="diggs:AbstractLaboratoryTestProcedureType" substitutionGroup="diggs:AbstractTestProcedure" abstract="true"> <annotation> <documentation>Base type for laboratory test procedure objects. A laboratory test procedure is performed on a specimen derived from a sample that was collected from a samplingFeature, and therefore the sample's location is known and relates to a geographic feature of interest. Use of a laboratory test procedure within a Test object does not require that information about the specific sample or specimen is known, only that the source location of the sample is known or recorded. This allows results of a test to be transferred without specific information about the sample or specimen.</documentation> </annotation> </element>

Showing: