1220 2005-04-06 21:12:12 +0000 Serialization - choice of quotes on attributes 2005-08-17 14:57:12 +0000 1 1 1 Unclassified XPath / XQuery / XSLT Serialization 1.0 Last Call drafts PC Windows XP CLOSED FIXED P2 normal --- 1 mike scott_boag public-qt-comments oldest_to_newest 3815 0 mike 2005-04-06 21:12:12 +0000 In serialization section 4, phase 2f states: If a quote (") character is in an attribute, and the attribute is delimited by quote, the character will be changed to an an apostrophe ('). Likewise, if a apostrophe (') character is in an attribute, and the attribute is delimited by apostrophe, the character will be changed to an an quote ("). I'm sure the intention here is to change the attribute delimiters, not the attribute value; but that's not how it reads. Change both occurrences of "the character will be changed" to "the delimiter will be changed". Add, for completeness. "If both characters are present in an attribute value, one of them will be escaped." 3821 1 scott_boag 2005-04-07 00:20:26 +0000 "Michael Rys" <mrys@microsoft.com> wrote: The intent as far as I understand XML serializers is to change the character and not the quotes (since you may write the quote before you have seen the full value of the attribute!). 3705 2 scott_boag 2005-04-28 16:19:43 +0000 from http://lists.w3.org/Archives/Member/w3c-xsl-wg/2005Apr/0030.html: MK reports: ' In serialization section 4, phase 2f states: If a quote (") character is in an attribute, and the attribute is delimited by quote, the character will be changed to an an apostrophe ('). Likewise, if a apostrophe (') character is in an attribute, and the attribute is delimited by apostrophe, the character will be changed to an an quote ("). I'm sure the intention here is to change the attribute delimiters, not the attribute value; but that's not how it reads. Change both occurrences of "the character will be changed" to "the delimiter will be changed". Add, for completeness. "If both characters are present in an attribute value, one of them will be escaped."' MK: Character map use case, want to give user more control. It is clear that we are referring to changing delimiters, not content, but this should be explicit. MR: Added comment saying that this really did refer to content rather than delimiters. Streaming output scenario. MK: Entitizing is fine, but doesn't work in character map use case where output is not XML. Joanne: Henry doesn't like this rule, would prefer parameter specifying which type of delimiter to use. MK: We can take this provision out of the spec, implementation is permitted to fix delimiters, but user doesn't have predictability. We should all agree that serializer can't change content except by escaping. PC: Proposal is to drop this paragraph entirely. Anders: Proposes change to SHOULD. PC: This used to say "should", we changed it to "will". Scott: Changed December 8. Karun, Joanne, MR agree to drop. RESOLUTION: " http://www.w3.org/Bugs/Public/show_bug.cgi?id=1220 Serialization - choice of quotes on attributes" is resolved. Offending paragraph will be deleted.