[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [emergency] RE: OGC standards work in the
Cool, Carl, I was on my way to Nashville for the National Medical Banking Instiute, so just got this today. I will look into it as I catch up with everything else. Regards, Rex At 11:19 AM -0700 2/21/06, Carl Reed OGC Account wrote: >All - > >This is an informational email and is provided >in the spirit of promoting coordination and >harmonization efforts among and between >standards organizations. > >The OGC membership has been working on a series >of standards under an umbrella activity called >Sensor Web Enablement (SWE). Many of these draft >standards have been developed as the result of >OGC Interoperability Testbed activities, >specifically as part of the OGC Web Services >activities. As such, these draft standards have >been implemented and tested in a variety of >demonstration scenarios, all focused on >emergency services. The focus of the OGC sensor >related standards has to do with interfaces >(discovery, tasking, and access) and description >(sensor metadata). Please also note that the >interfaces and encodings described in the draft >standards have been designed to work with both >in-situ and dynamic sensors, ranging from >weather stations to UAVs to satellites to >traffic monitoring. In other words, these specs >are for the most part both application and >domain agnostic. > >I would encourage everyone to check out a movie >produced by WNET and done in concert with the >OGC and the members that captures the essence of >the OWS-3 demonstration >- <http://www.opengeospatial.org/demo/ows3/>http://www.opengeospatial.org/demo/ows3/ . >Much of the focus is on the discovery, and use >(fusion) of sensor inputs. > >Anyway, the OGC draft standards and best practices documents are: > >· Observations and Measurements, OGC Document 05-087 >· Sensor Alert Service, OGC Document 05-098 >· Sensor Model Language (SensorML) , OGC Document 05-086 >· Sensor Planning Service, OGC Document 05-089 >· SWE Architecture, OGC 05-090 >· Transducer Markup Language (TML), OGC Document 05-085 >· Web Notification Service, OGC Document 03-008r1 > >All of these documents have been approved for >public release by the OGC membership. SensorML, >Sensor Planning, Sensor Observation, and >TransducerML have now all entered the OGC RFC >process, the final step in becoming formal, >adopted OGC standards. There are numerous >commercial and government organizations backing >and endorsing these draft standards. > >As Dave pointed out today, we need to consider >just where the many sensor related standards fit >in the sensor and web services/SOA processing >stack. > >Regards > >Carl Reed, PhD >CTO and Executive Director Specification Program >OGC > >The OGC: Helping the World to Communicate Geographically > >--------------------- > >This communication, including attachments, is >for the exclusive use of addressee and may >contain proprietary, confidential or privileged >information. If you are not the intended >recipient, any use, copying, disclosure, >dissemination or distribution is strictly >prohibited. If you are not the intended >recipient, please notify the sender immediately >by return email and delete this communication >and destroy all copies. > >"The important thing is not to stop questioning." -- Albert Einstein -- Rex Brooks President, CEO Starbourne Communications Design GeoAddress: 1361-A Addison Berkeley, CA 94702 Tel: 510-849-2309
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]