W3C home > Mailing lists > Public > public-qt-comments@w3.org > July 2007

[Bug 4845] Do we need an error for "]]>" in replacement text?

From: <bugzilla@wiggum.w3.org>
Date: Tue, 10 Jul 2007 22:54:53 +0000
To: public-qt-comments@w3.org
Message-Id: <E1I8Obd-0001gt-Ep@wiggum.w3.org>


           Summary: Do we need an error for "]]>" in replacement text?
           Product: XPath / XQuery / XSLT
           Version: Working drafts
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Update Facility
        AssignedTo: andrew.eisenberg@us.ibm.com
        ReportedBy: chamberl@almaden.ibm.com
         QAContact: public-qt-comments@w3.org

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 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

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.

Don Chamberlin
Received on Tuesday, 10 July 2007 22:54:57 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:19 UTC