here's the current text, suggested by Julian Reschke: All leading and trailing whitespace is part of the element content, and MUST NOT be ignored. Consequently, it is disallowed for elements where the defined type does not allow whitespace, such as dates, integers, or IRIs. Some XML-generating implementations erroneously insert white space around values by default, and such implementations will generate invalid Metalink Documents.
On Sun, Dec 13, 2009 at 9:30 PM, Peter Pöml <[email protected]> wrote: > Hi, > > a discussion how whitespace should be treated came up on the apps-discuss > list [*]. > > Short summary: > > Whitespace matters in all of Metalink's XML elements, and MUST not be > ignored; it's part of their content. This also implies a caveat for > generators to make sure that some XML library that's used doesn't add > whitespace around values by default. (The exmples in the Internet Draft need > to be fixed to match this. This affects date fields and IRIs (URLs).) > However, a more relaxed scheme that would strip trailing and leading > whitespace has been suggested: > http://www.ietf.org/mail-archive/web/apps-discuss/current/msg01189.html > > I'm pondering on this, and would love to hear some opinions... > > Peter > > [*] https://www.ietf.org/mailman/listinfo/apps-discuss -- (( 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.
