|
|||
|
TransducerML and possible mechanism integration
Demos
Excerpts from TML documentsFrom 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 DataBecause 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 streamThe TML data stream is a product generated from a TML system. The TML data stream carries the time varying data representing various external and internal phenomena. The opening TML tag initiates a stream. A stream may be promptly terminated at any point at which time the reading machine should add a closing TML tag to make the terminated stream valid XML. If the stream is terminated normally a closing tag from the sender will terminate the 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 dataBecause XML cannot efficiently carry binary data, as discussed previously, TML enables the binary data to be sent or exchanged via binary means.
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.
Aditional notes
IntegrationIn the context of the SOS getObservation operation:I think there are some possible alternatives for integration of the various mechanisms, roughly illustrated in this diagram: That is:
ImplementationAs there seem to be no available software to consume/produce TML data, I went ahead with some preliminary tests of a JABX-based databinding for TML.
|
This material is based upon work supported by the National Science Foundation under award 0619060. Any opinions, findings and conclusions or recomendations expressed in this material are those of the author(s) and do not necessarily reflect the views of the National Science Foundation (NSF). Copyright 2007 |