Metalink Team,

Greetings.  I am working on a proposal to the HTML5 working group.  The 
proposal intends to include examples of how HTML5 can extend to include the 
expressiveness of metalink.

The following example indicates several premises simultaneously:

<html xmlns:dc="http://purl.org/dc/elements/1.1/";>
 <a dc:title="Example" dc:language="en" dc:description="Text 
description.">Example
  <link rel="alternate" type="multipart/mixed" 
?:hash="md5:e4d909c290d0fb1ca068ffaddf22cbd0" 
href="torrent+http://www.example.com/example1.ext.torrent";>
   <link rel="part" type="video/avi" ?:hash="..."/>
   <link rel="part" type="image/png" ?:hash="..."/>
  </link>
  <link rel="alternate" type="multipart/mixed" ?:hash="..." 
href="torrent+http://www.example.com/example2.ext.torrent";>
     <link rel="part" type="video/mpeg" ?:hash="..."/>
   <link rel="part" type="image/png" ?:hash="..."/>
  </link>
  <link rel="alternate" type="multipart/mixed" ?:hash="..." 
href="torrent+http://www.example.com/example3.ext.torrent";>
   <link rel="part" type="video/ogg" ?:hash="..."/>
   <link rel="part" type="image/png" ?:hash="..."/>
  </link>
 </a>
</html>

Firstly, the use of the "multipart/mixed" MIME type.  Secondly, the <link 
rel="alternate" .../>, which intends to indicate a set of alternative resource 
locations in a manner similar to metalink.  Thirdly, the <link rel="part" 
.../>, which intends to indicate the substructure of a "multipart/mixed" MIME 
type.  Fourthly, the indicated "torrent+http://"; protocol syntax.  Fifthly, the 
use of attributes to indicate at least file hashes.  Sixthly, a possible syntax 
for hash attribute value strings.

If a protocol, capable of multiple files, such as torrent, references one file, 
then the following syntax is indicated:

<a type="video/ogg" 
href="torrent+http://example.com/example3.ext.torrent";>Example</a>

Where the torrent file is, in the example, containing one video file.

If a protocol, capable of multiple files, such as torrent, references multiple 
files, then the "multipart/mixed" MIME type is indicated and the <link 
rel="part" .../> can be in the substructure of an anchor tag:

<a type="multipart/mixed" 
href="torrent+http://example.com/www.example.ext.torrent";>Example
 <link rel="part" type="video/ogg"/>
 <link rel="part" type="image/png"/>
</a>

I wanted to broach these ideas with you and to invite a discussion towards 
arriving at the best possible proposal for the HTML5 team.



Kind regards,

Adam Sobieski







                                          

-- 
You received this message because you are subscribed to the Google Groups 
"Metalink Discussion" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/metalink-discussion?hl=en.

Reply via email to