IETF Logo Mail Archive

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

"Joe Hildebrand (jhildebr)" <jhildebr@cisco.com> Sat, 05 July 2014 01:30 UTC

Return-Path: <jhildebr@cisco.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 4FC7B1A0011 for <json@ietfa.amsl.com>; Fri, 4 Jul 2014 18:30:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.152
X-Spam-Level:
X-Spam-Status: No, score=-15.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 AXwAOvni5lmo for <json@ietfa.amsl.com>; Fri, 4 Jul 2014 18:30:37 -0700 (PDT)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2AA3F1A0118 for <json@ietf.org>; Fri, 4 Jul 2014 18:30:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2168; q=dns/txt; s=iport; t=1404523836; x=1405733436; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=xoxOk6Iuldlg0QgAXoId3lvJ21JWuopwMBScQYFJPxU=; b=GNVXnKW8qQmZWii1CHgw01xUnl9a/oxjAonWGlEh4q3qD+N5Uw/wjOoH h7WEMWheM7F/uc0i8+RXVvH016aamCE/a5UOFTvrytz60iblBvRxiqYYv IPT1P8YKB82/xXRQjP8PqI2PTTZ54WIjePJ2OL1MtQNvABb36f42Wlk4t A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjwFADBUt1OtJA2I/2dsb2JhbABagw5SWoJvu32HPwEZbhZ1hAMBAQEEAQEBIBE6CxACAQgOCgICJgICAiULFRACBAENBYhCDa81mm4TBIEsjXYHgneBTAWadpQMg0OCMA
X-IronPort-AV: E=Sophos;i="5.01,605,1400025600"; d="scan'208";a="58432248"
Received: from alln-core-3.cisco.com ([173.36.13.136]) by alln-iport-6.cisco.com with ESMTP; 05 Jul 2014 01:30:34 +0000
Received: from xhc-aln-x01.cisco.com (xhc-aln-x01.cisco.com [173.36.12.75]) by alln-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s651UYdH013420 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 5 Jul 2014 01:30:34 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.102]) by xhc-aln-x01.cisco.com ([173.36.12.75]) with mapi id 14.03.0123.003; Fri, 4 Jul 2014 20:30:34 -0500
From: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
To: Mark Baker <distobj@acm.org>, Tim Bray <tbray@textuality.com>
Thread-Topic: [Json] Media types, extensibility in draft-ietf-json-i-json-02
Thread-Index: AQHPli3TeLKmyOx7w0yav7qrcKonZpuQpE0A
Date: Sat, 05 Jul 2014 01:30:34 +0000
Message-ID: <CFDCB00F.52A7B%jhildebr@cisco.com>
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>
In-Reply-To: <CALcoZioTakxzkuvrt1EgNAKS==NNskWJ1TLUjxtZ1TBGPD+EXw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.4.3.140616
x-originating-ip: [10.82.224.80]
Content-Type: text/plain; charset="utf-8"
Content-ID: <FC6F0B5967CE984BBEEC4AD910AAB1AE@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/json/5K8xY_o5ZOSfATEj1HCEOZ-oKy8
Cc: Phillip Hallam-Baker <ietf@hallambaker.com>, JSON WG <json@ietf.org>
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: Sat, 05 Jul 2014 01:30:44 -0000

There are times when, in the documentation for a service that is producing
JSON, I would like to say:

"If you receive a message from me that is not strictly I-JSON, I would
prefer you treat it as an error on my part, and therefore treat my message
as invalid, because if something went wrong enough that what I sent you
wasn't valid I-JSON my server room is likely on fire."


On 7/2/14, 1:42 PM, "Mark Baker" <distobj@acm.org> wrote:

>On Wed, Jul 2, 2014 at 11:54 AM, Tim Bray <tbray@textuality.com> wrote:
>> I’ll say that just on Web-architectural grounds, I think distinct data
>> formats should have distinct Internet Media Types, and so it bothers me
>>that
>> we don’t have one for i-json.  But the WG couldn’t perceive any real
>>value
>> in having one that’s distinct from JSON’s and I didn’t have  a
>> forceful-enough argument to move the consensus on this.
>
>Were there driving use cases behind I-JSON? I could imagine a
>(atypical) scenario where it's used as a "publishing profile",
>defining a best practice for publishers (Postel-ian style), with no
>regard for what happens once it's consumed. You wouldn't need to say
>anything about media types then.
>
>But if you want to be able to exchange I-JSON over the Web or
>Internet, so that recipients know, e.g., not to add duplicate keys,
>then that can only practically be indicated with a new media type.
>
>_______________________________________________
>json mailing list
>json@ietf.org
>https://www.ietf.org/mailman/listinfo/json
>


-- 
Joe Hildebrand

v2.37.1 | Report a Bug | By Email | System Status