[georss] GeoRSS Location References

[Ron Lake]

Hi,

In GML the type of the resource referenced in the link is signaled by
the remoteSchema attribute.  This is usually an xpointer expression that
references a schema fragment describing the resource.  It is up to the
application to decide if it wants to fetch the remote schema fragment
and validate the remote resource.

In RDF all such references (rdf:resource) must comply with the resource
type identified in the schema (RDFS).  RDF parsers always fetch and
validate such links.  This was felt to be too heavy weight in GML.

Ron


-----Original Message-----
From: georss-bounces at lists.eogeo.org
[mailto:georss-bounces at lists.eogeo.org] On Behalf Of Raj Singh
Sent: March 30, 2008 8:42 PM
To: GeoRss
Subject: Re: [georss] GeoRSS Location References

On Mar 30, 2008, at 11:25 PM, Christopher Schmidt wrote:
>> 1) Sean, does your proposal only work with Atom?
>
> Insofar as GeoRSS has meaning within RSS2, I think that <atom:link>  
> oes
> as well.

Thinking about it a bit more, I guess it works fine. It just feels  
really strange using <atom:link> in RSS2 or RSS1.

>
>
>> 2) Is there any important advantage for software to know a little
>> about what the referenced link will contain prior to dereferencing  
>> it?
>> If so, then Andrew's ideas where you still have a <where>, <point>,
>> <line> or <polygon> is useful.
>
> You can describe this in <atom:link rel="type">, perhaps?


That's loading a lot of semantics into rel -- not only the fact that  
it's a location, but also the type of geometry. And we'll also need to  
signal whether the link is to simple georss or GML. But if people  
really feel they need to know geometry type before dereferencing, fine  
with me.

---
Raj

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