This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 1344 - make prohibited characters explizit
Summary: make prohibited characters explizit
Status: CLOSED INVALID
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XQueryX 1.0 (show other bugs)
Version: Last Call drafts
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Jim Melton
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-05-11 03:20 UTC by Felix Sasaki
Modified: 2005-06-27 00:20 UTC (History)
0 users

See Also:


Attachments

Description Felix Sasaki 2005-05-11 03:20:43 UTC
http://www.w3.org/International/2005/02/xqueryx-review.html Comment:
Comment 1 Felix Sasaki 2005-05-11 03:22:20 UTC
http://www.w3.org/International/2005/02/xqueryx-review.html Comment: 1
Comment 2 Felix Sasaki 2005-05-18 18:58:50 UTC
(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.
Comment 3 Felix Sasaki 2005-05-30 08:32:57 UTC
(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.
Comment 4 Jim Melton 2005-06-02 20:57:30 UTC
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.