RE: Why XML (was: Re: What I see as problems to solve ... and a strawman solution)

Martin Duerst <[email protected]>
Newsgroups gmane.mail.ng
Message-ID <4.2.0.58.J.20040202144451.07b5a4a8@localhost>
At 14:56 04/02/01 -0800, Jim Schaad wrote:

>  I would think very carefully before I looked at adopting the XML signature
>specification for signing messages, especially if you are looking at only
>doing partial signing of documents.
>
>One of the biggest issues that has evolved over the development of this
>specification is the concept of canonicalization.  The problem with this is
>that many XML parsers play games with whitespace (lose it, gain it, combine
>it, ignore it) and an system where nodes read and write back out XML on the
>way to deliver things can cause many problems of keeping data unchanged.

XML defines exactly what an XML processor (parser) can do and what not.
It's somewhat complicated at first sight, but there are no choices.
Of course, the application on top of the parser may do whatever it chooses,
but that's a different issue. For details, please see
http://www.w3.org/TR/REC-xml#sec-white-space and
http://www.w3.org/TR/REC-xml#sec-line-ends.

If different parsers actually give you different whitespace for
the same document, at least one of them is non-conformant.

Regards,   Martin.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.