W3C home > Mailing lists > Public > public-qt-comments@w3.org > September 2015

[Bug 29007] json-to-xml definition is inconsistent with construction from PSVI

From: <bugzilla@jessica.w3.org>
Date: Wed, 02 Sep 2015 17:29:58 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29007-523-b85r1ztsYj@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29007

--- Comment #2 from Michael Kay <mike@saxonica.com> ---
To implement the decision, I propose to change the paragraph

The XDM tree returned by the function does not contain any unnecessary (albeit
valid) nodes such as whitespace text nodes, comments, or processing
instructions, or attributes (escaped and escaped-key) whose value is equal to
the default value (false). It does not include any whitespace in the value of
number or boolean element nodes.

to read:

The XDM tree returned by the function does not contain any unnecessary (albeit
valid) nodes such as whitespace text nodes, comments, or processing
instructions. It does not include any whitespace in the value of number or
boolean element nodes, or in the values of the *escaped* and *escaped-key*
attribute nodes. 

If the result is typed, every element named *string* will have an attribute
named *escaped* whose value is either "true" or "false", and every element
having an attribute named *key* will also have an attribute named *escaped-key*
whose value is either "true" or "false".

If the result is untyped, the attributes *escaped* and *escaped-key* will never
be present with the value "false". (In cases where the value false would be
appropriate, the attribute will be absent). 

The changes have been applied.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 2 September 2015 17:30:09 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 2 September 2015 17:30:10 UTC