[georss] WAS: GeoRSS Validation Service? RETURNING TO: multiple locations and time

[Mikel Maron]

Hi Brian

Don't want to belabor the issue, but I very much share your interest in representing time and space,
and my inkling on the best way to go is leveraging RSS time/event namespaces already in use.
Small pieces, loosely joined, of simple targeted vocabularies. I sent some links in the thread a few
weeks back, here's another demo of using the Upcoming.org GeoRSS/Event feeds 

http://worldkit.org/upcoming/

If you 'd like to pursue this course, well, let's do it!

Mikel



----- Original Message ----
From: "Knoth, Brian D." <bknoth at mitre.org>
To: Joshua Lieberman <josh at oklieb.net>; georss at lists.eogeo.org
Sent: Wednesday, February 28, 2007 12:28:06 PM
Subject: Re: [georss] WAS: GeoRSS Validation Service? RETURNING TO: multiple locations and time

Josh,

If by Give-and-Take, you mean that I should go off and implement my own
extension(s) or utilize some combination of existing extensions for
time windows and locations (while providing a loose referential linking
between them) to support what I need, then I feel I have been very
accommodating this. These are the suggestions that I've received and
I'm being forced to accept them because my original recommendation to
this mailing list of simply allowing the GML representation of space
with time in the geoRSS profile has been discarded.

I just don't understand how an extension whose main purpose which is to
represent location (ie, geoRSS:where) can ignore the fact that stuff is
at a place at a specific time, usually for a period of time, and then
at some other place for other period of time. This fact just seems so
basic that to ignore it seriously limits the applicability of geoRSS to
anything more than possibly just the world of blogging. GE does a great
job of activating and deactivating things that are outside of their
time windows when TimePeriods are specified in KML. I've heard some
unsubstantiated rumors that GE may support geoRSS in the future - if
that is the case, shouldn't the hooks at least be inserted into geoRSS
now to begin preparing for that usage? 

So you are absolutely correct...I can build proprietary extensions and
mechanisms for supporting this in our RSS feeds. I have felt, and still
strongly do feel, that the proper place for this is within a maturing
RSS extension such as geoRSS which, hopefully for its own adoption
sake, can provide the building blocks necessary to support
functionality required by not only the Flikrs and blogs, but also
Enterprise RSS as well.

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




-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.eogeo.org/pipermail/georss/attachments/20070228/3cd02c7d/attachment.html