(a) <metadata> name
no one has a better name for URIs to torrents/metalinks? :)
(b) <verification> info does not apply to <metadata> files (torrents,
metalinks) but to the files the metadata points to.
(c) need to add a file attribute to <metadata> so you can specify one
file from a multi-file torrent or metalink. (see Matt's discussion,
did we resolve this?)
(d) <type> name
I think <type> could be interesting/useful. but I think we need a more
descriptive name, like <dynamic> or...any ideas?
4.2.16. The "metalink:type" Element
The "metalink:type" element is a Text construct that describes
whether the IRI from "metalink:origin" in a Metalink will contain
dynamic updated Metalinks or static content that is not updated.
metalinkType =
element metalink:type {
"static" | "dynamic"
}
(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.
(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.
--
(( 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
-~----------~----~----~----~------~----~------~--~---
