[georss] GeoRSS Validation Service?

Andrew Turner georss at highearthorbit.com
Mon Feb 26 17:46:58 EST 2007


On 2/26/07, Joshua Lieberman <josh at oklieb.net> wrote:
> Peter,
>
> There was much (months, years) discussion of this, and the decision
> came out in favor of simplicity. It is more complicated for a client
> to represent and work with a complex multiple geometry; and it is
> more difficult to figure out its purpose, e.g. which point
> corresponds to which part or aspect of the referenced Web resource.
> For the same reason, only one georss:where element is allowed per item.
>
> If the aim is to represent a region for the resource, an envelope or
> polygon does the job more simply and clearly.
>

I am in agreement with you on this Peter - it seems like there should
be a simple way to have multiple geometries per item. Simple use
cases:
 1) Item talks about hospitals in a city, want Points for hospital locations
 2) Item is a story about a trip, want Points and lines to reference
the hikes/locations visited

both of these use cases aren't solved by having multiple items. The
solution I've seen so far is to use Microformats within the content
itself to mark adr or geo, but this really isn't an entirely
satisfactory solution and uses a different technology.

What I would hope emerge would be a way to have multiple
<georss:point> (or whatever) for use case 1, or that include a
reference to an element (div or something) within the content for use
case 2.

Perhaps there is someone that can put out an example of a currently
supported solution we can all use in the meantime?

Andrew



More information about the georss mailing list