|
|||
|
Sensor Web Enablement: A synopsisThe SWE initiative seeks to provide interoperability between disparate sensors and sensor processing systems by establishing a set of standard protocols to enable a "Sensor Web," by which sensors of all types in the Web are discoverable, accessible, and taskable. The SWE standards allow the determination of the capabilities and quality of measurements from sensors, the retrieval of real-time observations in standard data formats, the specification of tasks to obtain observations of interest, and the asynchronous notification of events and alerts from remote sensors. SWE components include models and XML Schemas (SensorML, Observations&Measurements, TransducerML) and Web service interfaces (SOS, SPS, SAS, WNS), which are briefly described as follows:
Getting streaming observation dataThe following diagram (taken from here), shows how a client application can obtain streaming data from a provider through the SOS interface.
Streams, SWE, and RBNBCurrently, we are investigating the feasibility and suitability of providing SWE-related interfaces to RBNB data. A possible goal in this direction is to design and implement Kepler actors to get sensor data using some of the SWE services, for example, an SosReaderActor to connect to an SOS server. In this case, an SOS server would be implemented on top of an RBNB server. In COMET we are starting to get direct access to various data streams from BML, so we will be using these data sources as well in our testbed. We are considering setting up an RBNB server on COMET to handle the BML streams. This will provide us with more options for our tests.
TransducerML
Some notes about TML
Demos
Attachments:
|
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 |