On 2009-12-14 13:26, Tatsuhiro wrote: > On 12月14日, 午後2:49, Anthony Bryan<[email protected]> wrote: > >> 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. >> >> > I think this text is clear and looks good. > BTW how should the client behave when such invalid Metalink documents > are given? > In aria2, I currently strip left and right white spaces for all values > in Metalink document version 3.0. > If URI has trailing white space, then it is 404 error. > For new IETF version, should the client not remove white spaces for > URI? > I also think this is good and clear. Metalink Editor also currently strips whitespace. With this in the standard most generators will hopefully start generating metalinks with no extra whitespace inside elements.
Perhaps it is simply best not to give any recommendation on how to deal with invalid metalinks (they are invalid, after all). Most implementations will probably accept some invalid metalinks anyway (e.g. by stripping leading and trailing whitespace). It would be pretty cool with a validation web site for metalinks, by the way. Something similar to http://validator.w3.org/. Anyone interested in creating something like that? I'll be interested in doing it, but I'd prefer to finish Metalink Editor 2.0 first (it is slowly making progress). -- 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.
