XML.orgXML.org
FOCUS AREAS |XML-DEV |XML.org DAILY NEWSLINK |REGISTRY |RESOURCES |ABOUT
OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [xml-dev] Lightweight, grassroots "observation" data format, withsupporting tools!

Having worked on a system that supported several 100 different devices I know some standardization could sure help.  The actual contents don't necessarily need to be standardized but standardized containers, protocols, and schema / meta languages sure would help.  Something like EXI would have made out jobs way easier...

Some of the manufacturers (in the satellite world in particular) also make a tidy profit by supporting their own gateways or more fully featured service endpoints to do conversions from some proprietary binary format to something like XML. For example, Digi will be happy to charge you a dollar (or maybe less) per device and give you a cloud based API with persistent storage behind it. Seems cheap until you do something like put a couple of devices in every office in a couple dozen buildings. You can usually roll your own handlers for the binary formats, there are usually some docs, but the XML formats are trivial to implement.

On Tue Dec 23 2014 at 9:32:10 AM Simon St.Laurent <simonstl@simonstl.com> wrote:
I'm not sure there's much to be gained from standardizing sensor data
formats as a whole.  Standardizing time, quantity, and unit pieces might
be worthwhile, but I don't see a point in trying to create a generic
"sensor data" format.

Thanks,
Simon

On 12/23/2014 10:10 AM, Peter Hunsberger wrote:
> Not a lot of standardization in that field, especially in the mobile
> devices. At the transport level you do have MQTT and there are a couple
> of small efforts to build some standards on top of that.  Most of the
> mobile stuff is binary, I've worked with devices from probably over a
> dozen manufacturers and you see a tiny bit of standardization around
> some ASCII with yea olde Hayes modem command sets and so called hex bin
> numerics.  At the home level you're starting to see a few manufacturers
> gaining some traction, the Rockchip WiMo (Wireless Mobile Multimedia
> Transmission Protocol)* has a fair number of devices and Google has some
> people jumping on whatever is behind the Nest devices. Lutron uses
> Telnet and a (proprietary) ASCII protocol which makes it very easy to
> work with.*
>
> On Tue Dec 23 2014 at 8:15:25 AM Costello, Roger L. <costello@mitre.org
> <mailto:costello@mitre.org>> wrote:
>
>     Hi Folks,
>
>     There is an exploding growth of sensors. Here are a few examples of
>     sensors:
>
>     -       flood gauges
>     -       air pollution monitors
>     -       thermostat
>     -       stress gauges on bridges
>     -       mobile heart monitors
>     -       traffic Webcams
>
>     Sensors take observations. For example an air pollution monitor
>     periodically measures (observes) the air pollution.
>
>     How do we structure the data generated by a sensor? Has anyone
>     created a _lightweight_ data format for observation data? If yes,
>     are there tools to process the data format?
>
>     I am aware of the OGC's Observations and Measurements stuff. [1]
>     It's nice, but I am wondering if there has been a bottom-up,
>     grassroots development of a lightweight data model for observations?
>
>     /Roger
>
>     [1] OGC Observations and Measurements:
>     http://www.opengeospatial.org/__standards/om
>     <http://www.opengeospatial.org/standards/om>
>
>     ___________________________________________________________________________
>
>     XML-DEV is a publicly archived, unmoderated list hosted by OASIS
>     to support XML implementation and development. To minimize
>     spam in the archives, you must subscribe before posting.
>
>     [Un]Subscribe/change address: http://www.oasis-open.org/__mlmanage/
>     <http://www.oasis-open.org/mlmanage/>
>     Or unsubscribe: xml-dev-unsubscribe@lists.xml.__org
>     <mailto:xml-dev-unsubscribe@lists.xml.org>
>     subscribe: xml-dev-subscribe@lists.xml.__org
>     <mailto:xml-dev-subscribe@lists.xml.org>
>     List archive: http://lists.xml.org/archives/__xml-dev/
>     <http://lists.xml.org/archives/xml-dev/>
>     List Guidelines:
>     http://www.oasis-open.org/__maillists/guidelines.php
>     <http://www.oasis-open.org/maillists/guidelines.php>
>

_______________________________________________________________________

XML-DEV is a publicly archived, unmoderated list hosted by OASIS
to support XML implementation and development. To minimize
spam in the archives, you must subscribe before posting.

[Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
Or unsubscribe: xml-dev-unsubscribe@lists.xml.org
subscribe: xml-dev-subscribe@lists.xml.org
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS