- From: <bugzilla@jessica.w3.org>
- Date: Fri, 14 Nov 2014 21:59:48 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27330
Bug ID: 27330
Summary: Character Expansion
Product: XPath / XQuery / XSLT
Version: Recommendation
Hardware: PC
OS: All
Status: NEW
Severity: normal
Priority: P2
Component: Serialization 3.1
Assignee: cmsmcq@blackmesatech.com
Reporter: josh.spiegel@oracle.com
QA Contact: public-qt-comments@w3.org
Section 10, Character Maps, needs to be updated to account for JSON
"Character maps allow a specific character appearing in a text or attribute
node in the instance of the data ..."
"... that actually appear in a text or attribute node in the instance ..."
"... in the use-character-maps in text nodes and attribute values are replaced
..."
This text now applies to strings as well as nodes.
--
In section 4, phases of serialization, bullet 3, I believe the intent is that
character expansion occurs for values that will be output as JSON strings (not
just strings). For example, if the output contains a QName, this won't be
subject to character expansion yet it will still be output as a JSON string.
Is this really the intent?
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Friday, 14 November 2014 21:59:49 UTC