W3C home > Mailing lists > Public > w3c-ietf-xmldsig@w3.org > July to September 2001

Re: FW: Base64

From: Joseph Reagle <reagle@w3.org>
Date: Tue, 4 Sep 2001 14:53:09 -0400
To: "Gregor Karlinger" <gregor.karlinger@iaik.at>
Cc: "XMLSigWG" <w3c-ietf-xmldsig@w3.org>, elena@apache.org
Message-Id: <20010904185310.4D99E87400@policy.w3.org>

Gregor,

Since you already have an account and opened the issue, would you take the 
action to reopen the bug report [1] with an explaination that Xerces is 
collapsing the white space facet of the wrong item [2]? We can refer them to 
Henry Thomson and the Schema WG if they have further questions about the 
Infoset and Post Schema Infoset contributions.

[1] http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1228
[2] http://lists.w3.org/Archives/Public/w3c-ietf-xmldsig/2001JulSep/0209.html


On Tuesday 04 September 2001 07:08, Henry S. Thompson wrote:
> First check -- neither XML 1.0 nor XML Infoset specifies any notion of
> normalised value for element content.
>
> Conformant XML Schema processors add a [schema normalized value]
> property to element info items validated with simple type definitions.
>
> > There are scenarios in which people validate the signature itself
> > (instead of the data it signs which is served by an explicit
> > transform) and this then affects the computation of the signature:
> > the signature's base64 data [1] whitespace is collapsed:
> >
> >    "For all *atomic* data-types other than string ... the value of
> >    whitespace is collapse." [2]
>
> This describes the whitespace normalization that takes place in
> computing the [schema normalized value] -- nothing to do with element
> content per se.
>
> ht
Received on Tuesday, 4 September 2001 14:53:14 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:21:36 UTC