tml:data 

this element carries the date to or from transducer systems.  The data element will carry a single instance or a continuous stream of a condition or set of synchronous conditions time tag to the precise instant of creation.   There is no XML markup of data within the data tag.  A system description will describe the decoding and understanding of the data within the data tag.

Element Information

Model

Attributes

QName Type Fixed Default Use Inheritable Annotation
clk xs:integer optional 
sys clock state at trigger point to data cluster.  For low sampling frequency transducers this high frequency clock state may not be required.  A full dateTime attribute may suffice for time synchronization of data.
contents restriction of xs:string optional 
If a binary stream header does not contain a contents field then the data cluster is by default explicit data.  This field is encoded as a binary (2-bits) "00" in a binary file if the field is contained.
dateTime xs:dateTime optional 
Full qualified date and time of transducer or process producing this data. For low sampling frequency transducers this high frequency clock state may not be required.  A full dateTime attribute may suffice for time synchronization of data.
ismclass ClassificationType optional 
security classification of each data cluster. Overall data classification of  transducer data in clusterDescription.  Overall classification of file or stream in tml start tag.
ref xs:string optional 
alias or short id reference of transducer or process producing this data
reference xs:anyURI optional 
this is the full UID reference to the cluster description
seq xs:integer optional 
if no "total" attribute exist then this attribute can be used to number the data elements like a count, this enables the receipt end to determine if any data clusters were lost.
total xs:integer optional 
total in sequence e.g. 1 of 4, 2 of 4.  1 and 2 being the seq number and 4 being the total

Used By

Element tml:tml

Source 

<xs:element name="data">
  <xs:annotation>
    <xs:documentation>this element carries the date to or from transducer systems. The data element will carry a single instance or a continuous stream of a condition or set of synchronous conditions time tag to the precise instant of creation. There is no XML markup of data within the data tag. A system description will describe the decoding and understanding of the data within the data tag.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:simpleContent>
      <xs:extension base="xs:string">
        <xs:attribute name="ref" type="xs:string" use="optional">
          <xs:annotation>
            <xs:documentation>alias or short id reference of transducer or process producing this data</xs:documentation>
          </xs:annotation>
        </xs:attribute>
        <xs:attribute name="clk" type="xs:integer" use="optional">
          <xs:annotation>
            <xs:documentation>sys clock state at trigger point to data cluster. For low sampling frequency transducers this high frequency clock state may not be required. A full dateTime attribute may suffice for time synchronization of data.</xs:documentation>
          </xs:annotation>
        </xs:attribute>
        <xs:attribute name="reference" type="xs:anyURI" use="optional">
          <xs:annotation>
            <xs:documentation>this is the full UID reference to the cluster description</xs:documentation>
          </xs:annotation>
        </xs:attribute>
        <xs:attribute name="dateTime" type="xs:dateTime" use="optional">
          <xs:annotation>
            <xs:documentation>Full qualified date and time of transducer or process producing this data. For low sampling frequency transducers this high frequency clock state may not be required. A full dateTime attribute may suffice for time synchronization of data.</xs:documentation>
          </xs:annotation>
        </xs:attribute>
        <xs:attribute name="contents" use="optional">
          <xs:annotation>
            <xs:documentation>If a binary stream header does not contain a contents field then the data cluster is by default explicit data. This field is encoded as a binary (2-bits) "00" in a binary file if the field is contained.</xs:documentation>
          </xs:annotation>
          <xs:simpleType>
            <xs:restriction base="xs:string">
              <xs:enumeration value="exp"/>
              <xs:enumeration value="imp"/>
            </xs:restriction>
          </xs:simpleType>
        </xs:attribute>
        <xs:attribute name="seq" type="xs:integer" use="optional">
          <xs:annotation>
            <xs:documentation>if no "total" attribute exist then this attribute can be used to number the data elements like a count, this enables the receipt end to determine if any data clusters were lost.</xs:documentation>
          </xs:annotation>
        </xs:attribute>
        <xs:attribute name="total" type="xs:integer" use="optional">
          <xs:annotation>
            <xs:documentation>total in sequence e.g. 1 of 4, 2 of 4. 1 and 2 being the seq number and 4 being the total</xs:documentation>
          </xs:annotation>
        </xs:attribute>
        <xs:attribute name="ismclass" type="ism:ClassificationType">
          <xs:annotation>
            <xs:documentation>security classification of each data cluster. Overall data classification of transducer data in clusterDescription. Overall classification of file or stream in tml start tag.</xs:documentation>
          </xs:annotation>
        </xs:attribute>
      </xs:extension>
    </xs:simpleContent>
  </xs:complexType>
</xs:element>

Sample