The spec is a bit tricky in this aspect. The lexical space of normalizedString doesn't allow #xd, #xa, #x9 characters. But the string is first normalized (ws='replace' here) before it's checked against the lexical space. And during the normalization, all those characters are replaced by #x20. So your example is perfect legal.
The following [1] is the related constraint in the spec, but I suspect it would confuse you more. :-) [1] Bullet 3.1.3 of "http://www.w3.org/TR/xmlschema-1/#cvc-type";. Cheers, Sandy Gao Software Developer, IBM Canada (1-905) 413-3255 [EMAIL PROTECTED] Dave Flanagan <[EMAIL PROTECTED] To: [EMAIL PROTECTED] .com> cc: Subject: Xerces and Schema built in derived type normalizedString 11/18/2002 06:15 PM Please respond to xerces-j-user Not sure if it is something I am missing(probably the case) but if I define an element <sample> as type normalizedString as defined by the W3 schema such that an xml document has the structure below <sample> This is not a normalized String </sample> I would imagine that Xerces should find the above element invalid according to its schema - but I cannot seem to get it to complain about the above element content. is it something I am missing - or something that is a problem ? Any help would be greatly appreciated Dave Flanagan <-- no not the one you may be thinking of _________________________________________________________________________ This mail sent via toadmail.com, web e-mail @ ToadNet - want to go fast? http://www.toadmail.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
