I added language element and the location & preference attributes to
the example at the beginning of the ID.
<?xml version="1.0" encoding="UTF-8"?>
<metalink xmlns="urn:ietf:params:xml:ns:metalink">
<published>2008-05-15T12:23:23Z</published>
<files>
<file name="example.ext">
<identity>Example</identity>
<version>1.0</version>
<language>en</language>
<description>A description of the example file for
download.</description>
<verification>
<hash type="sha-1">80bc95fd391772fa61c91ed68567f0980bb45fd9
</hash>
</verification>
<resources>
<url location="de" preference="95">
ftp://ftp.example.com/example.ext</url>
<url location="fr" preference="100">
http://example.com/example.ext</url>
<metadata type="torrent" preference="90">
http://example.com/example.ext.torrent
</metadata>
</resources>
</file>
</files>
</metalink>
On Jul 8, 4:20 pm, Anthony Bryan <[email protected]> wrote:
> (See fwded msg for details).
>
> I'll replace the references to ISO639-2/RFC 3066 with RFC 4646 for
> now, & try to keep on top of when draft-ietf-ltru-4646bis gets an RFC
> number.
>
> Do you know if our schema needs to be modified beyond substituting RFC
> numbers in there?
>
> # As defined in RFC 3066
> metalinkLanguageTag = xsd:string {
> pattern = "[A-Za-z]{1,8}(-[A-Za-z0-9]{1,8})*"
> }
>
> PS - It also looks like there's an updated version of ISO3166-1 too.
>
> [ISO3166-1]
> International Organization for Standardization, "ISO 3166-
> 1:2006. Codes for the representation of names of
> countries and their subdivisions -- Part 1: Country
> codes", November 2006.
>
> ---------- Forwarded message ----------
> From: Felix Sasaki <[email protected]>
> Date: Wed, Jul 8, 2009 at 3:32 PM
> Subject: Re: [xml-dev] Metalink Download Description Format (XML)
> To: Anthony Bryan <[email protected]>
>
> Cc: [email protected]
>
> Not the main topic of this draft, but you are refering to ISO693-2 for
> the metalink:language element, and define the "metalinkLanguageTag"
> pattern terms of RFC 3066. You should define both in terms of RFC
> 4646, the current RFC for BCP 47 (the BCP for language identifiers).
> Actually a successor for RFC 4646 has just been
> approvedhttp://tools.ietf.org/html/draft-ietf-ltru-4646bis-23
> which soon will get a new RFC number.
>
> Felix
>
> 2009/7/9 Anthony Bryan <[email protected]>
>
> > Progress continues on the Metalink ID (
> >http://tools.ietf.org/html/draft-bryan-metalink).
>
> > With guidance from Eran Hammer-Lahav, we are focusing on the Metalink
> > XML file format. We've currently addressed all feedback, and welcome
> > more.
>
> > Metalink is an XML-based document format that describes a file or
> > lists of files to be added to a download queue. Lists are composed
> > of a number of files, each with an extensible set of attached
> > metadata. For example, each file can have a description, checksum,
> > and list of URIs that it is available from.
>
> > The primary use case that Metalink addresses is the description of
> > downloadable content in a format so download agents can act
> > intelligently and recover from common errors with little or no user
> > interaction necessary. These errors can include multiple servers
> > going down and data corrupted in transmission.
>
> > Other features:
> > Structured information about downloads that can be used by search
> > engines, etc.
> > Increased security (checksums, signatures).
> > Can combine FTP and HTTP with optional Peer-to-peer (P2P, shared
> > bandwidth).
> > Add multiple files to a download queue.
> > Transparent usage where people can get the benefits of Metalink
> > without even knowing they're using it.
>
> > --
> > (( Anthony Bryan ... Metalink [http://www.metalinker.org]
> > )) Easier, More Reliable, Self Healing Downloads
>
> > _______________________________________________________________________
>
> > XML-DEV is a publicly archived, unmoderated list hosted by OASIS
> > to support XML implementation and development. To minimize
> > spam in the archives, you must subscribe before posting.
>
> > [Un]Subscribe/change address:http://www.oasis-open.org/mlmanage/
> > Or unsubscribe: [email protected]
> > subscribe: [email protected]
> > List archive:http://lists.xml.org/archives/xml-dev/
> > List Guidelines:http://www.oasis-open.org/maillists/guidelines.php
>
> --
> (( Anthony Bryan ... Metalink [http://www.metalinker.org]
> )) Easier, More Reliable, Self Healing Downloads
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
