W3C home > Mailing lists > Public > public-exi@w3.org > October 2015

Re: JSON Schema

From: Michael Kay <mike@saxonica.com>
Date: Thu, 1 Oct 2015 15:04:01 +0100
Cc: "public-xsl-wg@w3.org" <public-xsl-wg@w3.org>, "public-exi@w3.org" <public-exi@w3.org>
Message-Id: <6098A7E9-0ED7-4844-B629-ED0FFBA0B0C8@saxonica.com>
To: "Peintner, Daniel (ext)" <daniel.peintner.ext@siemens.com>, Public Joint XSLT XQuery XPath <public-xsl-query@w3.org>
I am forwarding this to the mailing list for the joint XQuery/XSLT activity since the JSON-to-XML mapping has now found its way into XPath 3.1 and is therefore the joint responsibility of both groups.

Michael Kay
Saxonica


> On 1 Oct 2015, at 14:52, Peintner, Daniel (ext) <daniel.peintner.ext@siemens.com> wrote:
> 
> Hi XSLT folks,
> 
> I am getting in touch with you on behalf of the EXI working group.
> 
> In the recent past we have been analyzing various ways to support JSON data in EXI. One straight-forward approach is to map JSON data to XML [1] by making use of an XML Schema [2] just like XSLT 3.0 does.
> 
> In the ideal case we could just use this schema "as is". However, we have been studying the schema [2] and would like to propose an extension so that EXI can make use of its datatype representations (i.e., represent dateTime values like "2014-02-04T18:50:45" more appropriately [3] than just as String).
> 
> Attached a diffed version of our proposed changes (see diff.htm). The HTML shows in orange the changes. On the left hand side one can see the original and the right hand side there is the updated XSD.
> 
> Please let me walk through the proposed changes and/or comments.
> 
> (*) The three orange sections are about the element "other" and its type "otherType". This opens for EXI the possibility to use specific type-codecs for certain values. e.g., one can use the base64Binary element to encode binary data instead of xs:string or integer values encoded as integers and not as xs:double et cetera.
> 
> (*) The attributes "escaped" and "escaped-key" are XSLT specific and not necessary for EXI but do not hurt either.
> 
> I personally think these changes are important to have an optimal and easy EXI encoding and I also think we should avoid having different schemas.
> Hence we would like to start discussing these issues with you to get further feedback.
> 
> Thanks,
> 
> -- Daniel
> 
> [1] http://www.w3.org/TR/xslt-30/#json
> [2] http://www.w3.org/TR/xslt-30/schema-for-json.xsd
> [3] http://www.w3.org/TR/exi/#encodingDateTime
> <diff.htm>
Received on Thursday, 1 October 2015 14:04:38 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 1 October 2015 14:04:38 UTC