root-element and arbitrary triples in RSS (Re: Setting up a purl for rss/1.1)

Christopher Schmidt wrote:

>
>Since no source is going to want to aggregate these "arbitrary triples" 
>anyway, why would allowing them make any sense? 
>  
>
If we keep the promise of extensibility these triples are a must. People 
start to add "foaf:maker" properties even if there is no RSS-extension 
module yet.

Even for extension modules the inability to add top level resources may 
cause awful hacks. Some examples

- Annotations

because the a:annotates property of annotea[1] points from the 
a:Annotation to the annotated Item the annotation can only be integrated 
using the undefined a:hasAnnotation (inverse of a:annotates).

- foaf:maker

the foaf:maker points to an anonymous resource, in RSS 1.1 its 
properties must be shown as xml-child-elements. Since multiple items may 
have the same maker the elements are referenced by nodeID. The xml would 
be cleaner if the expansion of the maker would not have to be 
arbitrarily associated to an item but serialized as a second element 
after the channel.

- Reifications

a modules that wants to express meta-information on some triples in the 
model (like saying that the statement "item1 dc:author 'Einstein'" has 
been marked as possible bug) would have to define how the 
ReifiedStatement are to be used as object of statement in the 
channel-tree. However there is no relation between the channel and the 
ReifiedStatement.

reto

1. http://www.w3.org/2000/10/annotation-ns


 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/rss-dev/

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/