OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

wss message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [wss] White space (was RE: [wss] Proposal for a new attribute of UsernameToken)

I agree with what's been said. Some additional data:

I believe that whitespace is illegal around xsd:dateTime.
However, because our schema type derives from xsd:string
Eric's text is important.

DSig states that whitespace is significant for c14n purposes
and within KeyName. The only deviation is distinguished name
encoding: Given that whitespace must be trimmed *within* the
dname, trimming it *around* the dname was not an egregious

Whitespace compression within attributes depends on the
attribute type (non-CDATA); with other data-type normalization
and insignificant whitespace trimming, this is a headache
for dsig: If you generate and sign a non-normalized document,
and the recipient tries to verify a validated copy of the
document the signature will fail.

So, in addition to everything else, only sign normalized


>> From: Eric Gravengaard [mailto:eric@reactivity.com]
>> I think I agree with Irving. But I think that we should be 
>> clear about that in this spec then since we are being very 
>> clear about how to use the nonce ("the octet sequence of its 
>> decoded value").
>> I propose the following change:
>> Change:
>> "hashed using the octet sequence of its UTF8 encoding as 
>> specified in the contents of the element". 
>> To
>> "hashed using the octet sequence of its UTF-8 encoding as 
>> specified in the contents of the element including any whitespace"
>> The schema derives the <Created> element from xsd:string so I 
>> don't believe that it is otherwise specified what a leading 
>> space would mean and I believe that we should leave no doubts 
>> in the minds of those implementing our spec.
>> -Eric
>My point is that the meaning of white space *is* specified by XML:
>a) No distinction is made between white space and any other character data in 
>element content. That is, *every character* is significant. The one caveat is 
>that conforming parsers MUST normalize line endings to the linefeed character 
>U+000A before passing character data to the application.
>b) White space inside attribute values is transformed and compressed - whateve
>r the input looks like, conforming parsers are required to i)turn all other wh
>ite space characters to spaces (U+0020) and ii) compress runs of spaces to a s
>ingle space, before passing the attribute value to the application.
>c) In DTDs (I'm not sure about XML Schema or other proposals) it's possible to
> specify that whitespace *between* elements is insignificant. In that case, fo
>r example, given input as below:
>  <foo>bar</foo>
>  <baz>fumble</baz>
>a conforming, *validating* parser would not pass the newlines and spaces betwe
>en <fee> and <foo>, </foo> and <baz>, or </baz> and </fee> to the application.
>It is important that everybody implementing XML processors understand that the
>y MUST NOT arbitrarily reformat XML documents. Don't pretty-print, don't compr
>ess runs of white space, don't convert tabs to spaces or vice versa.
>Here http://lists.oasis-open.org/archives/security-services/200202/msg00018.ht
>ml is the detailed proposal I wrote up for the SAML spec on how to compare str
>ings; it has references to some of the W3C and Unicode related specs.
> - irving -
>To unsubscribe from this mailing list (and be removed from the roster of the O
>ASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/wss/members/leave

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]