4845 2007-07-10 22:54:53 +0000 Do we need an error for "]]>" in replacement text? 2007-07-31 20:55:24 +0000 1 1 1 Unclassified XPath / XQuery / XSLT Update Facility Working drafts PC Windows XP CLOSED INVALID P2 normal --- 1 chamberl andrew.eisenberg public-qt-comments oldest_to_newest 15770 0 chamberl 2007-07-10 22:54:53 +0000 In http://lists.w3.org/Archives/Member/w3c-xml-query-wg/2007May/0044.html, Mohamed Zergaoui suggested several changes to the update spec, labeled "Editorial". All but one of the changes are indeed editorial and I will implement them. But I think one of the changes deserves the attention of the working group. Here it is: In 2.4.3.2 Replacing the Value of a Node [[ If $target is a comment node, and $string contains two adjacent hyphens or ends with a hyphen, a dynamic error is raised [err:XQDY0072]. If $target is a processing instruction node, and $string contains the substring "?>", a dynamic error is raised [err:XQDY0026]. ]] The case of -- in comment and "?>" has been taken into account. But what about "]]>" everywhere in the content ? I request that the working group consider this issue at a future meeting. Regards, Don Chamberlin 15771 1 davidc 2007-07-10 23:16:24 +0000 I think that unlike the -- in comments case the ]]> restriction isn't a restriction on values in the data model, so shouldn't concern update, it's just that an xml serialisation needs to serialise ]]> as ]]> or some such. David 15779 2 mike 2007-07-11 10:24:58 +0000 Agree with David C. There's no problem having a text or attribute node with ']]>' in it. 15993 3 chamberl 2007-07-31 20:55:10 +0000 On July 31, 2007, the Query working group decided to close this bug report with no change to the specifications. The string "]]>" is valid as text content in the XQuery Data Model. When a Data Model instance containing this string is serialized, the string will be escaped appropriately. --Don Chamberlin (for the Query working group)