Am 14.12.2009 um 13:26 schrieb Tatsuhiro:
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 think I would do exactly that.I just would not strip whitespace from the fields that contain text (description/license) or signatures.
Peter
smime.p7s
Description: S/MIME cryptographic signature
