RE: [georss] Geospatial Incubator Group

From: Ron Lake <rlake@galdosinc.com> · Date: Thu, 20 Jul 2006 10:05:06 -0700

If you can embed GML features (of any kind) in the Atom feed then you
can have O&M (a GML Application Schema) or more simply still use the
built in GML observation or create a user-defined application schema for
sensor data. All of these methods are in use today in real world
applications.

Cheers

Ron

-----Original Message-----
From: georss-bounces@lists.eogeo.org
[mailto:georss-bounces@lists.eogeo.org] On Behalf Of Carl Reed OGC
Account
Sent: July 20, 2006 9:52 AM
To: Andrew Turner
Cc: GeoXG GeoXG; georss@lists.eogeo.org
Subject: Re: [georss] Geospatial Incubator Group

Andrew -

Excellent points and I agree - although Atom might not be the best
mechanism 
for expressing the necessary and complete set of Sensor metadata and
sensor 
processes. That is what the SensorML and Observations and Measurements 
specifications are highly suited for. It might be interesting to see how
to 
embed a SensorML based sensor payload in an Atom feed.

Cheers

Carl

----- Original Message ----- 
From: "Andrew Turner" <ajturner@highearthorbit.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>
Sent: Thursday, July 20, 2006 10:11 AM
Subject: Re: [georss] Geospatial Incubator Group

> 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 

_______________________________________________
georss mailing list
georss@lists.eogeo.org
http://lists.eogeo.org/mailman/listinfo/georss