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

[Bug 28836] New: fn:parse-json, fallback function

From: <bugzilla@jessica.w3.org>
Date: Mon, 22 Jun 2015 12:33:49 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-28836-523@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28836

            Bug ID: 28836
           Summary: fn:parse-json, fallback function
           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: christian.gruen@gmail.com
        QA Contact: public-qt-comments@w3.org

In the current spec, the fallback function of fn:parse-json is defined to have
the function signature "function(xs:string) as xs:string". In the given
example, however...

  parse-json('{"x":"\\", "y":"\u0000"}',
map{'fallback':function($s){'['||$s||']'}})

...the function is only of type `function(*)` (because the type are not
explicitly stated), and it can only be determined at runtime if the passed on
and returned item is of type xs:string (or a value that can be promoted to
xs:string).

Maybe the correct solution (albeit not so nice to read) would be to specify
"function(*)" as type, and require the function to only accept and return
strings?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Monday, 22 June 2015 12:33:52 UTC

This archive was generated by hypermail 2.3.1 : Monday, 22 June 2015 12:33:52 UTC