W3C home > Mailing lists > Public > public-xg-geo@w3.org > July 2006

Re: [georss] Geospatial Incubator Group

From: Andrew Turner <ajturner@highearthorbit.com>
Date: Thu, 20 Jul 2006 12:11:23 -0400
Message-ID: <4a31cd840607200911g71805f17m38de7566f2eecd@mail.gmail.com>
To: "Carl Reed OGC Account" <creed@opengeospatial.org>
Cc: "Mike Liebhold" <mnl@well.com>, "Josh@oklieb" <josh@oklieb.net>, "GeoXG GeoXG" <public-xg-geo@w3.org>, georss@lists.eogeo.org

Carl Reed OGC Account <creed@opengeospatial.org> wrote:
>
> Worse in the case of MS SenseWeb - they do not as yet use any international
> standards at all (IEEE, ISO, OGC). GeoRSS may not be the best solution for
> sensor networks as there is no ability to define the characteristics of the
> sensor, the characteristics of the observation, time, and so forth.
>
> But, if one only wants a simple point location and an "unknown" observation
> value with no related metadata, then GeoRSS could be used.
>

That's not necessarily true. GeoRSS is just a namespace extension to
RSS. Therefore, you have all of RSS to still use, or extend, with
other metadata. You could put sensor metadata in the summary and
updated fields, or even use one of the other sensor namespaces that is
pertinent to your specific application.

That's what makes GeoRSS nice, it isn't an application specific
markup. It is just a geo-extension to a very common format (set of
formats). Then its up to the Reader to handle other metadata (such as
data, manuf. controlling organization, etc) to parse and appropriately
display. If it doesn't know how to - for example you drop your Sensor
GeoRSS feed into Bloglines, then you'll just get unlocated
information, but it still works.


Andrew

-- 
Andrew Turner
ajturner@highearthorbit.com        42.4266N x 83.4931W
http://highearthorbit.com              Northville, Michigan, USA
Received on Thursday, 20 July 2006 21:12:11 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:21:18 GMT