On Friday 14 February 2003 16:15, John Boyer wrote: > On the other hand, the XML rule for element 'content' refers to > 'CharData', which only forbids the use of less-than (<) and ampersand (&) > in character content. The canonicalization rule for text node processing > was based on the CharData rule, so it is possible to get a correct c14n > program to write data that Xerces cannot read and that is possibly not > well-formed XML. I'm not sure what you mean by "based on", but if one accepts Francois's interpretation -- these chars are already excluded -- does anything have to change in c14n? The c14n for a text node takes the string value of the XPath text node and escapes '#xD', '<', and '>', but if these are precluded characters from the start, they wouldn't have appeared in an XPath text node, right?Received on Friday, 21 February 2003 13:29:58 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:32 GMT