Re: Re: mod_enclosures proposal

[email protected] wrote:
> 
> --- In [email protected], Suzan Foster <su@i...> wrote:
> 
> 
>>You could define your own containers:
>>
>>   <rdfs:Class 
>>rdf:about="http://crocodile.org/ns/rss/1.0/enclosures#Parallel" 
>>rdfs:label="Parallel">
>>     <rdfs:subClassOf 
>>rdf:resource="http://www.w3.org/2000/01/rdf-schema#Container"/>
>>     ...
>>   </rdfs:Class>
> 
> 
> This is a very good idea. I like this approach. It is
> more in spirit or RDF.
me too!
> 
> In this case "children" property of "enclosures" will
> will point to subclass of rdf:Container. 
> We will define specific container types for "kind". 
> For "mixed" we can use  "rdf:Seq". I will check specs to 
> see if "Alt" supposed to
> preserve the order of elements. 
 From w3.org/TR/rdf-primer/: "An Alt container is intended to have at
least one member, identified by the property rdf:_1. This member is
intended to be considered as the default or preferred value. Other than
the member identified as rdf:_1, the order of the remaining elements is
not significant."

For enclosures it could be useful to have a "q" value anloguos to the
q-parameter in http-accept header, this would be more flexible than
defining the quality by the order of the elements. For example this
would allow to express that two alternatives have the same quality and
make it easier to find an algorithm for the client to choose the best
variant.
> It it does, we would use 
> "rdf:Alt".  If not we will define "enc1:Alt". For "parallel" 
> we will define "enc1:Parallel".

I would suggest to start the IDs for classes with an uppercase letter,
as it is becoming more common to mix different RDF-vocabularies there is
less reason to be like RSS (i hope RSS 1.1 will change this and avoid
having terms that are both property and class).

reto



 
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/