W3C home > Mailing lists > Public > public-qt-comments@w3.org > August 2016

[Bug 29785] New: [FO31] 17.5.4 fn:xml-to-json

From: <bugzilla@jessica.w3.org>
Date: Fri, 19 Aug 2016 07:33:14 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29785-523@http.www.w3.org/Bugs/Public/>

            Bug ID: 29785
           Summary: [FO31] 17.5.4 fn:xml-to-json
           Product: XPath / XQuery / XSLT
           Version: Candidate Recommendation
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Functions and Operators 3.1
          Assignee: mike@saxonica.com
          Reporter: tim@cbcl.co.uk
        QA Contact: public-qt-comments@w3.org
  Target Milestone: ---

The specification says:

"An element node whose name matches the name of a global element declaration in
the schema given in C.2 Schema for the result of fn:json-to-xml, and whose
content after stripping all attributes (at any depth) in namespaces other than
http://www.w3.org/2005/xpath-functions is such that validation against the
schema given in C.2 Schema for the result of fn:json-to-xml would succeed."

Wouldn't stripping "all attributes (at any depth) in namespaces other than
http://www.w3.org/2005/xpath-functions" remove the attributes with no
namespace, such as "escaped", "key" and "escaped-key".

Also, under the three points given under

"The node supplied as $input must be one of the following: [err:FOJS0006]"

in what situations will (2) match where (1) would not (and vice versa)?

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Friday, 19 August 2016 07:33:22 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:58:01 UTC