TML

TransducerML and possible mechanism integration

Demos

• IRIS Sensor Observation Service Argon ST IRIS Group SOS provides front end for accessing live TML data streams.

Excerpts from TML documents

From the TML Application note "No. 1 – Why Would I Use TML?:

Transducer Markup Language (TML) is an XML-based system for capturing, characterizing and enabling the transport of raw sensor data. It has elements designed to make it a self-contained package, including not only the raw data but also information about that data which is necessary to process it later.

Some excerpts from the TML specification 1.0.0 particularly focused on streaming:

7.4 Live and Historical Streaming Data

Because transducers are real world interfaces, their responses are representative of the changing world. This changing world is represented in live streaming transducer data. TML captures this living streaming data, which is representative of real world transducer events corresponding to multiple phenomena and maintains the relative and absolute temporal and spatial relationships of the data such that we can review the events exactly as they happened either live in real time or at a different place and/or a different time. TML data represents a continuous stream of data from or for possibly a multitude of different transducers, all interleaved randomly, in roughly chronological order. It is up to the data acquisition equipment to capture the data as precisely and accurately as possible such that the precision and accuracy capabilities of the transducers are fully recognized and the acquisition process is not degrading the data in any fashion. The task of data integration and understanding is left to the transducer processors.

7.13 TML data stream

TML implements a time tagged implementation of XML. What this means is that a system time clock count is inserted into the start tag of TML data elements to signify the relative time (from the sysClk) (or absolute time, in some cases) to indicate when the data contained in each TML element was acquired. The system clock should be of sufficient resolution to adequately relate time differences at a transducer sample sub-sampling interval (approximately an order of magnitude faster that the fastest sample clock in the system) and enough digits to minimize the possibility of a roll over.

7.20 TML and binary data

From TML Applications note 3 -- http://www.ogcnetwork.net/node/105

Transducer Markup Language (TML) allows you to handle multiple data sources and to fuse them for processing and analysis, using each data source to enhance and complement the others.
(...)
Once data from multiple sources is combined into a single TML data stream using a common format, several good things happen:

1. Analysis of data becomes easier since it’s all in one place viewed from a single processor display
2. Common processing tools for multiple types of data sources can be developed
3. Common data display and representation is far easier, shifting the focus to data fusion rather than data integration

Aditional notes

Integration

I think there are some possible alternatives for integration of the various mechanisms, roughly illustrated in this diagram:

That is:

• A TML stream as a wrapper for the original, native stream
• A TML stream as a wrapper for the RBNB stream
• An RBNB stream directly
• Combine TML/RBNB with TML's out-of-band capability.
• SOS Feeder used to update the SOS db.

Implementation