Re: Re: mod_enclosures proposal

The approach of using rdf:resource (or rdf:about) to indicate the url of
the enclosure has the disadvantages that:

- it does not allow to assign properties to the enclosure that are not
properties of the enclosed documents. for example enclosures with the
same target may have different rdfs:label's and another rdfs:label may
be an appropriate for the target itself. also properties may be added to
an enclosure to tell clients how to present the resource to the user,
which dependents on the enclosing resource and not only on the enclosed
document.

- it is not suitable for protocols that support content-negotiatiation.
when the same resource has multiple enc:type's it is impossible to
associate these to the correct enc:length's or enc:qualitiy's. e.g., if
it seems obvious in this rdf/xml representation
    <enc:enclosure rdf:resource="http://example.org/images/logo"
enc:type="image/gif" enc:length="5897"/>
    <enc:enclosure rdf:resource="http://example.org/images/logo"
enc:type="image/png" enc:length="4987"/>
that the png version of the image is smaller than the gif version it is
not in the rdf graph: exchanging the values of the enc:length attributes
would result in the same rdf.

cheers,
reto


Suzan Foster wrote:

>On Nov 23, 2004, at 10:31 PM, [email protected] wrote:
>
>  
>
>>Is this valid RDF?
>>
>><enc:enclosure rdf:resource="http://some/external/file.mp3"
>>  enc:length="1939570" enc:type="audio/mpeg" />
>>    
>>
>
>The following four validate:
>
>1. <enc:enclosure enc:url="..." enc:type="..." enc:length="..."/>
>
>2. <enc:enclosure rdf:resource="..." enc:type="..." enc:length="..."/>
>
>3. <rdfs:seeAlso enc:url="..." enc:type="..." enc:length="..."/>
>
>4. <rdfs:seeAlso rdf:resource="..." enc:type="..." enc:length="..."/>
>
>My preference would be for either 1 or 2.
>
>Regards,
>Suzan Foster.
>
>  
>



 
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/