W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2008

Re: [APPS-REVIEW] Metalink XML Download Description Format (draft-bryan-metalink-01)

From: Julian Reschke <julian.reschke@gmx.de>
Date: Tue, 02 Sep 2008 11:35:17 +0200
Message-ID: <48BD08D5.1070206@gmx.de>
To: Dave Cridland <dave@cridland.net>
CC: Anthony Bryan <anthonybryan@gmail.com>, general discussion of application-layer protocols <discuss@apps.ietf.org>, Applications Review List <apps-review@ietf.org>, xml-dev@lists.xml.org, ietf-http-wg@w3.org

Dave Cridland wrote:
> ...
> 11) Section 4.2.17: Does that "type" attribute totally suck? Of course, 
> you have to have it because every man, his dog, and his pet hampster has 
> decided that only HTTP is allowed, these days, for absolutely 
> everything, leading to a totally useless URI scheme which essentially 
> fails to describe the actual resource it's supposedly a locator for. 
> Okay, rant over, back to the review.
> ...

"4.2.17. The "metalink:url" Element


    The "metalink:url" element contains the IRI of a file.  All IRIs
    should lead to identical files, except in the case of type
    "bittorrent" where the IRI should lead to a .torrent file."

Actually, don't do that. Don't make the meaning of an element totally 
dependent on an attribute on it. If torrent files are a special case 
(can there be more...?), then define a separate element.

BR, Julian
Received on Tuesday, 2 September 2008 09:36:00 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:50:54 GMT