On Sat, Jan 10, 2009 at 5:26 PM, Hampus Wessman
<[email protected]> wrote:
> Yep, that's good IMO.
>
> I've actually been reading it some more and spotted a few more things worth
> commenting. Most of them are just small misses (probably due to earlier
> changes).
thanks!
> metalink:verification (4.1.5)
> It may contain exactly one metalink:signature element. This has probably
> changed at some point, because there's no ? after metalinkSignature and
> above the bullet list the text says that some of these elements are required
> (but none are). "elements" could be in singular too (after "...contain
> exactly one metalink:signature").
we want to allow multiple signature elements. we only have one type
listed in the spec that we can define now, but want to define more.
metalinkVerification =
element metalink:verification {
metalinkCommonAttributes,
(metalinkHash*
& metalinkPieces*
& metalinkSignature?
& extensionElement*)
}
The following child elements are defined by this specification:
o metalink:verification element MAY contain one or more metalink:
hash elements.
o metalink:verification element MAY contain one or more metalink:
pieces elements.
o metalink:verification element MAY contain one or more metalink:
signature elements.
> metalink:resources (4.1.4)
> metalink:metadata could also be added to the schema and introducing
> paragraph here.
good. could you also check the schema in the latest svn version?
4.1.4. The "metalink:resources" Element
The "metalink:resources" element acts as a container for metadata and
data associated with the listed files. It contains one or more
metalink:url child elements. It can also contain one or more
metalink:metadata child elements.
metalinkResources =
element metalink:resources {
metalinkCommonAttributes,
extensionElement*
metalinkURL*
metalinkMetadata*
}
This specification assigns no significance to the order of metalink:
url elements. Significance is determined by the value of the
"preference" attribute of the metalink:url elements.
The following child elements are defined by this specification (note
that the presence of some of these elements is required):
o metalink:resources element MUST contain at least one metalink:
metadata element or at least one metalink:url element. Typically,
metalink:resources element contains more than one metalink:url
element to provide multiple download sources.
> That's all for now. Have a great 2009 everyone!
>
>
> Anthony Bryan wrote:
>
> thanks for the review! you caught some good things!
>
> I changed it to:
>
> o metalink:resources element MUST contain at least one metalink:
> metadata element or at least one metalink:url element. Typically,
> metalink:resources element contains more than one metalink:url
> element to provide multiple download sources.
>
> is that ok, or is there a better way to word it?
>
> On Fri, Jan 9, 2009 at 2:57 PM, Hampus Wessman <[email protected]>
> wrote:
>
>
> I just read the current draft and I must say that it's really good!!
> It's very clear and I like the new standard too. It shows that the
> metalink format has been around for some time. Lots of improvements!
>
> Just a few comments on small things:
>
> Somewhere it says:
> metalink:metalink elements MAY contain exactly one metalink:origin
> element. If metalink:type is "dynamic", metalink:metalink
> elements MAY contain exactly one metalink:origin element.
> Looks like an unnecessary repetition. The same for metalink:updated a
> few lines down.
>
> metalink:resources element MUST contain at least one metalink:url
> element, but couldn't it be useful with a metalink that only contains
> metalink:metadata tags (and no urls)?
>
> Great work!
> Hampus Wessman
>
>
> Anthony Bryan wrote:
>
>
> http://www.ietf.org/internet-drafts/draft-bryan-metalink-04.txt
>
> A new version of I-D, draft-bryan-metalink-04.txt has been successfuly
> submitted by Anthony Bryan and posted to the IETF repository.
>
> Filename: draft-bryan-metalink
> Revision: 04
> Title: The Metalink Download Description Format
> Creation_date: 2008-12-31
> WG ID: Independent Submission
> Number_of_pages: 36
>
> Abstract:
> This document specifies Metalink Documents, an XML-based download
> description format.
>
>
>
>
>
>
>
>
> >
>
--
(( 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
-~----------~----~----~----~------~----~------~--~---
