Anthony Bryan wrote:
> o metalink:metalink elements SHOULD contain exactly one metalink:
> origin element.
SHOULD contain one always? Not only if dynamic?
What "origin" element would be used if I create a metalink using a graphical
tool, and then send it by email to a friend? (the .metalink itself never
had a URI in the whole process)
> Entities such
> as "&" and "<" represent their corresponding characters ("&"
> and "<" respectively), not markup.
Do we need to say that? Anyone not following this is violating the *XML*
spec.
It's used in Atom and/or RSS specs (don't remember which) because of the
sheer amount of noobs who think they can parse RSS with their own
hand-written parsers instead of using a real XML library...
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
