Re: [Json] Media types, extensibility in draft-ietf-json-i-json-02

Phillip Hallam-Baker <ietf@hallambaker.com> Mon, 07 July 2014 15:59 UTC

Return-Path: <hallam@gmail.com>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C0CB1A0305 for <json@ietfa.amsl.com>; Mon, 7 Jul 2014 08:59:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level:
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8D9j01S44dOa for <json@ietfa.amsl.com>; Mon, 7 Jul 2014 08:59:42 -0700 (PDT)
Received: from mail-wi0-x231.google.com (mail-wi0-x231.google.com [IPv6:2a00:1450:400c:c05::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C8C9D1A0266 for <json@ietf.org>; Mon, 7 Jul 2014 08:59:41 -0700 (PDT)
Received: by mail-wi0-f177.google.com with SMTP id r20so7174766wiv.4 for <json@ietf.org>; Mon, 07 Jul 2014 08:59:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=MAfTKvIc5kL62/74SUObpCGUMynDeGWqfd2ICz53gu8=; b=che37ieQQ9a7wgWuLLYhg9jWSZo+qFT+mxI92QGCtlMYTlcEWzSiOSi4pKSr60bzXK UPq7tXeYMrjNVopC8Cc0sUsSs6tqOp1gAv0ERZWQZCGy8Fmv46fysByiMa5bVNYTdW4b XmZH9n0HOk2OB1CqcF7N3ejvMAInH+2W9ESHEutMKBfdV0yIWR45NFV1WrVNZBG+iSLn IjX7/nC34kKZp4WDKf+y47vfg4BBvs7ccHqfoh6ya+QGqkkGdQ/an8mhKv2DyN5Kp9DE JExWTSFH6mB039lomSH+3HGaT89L1WoacFQY+A/WKTZYP4URWczqsPUMVr3tpf/aAG7L v9pQ==
MIME-Version: 1.0
X-Received: by 10.180.97.195 with SMTP id ec3mr38174301wib.13.1404748780362; Mon, 07 Jul 2014 08:59:40 -0700 (PDT)
Sender: hallam@gmail.com
Received: by 10.194.79.136 with HTTP; Mon, 7 Jul 2014 08:59:40 -0700 (PDT)
In-Reply-To: <53BAB379.3040506@berkeley.edu>
References: <CALcoZionwZ1gn0hkhq4sKcDKg3LK13+d-XvBzXUA4iHjS6PHNA@mail.gmail.com> <CAMm+LwgU5veinaNJ6ptLJ509QD3R5=LEbpfmNjZSy5C+8jfPXg@mail.gmail.com> <CAHBU6iuc2j4a5VYnrboMEMnAPxhs5i+iZxfpbfnN1oa3740TfQ@mail.gmail.com> <CALcoZioTakxzkuvrt1EgNAKS==NNskWJ1TLUjxtZ1TBGPD+EXw@mail.gmail.com> <CFDCB00F.52A7B%jhildebr@cisco.com> <3b407fff0cc14d5ba291cea58bacac4f@BL2PR02MB307.namprd02.prod.outlook.com> <CFDE30C2.52BE7%jhildebr@cisco.com> <CAHBU6itrQTvccZqTXDBo4MaK9Txu7gGfGh8mfS4Rmv73DwSXfQ@mail.gmail.com> <043801cf99f1$7165f8b0$5431ea10$@gmx.net> <53BAB379.3040506@berkeley.edu>
Date: Mon, 07 Jul 2014 11:59:40 -0400
X-Google-Sender-Auth: IZpbft9kLRJGYZWjoANKp8it9vo
Message-ID: <CAMm+Lwh5XFXqXxE2MwpLqcSZ4LUZ-6a1zO+Yz2duC5Gc_qntjw@mail.gmail.com>
From: Phillip Hallam-Baker <ietf@hallambaker.com>
To: Erik Wilde <dret@berkeley.edu>
Content-Type: multipart/alternative; boundary="f46d0443066e0d675d04fd9c9000"
Archived-At: http://mailarchive.ietf.org/arch/msg/json/aYlbWUodDWndyjaaPf8Zdob27lk
Cc: Mark Baker <distobj@acm.org>, Larry Masinter <masinter@adobe.com>, Tim Bray <tbray@textuality.com>, Joe Hildebrand <jhildebr@cisco.com>, JSON WG <json@ietf.org>, Markus Lanthaler <markus.lanthaler@gmx.net>
Subject: Re: [Json] Media types, extensibility in draft-ietf-json-i-json-02
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "JavaScript Object Notation \(JSON\) WG mailing list" <json.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/json>, <mailto:json-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/json/>
List-Post: <mailto:json@ietf.org>
List-Help: <mailto:json-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/json>, <mailto:json-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Jul 2014 15:59:43 -0000

Exactly

I-JSON is a subset of JSON.

We have two choices for I-Json content:

1) Use the content type application/json and not tell the application they
are getting I-JSON

2) Use the content type application/i-json and risk having parsers that
accept JSON but don't do special processing for I-JSON reject it.

I can't see any advantage to choice #2, it risks breaking things for a
distinction that does not provide leverage.


Now the story for JSON-B is completely different as that is a superset. So
even though a I-JSON document will be accepted by a JSON-B parser the
reverse is not the case as JSON-B has optional binary encodings. And so in
that case it is essential that the application know what the content type
is.









On Mon, Jul 7, 2014 at 10:49 AM, Erik Wilde <dret@berkeley.edu> wrote:

> hello markus.
>
>
> On 2014-07-07, 16:40, Markus Lanthaler wrote:
>
>> On Sunday, July 06, 2014 7:13 AM, Tim Bray wrote:
>>
>>> So, question: Is there anyone else who agrees with Mark's original
>>> argument that there ought to be a Media type for i-json. I wouldn't
>>> be wildly against it, but frankly can't see much of a practical upside.
>>>
>> I don't think it makes much sense to define a separate media type for
>> i-json and even less a media type suffix. It *might*, however, make sense
>> to mint a profile URI as defined by RFC6906 [1] for i-json and register it
>> according RFC7284 [2].
>>
>
> that would have made a lot of sense if JSON had chosen to support profiles
> in its recently published update, which it unfortunately didn't. i guess
> the problem now is that there is no agreed-upon way how profiles are
> signaled in JSON, which makes the profile mechanism only moderately useful.
> but i still agree that it would be useful to include such a profile URI for
> I-JSON in the spec, so that JSON-based formats that have an agreed-upon way
> of signaling profiles can use it.
>
> cheers,
>
> dret.
>
> --
> erik wilde | mailto:dret@berkeley.edu  -  tel:+1-510-2061079 |
>            | UC Berkeley  -  School of Information (ISchool) |
>            | http://dret.net/netdret http://twitter.com/dret |
>