[georss] Geolocation by reference

[Sean Gillies]

Andrew Turner wrote:
> 
> On Nov 15, 2007, at 4:27 PM, Sean Gillies wrote:
> 
> 
>>>
>>> How would this work with multiple geometries for a single entry? Somehow
>>> referring to an element id within the content would be nice.
>>>
>>
>> Multiple geometries:
>>
>> <georss:where
>>   scheme="http://example.com/vocabularies/x"
>>   term="is-bounded-by">...</georss:where>
>>
>> <georss:where
>>   scheme="http://example.com/vocabularies/x"
>>   term="is-centered-on">...</georss:where>
>>
>> I feel the story of different geometries related to different sections
>> of the content is beyond the scope of Atom. An Atom entry representing a
>> bibliographic record about "Voyage Autour Du Monde" or containing a blog
>> post about a backcountry ski trip would be well served by a single line
>> or multipoint geometry in a georss:where element.
> 
> This doesn't address that you speak of 5 locations in your single entry
> on your Voyage. Brandon's MetaCarta GeoRSS parser is a particularly
> exemplary case of needing a way to reference items within the content.
> His demo geoparser includes about 15 locations for every news item, and
> it's not clear what bits refer to what part of the article.

Yes, I understand, but I don't think it matters that much to most of us.
The article is the "atom". Annotate it with a multipoint or a bounding
polygon and call it good.

But on the other hand, I do see a neat solution for those who crave more
precision. I'm happy to consult with companies on implementing it,
although I guarantee that you'll slap yourself on the forehead when I
explain it to you ;)

Interop in 2009 it is then.

Sean

>>>>
>>>> with the no attribute case defaulting to "is-located-at" works.
>>>>
>>>>>
>>>>> We're *way* behind on moving forward with some of the outstanding
>>>>> 'feature requests' that we were thinking about for GeoRSS v1.2 (I
>>>>> believe 1.1 was a 'bug fix'?). What say we put together this SRC
>>>>> proposal, Toponym, Multiple Geometry and others as potential specs and
>>>>> do an email discussion vote for a 1.2 update?
>>>>>
>>>>
>>>> Working my proposal into GeoRSS in some form would be great. I'm also
>>>> hoping to find some folks who would like to help me write a "best
>>>> geospatial practices for Atom" document.
>>>
>>> Well, it would help if you put up a page on the GeoRSS.org CMS kind of
>>> summarizing the proposal. A BP for GeoAtom would be great!
>>>
>>
>> I want to field test this a bit to make sure that it's not just geo
>> wankery. How about another attempt at Geo-Atom interop?
> 
> Sounds good, but for me it would probably have to wait until after the
> New Year.
> 
>>
>> 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
> 
> 
>