1344 2005-05-11 03:20:43 +0000 make prohibited characters explizit 2005-06-27 00:20:15 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XQueryX 1.0 Last Call drafts PC Windows XP CLOSED INVALID P2 normal --- 1 fsasaki jim.melton public-qt-comments oldest_to_newest 3476 0 fsasaki 2005-05-11 03:20:43 +0000 http://www.w3.org/International/2005/02/xqueryx-review.html Comment: 3477 1 fsasaki 2005-05-11 03:22:20 +0000 http://www.w3.org/International/2005/02/xqueryx-review.html Comment: 1 3191 2 fsasaki 2005-05-18 18:58:50 +0000 (In reply to comment #0) > http://www.w3.org/International/2005/02/xqueryx-review.html Comment: "If the XQuery contains characters that are prohibited in XML text (such as < and &), they must be "escaped" as either character entity references or character references." It should be made clear what is meant my "prohibited in XML text", e.g. XML-predefined entities. 2971 3 fsasaki 2005-05-30 08:32:57 +0000 (In reply to comment #2) > (In reply to comment #0) > > http://www.w3.org/International/2005/02/xqueryx-review.html Comment: > > "If the XQuery contains characters that are prohibited in XML text (such as < > and &), they must be "escaped" as either character entity references or > character references." It should be made clear what is meant my "prohibited in > XML text", e.g. XML-predefined entities. consensus of the i18n-core-wg, telecon 27 may 2005: closed. 3012 4 jim.melton 2005-06-02 20:57:30 +0000 Even though this comment has been marked RESOLVED INVALID, the Working Group agrees that some clarification in the text of the XQueryX specification, along the lines of your suggestion, is justified. We will undertake to make an appropriate clarification editorially. Assuming that you agree with this resolution of your issue, it would be appropriate for you to change the Status of the issue to CLOSED. If you do not mark the issue as CLOSED and do not re-open the issue witin two (2) weeks, we will assume that we can mark it CLOSED.