[georss] "When" information in georss

[Ron Lake]

I don't understand the statement below " I was hoping for a more generic
definition of time (not even necessarily bound to geo* - so not GML".
There is no necessity of a bind to Geo in GML.  We have customers using
GML for sensor data transmission where there is no geo-component at all
- but GML provides the observation construct AND a good time model that
they like, not to mention value objects and dynamic features.  Of course
when you also have a geo component that can easily be added.

R

Ron Lake
CEO and Chairman
Galdos Systems Inc
+1-604-484-2751
Be there when GIS and the Web unite! Register now for GeoWeb 2007 at
www.geoweb.org


-----Original Message-----
From: georss-bounces at lists.eogeo.org
[mailto:georss-bounces at lists.eogeo.org] On Behalf Of Carl Reed OGC
Account
Sent: August 6, 2007 11:36 AM
To: Andrew Turner; Sean Gillies
Cc: georss at lists.eogeo.org
Subject: Re: [georss] "When" information in georss

Why not GML? There is a rapidly growing international movement in
various 
scientific and research communities (such as Oceans monitoring and 
environmental monitoring) to enable and make web accessible (via
standard 
interfaces) numerous sensor networks using the new OGC Sensor
Observation 
Service (SOS) and/or WFS. Both return GML responses.

Would be nice to be consistent.

Just wondering.

Carl

----- Original Message ----- 
From: "Andrew Turner" <ajturner at highearthorbit.com>
To: "Sean Gillies" <sgillies at frii.com>
Cc: <georss at lists.eogeo.org>
Sent: Wednesday, August 01, 2007 4:15 PM
Subject: Re: [georss] "When" information in georss


> b/c the current Time specification doesn't actually specify including
> the time element in the response. This is similar to the Geo that uses
> GeoRSS, and not OpenSearch-Geo, to specify the geographic search
> parameters.
>
> I was hoping for a more generic definition of time (not even
> necessarily bound to geo* - so not GML), but RSS or Atom don't support
> that it appears (which is actually kind of surprising?
>
> On 8/1/07, Sean Gillies <sgillies at frii.com> wrote:
>> Andrew Turner wrote:
>> > On 7/29/07, Sean Gillies <sgillies at frii.com> wrote:
>> >> The time period that the feed is valid for for ... that would be
>> >> published/updated up until *now* right? It seems that the best way
to
>> >> indicate a future limit would be for the feed's origin server to
set 
>> >> an
>> >> "Expires" HTTP header. That would be going with the grain of the
Web.
>> >
>> > I may have requested a feed for another, arbitrary time period, say
>> > 4-20-2007 > 5-15-2007
>> >
>> > And relying on just the HTTP headers means that I then lose that
>> > information if I store the file. So like GeoRSS feeds can have a
>> > geometry that applies to the entire feed, it would be nice to use
the
>> > timespan to define a timespan for the entire feed. This is
especially
>> > important if I request a feed for that month, even if there are
only
>> > items for a week in the middle. The feed still is of the entire
month.
>> >
>> > Brian - can you put that example as a page on the GeoRSS CMS?
>> >
>> > Thanks,
>> > Andrew
>> >
>>
>> Andrew,
>>
>> Assuming you're using OpenSearch to request a feed using a temporal
>> query, could you not rely on the os:Query element that you would
include
>> in the response?
>>
>> Sean
>>
>> _______________________________________________
>> georss mailing list
>> georss at lists.eogeo.org
>> http://lists.eogeo.org/mailman/listinfo/georss
>>
>
>
> -- 
> Andrew Turner
> ajturner at highearthorbit.com      42.2774N x 83.7611W
> http://highearthorbit.com              Ann Arbor, Michigan, USA
> Introduction to Neogeography - http://oreilly.com/catalog/neogeography
> _______________________________________________
> georss mailing list
> georss at lists.eogeo.org
> http://lists.eogeo.org/mailman/listinfo/georss 

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