[georss] Geolocation by reference

[Raj Singh]

I just read this. Here's what I got out of it:
- Reference a location using a URI
- There is nothing about the encoding of the location
- Include an 'updated' timestamp in the location encoding (something  
we should consider for georss?)
- Include an 'expires' timestamp in the location encoding
---
Raj


On Nov 12, 2007, at 3:37 PM, Carl Reed OGC Account wrote:

> Back to an older LbR thread. Attached is the IETF document on LbR. I  
> am not suggesting that their approach be followed as they are  
> specifically focused on how to express LbR as part of a value chain  
> that may start with a DHCP packet and end up at a 9-1-1 dispatch  
> center.
>
> Anyway, they have done some hard thinking and had numerous  
> discussion on this topic. I would encourage reading section 5. At  
> the very least, it would be nice to be aligned with the internet  
> community at the abstract or information model level.
>
> Cheers
>
> Carl
>
> ----- Original Message ----- From: "Raj Singh" <raj at rajsingh.org>
> To: "Sean Gillies" <sgillies at FRII.COM>
> Cc: <georss at lists.eogeo.org>
> Sent: Monday, November 12, 2007 12:24 PM
> Subject: Re: [georss] Geolocation by reference
>
>
>> I don't feel bad about breaking compatibility with other RSS flavors.
>> IMHO, there's so much good, well-designed functionality in Atom the
>> other RSSes should be deprecated now.
>> ---
>> Raj
>>
>>
>> On Nov 12, 2007, at 12:42 PM, Sean Gillies wrote:
>>
>>> Extending atom:link (like Josh suggested) with new relationships  
>>> seems
>>> more and more the way to go. It's an Atom-only solution unless you
>>> extend RSS 1/2 feeds with atom:link, but that's fine with me. If
>>> OpenSocial takes off the Atom/Geo community is going to be huge.
>>
>> _______________________________________________
>> georss mailing list
>> georss at lists.eogeo.org
>> http://lists.eogeo.org/mailman/listinfo/georss
> <draft-ietf-geopriv-lbyr-requirements-01.txt>