This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
In serialization section 4, phase 2b states that character maps are not applied in elements included with cdata-section-elements. This seems an odd provision, and I wonder what the rationale for it is? It upsets the sequential pipeline of character processing, and it's not clear to me that it has any user benefits. It encourages users to use cdata-section-elements as a mechanism for making character maps apply selectively to different parts of the result document, which will only cause frustration because it doesn't do that job very effectively. Admittedly there are some use cases for character maps - such as generating entity references in the output - that don't make sense within CDATA sections; but the answer to that is for users to avoid mixing the two facilities. Michael Kay
> which will only cause frustration because it doesn't do > that job very effectively. Why not? How else does one bypass the character mapping in selective cases, except by using disable-output-escaping="yes", which is depreciated. (As a side note, the serialization spec does not seem to actually support disable-output-escaping. Is this a problem?) Some History: In http://lists.w3.org/Archives/Member/w3c-xsl-wg/2004Jul/0022 the minutes state: > In passing, the editor also notes that the second sentence of phase 2 is > wrong: character mapping may affect characters that were affected by > creation of CDATA sections. ... But then in http://www.w3.org/XML/Group/xsl-query-specs/last-call-comments/xquery-serialization/issues.xml#qt-2004Feb0362-11 Henry does not seem to follow up on this. See also possibly http://lists.w3.org/Archives/Member/w3c-xsl-wg/2003Mar/0066
Resolved not to take action in 2005-04-28 telcon. (see minutes for discussion)