W3C home > Mailing lists > Public > public-qt-comments@w3.org > May 2014

[Bug 23594] [xslt 3.0] new JSON specification

From: <bugzilla@jessica.w3.org>
Date: Wed, 07 May 2014 11:25:59 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-23594-523-uyga6RJPcz@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23594

Abel Braaksma <abel.braaksma@xs4all.nl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|CLOSED                      |REOPENED
                 CC|                            |abel.braaksma@xs4all.nl
         Resolution|FIXED                       |---

--- Comment #8 from Abel Braaksma <abel.braaksma@xs4all.nl> ---
I understand that we now don't support RFC4627 or ECMA-404 anymore, except as
an extension to liberal := yes.

Reopening, because there are still a few references left over that refer to the
"spec" option, or refer to the old specifications or old syntax. 

Summarizing:

Validate option:
"or against an implementation-defined schema if the spec option has the value
liberal."

should become:
"or against an implementation-defined schema if the liberal option has the
value yes.

Error [ERR XTDE3240] 
"It is a dynamic error if the value of $input does not conform to the JSON
grammar, as selected using the explicit or implicit spec option."

should become:
"It is a dynamic error if the value of $input does not conform to the JSON
grammar, as specified by [RFC7159], and when liberal is set to yes."

Error [ERR XTDE3260] 
'It is a dynamic error if the value of $options includes an entry whose key is
"spec" and whose value is not a single xs:string, or an entry whose key is
"validate" or "unescape" and whose value is not a single xs:boolean.'

should become:
'It is a dynamic error if the value of $options includes an entry whose key is
"liberal", "validate" or "unescape" and whose value is not a single xs:boolean,
or an entry "fallback" whose value is not a function item that conforms to
function(xs:string) as xs:string.'

Errors under E. Summary of Error conditions have the same texts, currently.

Notes:
The paragraph "ECMA-404 differs from RFC 4627 in two respects: [...] array."
can be removed.

The paragraph "Many JSON implementations allow commas [...] Representation of
JSON." should be revised or removed.

Examples:
Example "The expression json-to-xml('"abcd"', map{'spec': 'RFC4627'}) [...] not
a string.)." should be removed or revised.

Example "The expression json-to-xml('"abcd"', map{'spec': 'ECMA-404'})[...]
abcd</string>." should be removed or revised.

Example: the last example, right under "The following example illustrates ..."
contains the "spec" option, this should be revised.

Normative references
The text of the link contains "4627", while the link was updated to refer to
7159: "IETF. The JavaScript Object Notation (JSON) Data Interchange Format.
July 2006. See http://www.ietf.org/rfc/rfc4627.txt"

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 7 May 2014 11:26:01 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:56 UTC