W3C home > Mailing lists > Public > public-xformsusers@w3.org > February 2017

Re: JSON content

From: Steven Pemberton <steven.pemberton@cwi.nl>
Date: Tue, 14 Feb 2017 21:19:55 +0100
To: "public-xformsusers@w3.org" <public-xformsusers@w3.org>, "Erik Bruchez" <erik@bruchez.org>
Message-ID: <op.yvn2rhd8smjzpq@steven-xps>
So I fixed this. In fact we were pretty vague about it already; although  
we point to rfc4627.txt (which specifies the application/json mediatype),  
it is only a non-normative reference. I added a link to the IANA list of  
mediatypes, also non-normatively.

Otherwise we only say "When an XForms Processor receives a JSON value".

There is one other place where we specifically mention application/json,  
but that is for the serialize attribute of <submission/>, and you can use  
@mediatype on that element to specify the actual mediatype to use.


On Fri, 03 Feb 2017 23:16:45 +0100, Erik Bruchez <erik@bruchez.org> wrote:

> All,
> The spec says "When an XForms Processor receives a JSON value" and  
> points to RFC 4627, which establishes >the application/json media type.
>> In practice we have seen that, like for XML, there are some other media  
>> types in use for JSON, including >using the `+json` suffix. In fact,  
>> many `+json` media types are registered at IANA [1].
>> We might want to clarify what "receiv[ing] a JSON value" means more  
>> precisely (or leave it open).
>> -Erik
>> [1] http://www.iana.org/assignments/media-types/media-types.xhtml
Received on Tuesday, 14 February 2017 20:20:36 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:37:47 UTC