DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20363>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20363 Some invalid IDREFS, ENTITIES, and NMTOKENS attributes not reported during valdiation. Summary: Some invalid IDREFS, ENTITIES, and NMTOKENS attributes not reported during valdiation. Product: Xerces2-J Version: 2.4.0 Platform: All OS/Version: All Status: NEW Severity: Normal Priority: Other Component: DTD AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] The DTD validator does not report some invalid IDREFS, ENTITIES, and NMTOKENS. The problem is in ListDatatypeValidator. It allows the following to slip through: 1) Attributes of those types containing the character reference . This reference is legal in XML 1.1, and by default StringTokenizer uses 0x0C as one of its delimiters. Form feed (0x0C) isn't even XML white space. 2) Attributes of those types which have leading or trailing whitespace chars after normalization, which you can get if you specify an attribute value with char references to 0x09, 0x0A, and 0x0D. 3) Attributes of those types which don't meet changes to the Names and Nmtokens production, as stated in E20 of the XML 1.0 SE Errata (http://www.w3.org/XML/xml-V10-2e-errata#E20). In summary, IDREFS, ENTITIES, and NMTOKENS before attribute normalization cannot contain references to whitespace characters other than 0x20, in order for them to meet the Names and Nmtokens productions after normalization. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
