ID -08 is out, which addresses some of these issues. http://tools.ietf.org/html/draft-bryan-metalink-08
please provide feedback, improvements, & corrections. :) On Fri, Jul 3, 2009 at 4:27 PM, Anthony Bryan<[email protected]> wrote: > > (b) <verification> info does not apply to <metadata> files (torrents, > metalinks) but to the files the metadata points to. 4.2.9. The "metalink:metadata" Element The "metalink:metadata" element contains the IRI of metadata about a resource to download. For example, this could be the IRI of a BitTorrent .torrent file or a Metalink Document. Note that the information in the metalink:verification element does not apply to these files. > (e) where a metalink is static or dynamic, it will be nice to have > <origin> to know where it came from, if you're finding the metalink > from some other site. so I need to change or removed the following > text: > > o If metalink:type is "dynamic", metalink:metalink elements MAY > contain exactly one metalink:origin element. o metalink:metalink elements SHOULD contain exactly one metalink: origin element. > (f) generator has a name, URI, and version. > > this whole section is borrowed from atom, I wonder how much it's used > in atom & if it helps? we currently can include a generator name. is a > URI and version really necessary for figuring out if a generator is > spurting out bad metalinks? isn't <origin> a better way to track down > an offender? > > 4.2.3. The "metalink:generator" Element > > The "metalink:generator" element's content identifies the agent used > to generate a Metalink Document, for debugging and other purposes. > > metalinkGenerator = element metalink:generator { > metalinkCommonAttributes, > attribute uri { metalinkUri }?, > attribute version { text }?, > text > } > > The content of this element, when present, MUST be a string that is a > human-readable name for the generating agent. Entities such as > "&" and "<" represent their corresponding characters ("&" and > "<" respectively), not markup. > > The metalink:generator element MAY have a "uri" attribute whose value > MUST be an IRI reference [RFC3987]. When dereferenced, the resulting > URI (mapped from an IRI, if necessary) SHOULD produce a > representation that is relevant to that agent. > > The metalink:generator element MAY have a "version" attribute that > indicates the version of the generating agent. 4.2.3. The "metalink:generator" Element The "metalink:generator" element's content identifies the generating agent name and version, separated by a "/", used to generate a Metalink Document, for debugging and other purposes. metalinkGenerator = element metalink:generator { metalinkCommonAttributes, text } The content of this element, when present, MUST be a string that is a human-readable name and version, separated by a "/", for the generating agent. For example, "MirrorBrain/2.8.1", where "MirrorBrain" is the name and "2.8.1" is the version. Entities such as "&" and "<" represent their corresponding characters ("&" and "<" respectively), not markup. -- (( 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 -~----------~----~----~----~------~----~------~--~---
