IETF Logo Mail Archive

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

Larry Masinter <masinter@adobe.com> Sat, 05 July 2014 07:03 UTC

Return-Path: <masinter@adobe.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 6B5051A035D for <json@ietfa.amsl.com>; Sat, 5 Jul 2014 00:03:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001] 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 8yz3Hn3nZyit for <json@ietfa.amsl.com>; Sat, 5 Jul 2014 00:03:02 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1blp0188.outbound.protection.outlook.com [207.46.163.188]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 523651A035C for <json@ietf.org>; Sat, 5 Jul 2014 00:03:02 -0700 (PDT)
Received: from BL2PR02MB307.namprd02.prod.outlook.com (10.141.91.21) by BL2PR02MB308.namprd02.prod.outlook.com (10.141.91.24) with Microsoft SMTP Server (TLS) id 15.0.954.9; Sat, 5 Jul 2014 07:03:00 +0000
Received: from BL2PR02MB307.namprd02.prod.outlook.com ([10.141.91.21]) by BL2PR02MB307.namprd02.prod.outlook.com ([10.141.91.21]) with mapi id 15.00.0980.000; Sat, 5 Jul 2014 07:03:00 +0000
From: Larry Masinter <masinter@adobe.com>
To: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>, 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: AQHPlf/UPrUNrMCeDkWqzE2zLswAjpuM2y2AgAAUwoCAAD+5gIADhcYAgABZSgA=
Date: Sat, 05 Jul 2014 07:02:58 +0000
Message-ID: <3b407fff0cc14d5ba291cea58bacac4f@BL2PR02MB307.namprd02.prod.outlook.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> <CFDCB00F.52A7B%jhildebr@cisco.com>
In-Reply-To: <CFDCB00F.52A7B%jhildebr@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [50.184.24.49]
x-microsoft-antispam: BL:0; ACTION:Default; RISK:Low; SCL:0; SPMLVL:NotSpam; PCL:0; RULEID:
x-forefront-prvs: 02638D901B
x-forefront-antispam-report: SFV:NSPM; SFS:(6009001)(189002)(199002)(107046002)(46102001)(106116001)(99396002)(95666004)(50986999)(76176999)(21056001)(4396001)(85306003)(20776003)(77982001)(2656002)(33646001)(87936001)(106356001)(76576001)(85852003)(74316001)(76482001)(101416001)(74502001)(74662001)(86362001)(81542001)(93886003)(31966008)(83322001)(80022001)(66066001)(92566001)(54356999)(99286002)(83072002)(81342001)(79102001)(105586002)(64706001)(108616002)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:BL2PR02MB308; H:BL2PR02MB307.namprd02.prod.outlook.com; FPR:; MLV:sfv; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: adobe.com
Archived-At: http://mailarchive.ietf.org/arch/msg/json/JT7xnDOqnDXRKsbYKMt9CPZCLUY
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 07:03:04 -0000

There is an advantage to using application/json for I-JSON
because many components can/should treat I-JSON as
JSON.  So there actually should be a use case which
NEEDS the distinction.

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."

In this particular case, I can't think of a situation
where you wouldn't also want to validate other constraints
as well.

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