Re: Re: mod_enclosures proposal

> 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.

Why not #4?  The idea being if we're going to get developers to pay
attention to things we might as well get them to be able to do more than
just one thing.  If it uses an rdfs:seeAlso with an rdf:resource and a
separate type we'd be opening the door to a lot more than just enclosures.
Granted, the interest exists for enclosures and I'm all for the idea but
wonder if we'd be needlessly limiting things by not using #4.  I suppose
there would need to be something in the markup that made the assertion it's
indeed a thing to be used as an enclosure and #2 is probably "simpler" at
doing this.  I wonder if it's not overly simplified.

For those not versed in RDF consider that by using an rdf:resource on the
URL (which #2 also does) makes for much easier finding its use in a
triplestore situation.  Or in a big index or archive of lots of feeds.
Using it as a enc:url type would /require/ use of an RDF schema to clarify
it's semantics.  As in, a query for "everything using that URL as a
resource" could help build out a list of quite a lot more than just looking
for enc:url uses.   At the same time, making use of a seeAlso opens the door
for developers to use a single interface to detect "other things" being
available for an item.  This as opposed to multiple interfaces for each and
every type of other thing.

Support for an enclosure is indeed a compelling feature to add and could
well stand on it's own.  I'm just thinking about the two-step process of
"hey, something else and it's an enclosure" allowing for more extensibility
than just "hey, it's an enclosure".

-Bill Kearney
Syndic8.com



 
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/