27930 2015-01-30 10:19:01 +0000 [fo31] Missing error condition for parse-json 2015-03-11 21:27:59 +0000 1 1 1 Unclassified XPath / XQuery / XSLT Functions and Operators 3.1 Candidate Recommendation PC All CLOSED FIXED P2 normal --- 1 mike mike christian.gruen public-qt-comments oldest_to_newest 117619 0 mike 2015-01-30 10:19:01 +0000 The spec of parse-json does not define an error code to raise if an option is present with an incorrect value, e.g. 'liberal':'maybe'. I propose to use FOJS0004. The error code FOJS0002 appears in the appendix but is not used (the condition it describes is no longer an error). The table of options is a little inconsistent in its presentation. For some options it uses a bold "must" to say what the value must be; for some options it is explicit about the default. I propose to use "must", and describe the default, for all three options. 117641 1 christian.gruen 2015-01-31 18:45:41 +0000 > I propose to use FOJS0004. I would suggest to use a general code for invalid map arguments. In EXPath (and many of our own modules), we decided to raise the existing code FORG0006 whenever the type of an argument, or the key or value of a map argument, is invalid. FORG0006 is also raised by fn:boolean, fn:sum, and some other functions. 117667 2 mike 2015-02-03 16:20:25 +0000 The WG agreed to fix the bug as suggested. 117819 3 mike 2015-02-10 17:20:57 +0000 The change has been applied. 118532 4 mike 2015-03-11 21:27:59 +0000 In my efforts to converge the specifications of the various JSON-related functions, this code changed to FOJS0005.