- From: <bugzilla@wiggum.w3.org>
- Date: Mon, 13 Apr 2009 17:27:42 +0000
- To: www-xml-schema-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=6695 --- Comment #2 from Dave Peterson <davep@iit.edu> 2009-04-13 17:27:42 --- It appears that 'leading' and 'trailing' can be interpreted to require something "in between", or not. It's clear that the WG intended "not": E.g., consider hexBinary which has whiteSpace = collapse. The element <gorp xsi:type=hexBinary> 00 </gorp> has its [actual value] the single-byte bit-string 00000000. It would be very counterintuitive if <gorp xsi:type=hexBinary> </gorp> was invalid rather than having the empty bit-string as its [actual value]. (Note that if all whitespace were removed from each example, their [actual value]s *would* be 00000000 and the empty bit-string, respectively.) Accordingly it appears clear that the intent in the spec is to interpret 'leading' and 'trailing' as *not* requiring something in between. The editors propose to add, after the serntence beginning "After the processing implied by replace": This means a string consisting entirely of whitespace is first replaced with a single space character (#x20) and then that character is removed, since it is considered to be both a leading and trailing character; the final result is the empty character string. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Monday, 13 April 2009 17:27:52 UTC