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

Re: JSON content

From: Erik Bruchez <erik@bruchez.org>
Date: Tue, 14 Feb 2017 13:07:05 -0800
Message-ID: <CAAc0PEUZ+FqkSbjG8B6RhcA_quGKMK6k2mhhFdcsepOGB=03BA@mail.gmail.com>
To: Steven Pemberton <steven.pemberton@cwi.nl>
Cc: "public-xformsusers@w3.org" <public-xformsusers@w3.org>
Good, that works for me.

-Erik

On Tue, Feb 14, 2017 at 12:19 PM, Steven Pemberton <steven.pemberton@cwi.nl>
wrote:

> 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.
>
> Steven
>
>
> 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 21:07:59 UTC

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