Re: [Json] Media types, extensibility in draft-ietf-json-i-json-02
Mark Baker <distobj@acm.org> Sun, 06 July 2014 19:45 UTC
Return-Path: <mark@coactus.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 3789C1A0A84 for <json@ietfa.amsl.com>; Sun, 6 Jul 2014 12:45:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level:
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-0.7] 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 EM2anTBtmgIF for <json@ietfa.amsl.com>; Sun, 6 Jul 2014 12:45:31 -0700 (PDT)
Received: from mail-pa0-f50.google.com (mail-pa0-f50.google.com [209.85.220.50]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C306B1A03D8 for <json@ietf.org>; Sun, 6 Jul 2014 12:45:31 -0700 (PDT)
Received: by mail-pa0-f50.google.com with SMTP id bj1so4274264pad.37 for <json@ietf.org>; Sun, 06 Jul 2014 12:45:31 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=R6ilyaHLA+WA1pR08uMAEAxQmJR5FnyzsmrbrAfSi00=; b=cPQskt7F+mZTGiiv+hGgxJs838jmNetQA/UBY4RxlOgb0Q1yICSy8YtoQyzX8Sikg6 FkHHvD6sOFjjiDyI5xH5AMIHlPcrVXs8Yupd876ggcz2m+Ov+UYO0fJdO9YjoqtzSWie sEWyd7bOuor0c2436Rv9+CEGJIbR+zA/XsVXzJwNBWzxU6TKvynwwy5SISwQOU3ZlL9C CPOcOKGDYP3TLHASWn64Qs1Pk1tDHRCjLvw47GTmS12qJfOhlKwiXjbOZJFQJ5c0wy7j sH1vWscdrWDIuZJ9oL3XwPuTEd9tA13wRFYOc4WPDoM6npOqWjdYcDVJu5tw+lGy8F/w GOsg==
X-Gm-Message-State: ALoCoQmMhBM51X3p1pdThebaKYhITh9BNlrXX1LcSVpzen7JSMGOlQv2oVmW3hxZcHYsmkaAZCTv
MIME-Version: 1.0
X-Received: by 10.67.30.130 with SMTP id ke2mr24526026pad.44.1404675931296; Sun, 06 Jul 2014 12:45:31 -0700 (PDT)
Sender: mark@coactus.com
Received: by 10.70.91.108 with HTTP; Sun, 6 Jul 2014 12:45:31 -0700 (PDT)
X-Originating-IP: [192.0.216.13]
In-Reply-To: <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> <CFDCB00F.52A7B%jhildebr@cisco.com>
Date: Sun, 06 Jul 2014 15:45:31 -0400
X-Google-Sender-Auth: BqIBwYDt-hGs303xl7SdQF5CQT0
Message-ID: <CALcoZipXQKAJRtPB52rj0ZpstaPHRe5NVPKJFyFvWnxURtt6wQ@mail.gmail.com>
From: Mark Baker <distobj@acm.org>
To: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: http://mailarchive.ietf.org/arch/msg/json/ilDIdgx4AtW1__I_OrgVOm2Mk8w
Cc: Phillip Hallam-Baker <ietf@hallambaker.com>, Tim Bray <tbray@textuality.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: Sun, 06 Jul 2014 19:45:33 -0000
On Fri, Jul 4, 2014 at 9:30 PM, Joe Hildebrand (jhildebr) <jhildebr@cisco.com> wrote: > 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." Other than pre-arranging that with the human behind "you", the only existing way to achieve that goal is to use a new media type. Also, creating an I-JSON specific media type doesn't mean that I-JSON can't be delivered as application/json (or application/*+json). It just makes I-JSON useful in more situations IMO, like this one.
- [Json] Media types, extensibility in draft-ietf-j… Mark Baker
- Re: [Json] Media types, extensibility in draft-ie… Phillip Hallam-Baker
- Re: [Json] Media types, extensibility in draft-ie… Tim Bray
- Re: [Json] Media types, extensibility in draft-ie… John Cowan
- Re: [Json] Media types, extensibility in draft-ie… Mark Baker
- Re: [Json] Media types, extensibility in draft-ie… Joe Hildebrand (jhildebr)
- Re: [Json] Media types, extensibility in draft-ie… Tim Bray
- Re: [Json] Media types, extensibility in draft-ie… Joe Hildebrand (jhildebr)
- Re: [Json] Media types, extensibility in draft-ie… Larry Masinter
- Re: [Json] Media types, extensibility in draft-ie… Joe Hildebrand (jhildebr)
- Re: [Json] Media types, extensibility in draft-ie… Tim Bray
- Re: [Json] Media types, extensibility in draft-ie… Mark Baker
- Re: [Json] Media types, extensibility in draft-ie… Nico Williams
- Re: [Json] Media types, extensibility in draft-ie… Martin J. Dürst
- Re: [Json] Media types, extensibility in draft-ie… Markus Lanthaler
- Re: [Json] Media types, extensibility in draft-ie… Erik Wilde
- Re: [Json] Media types, extensibility in draft-ie… Mark Baker
- Re: [Json] Media types, extensibility in draft-ie… Markus Lanthaler
- Re: [Json] Media types, extensibility in draft-ie… mike amundsen
- Re: [Json] Media types, extensibility in draft-ie… Phillip Hallam-Baker
- Re: [Json] Media types, extensibility in draft-ie… Joe Hildebrand (jhildebr)
- Re: [Json] Media types, extensibility in draft-ie… Erik Wilde
- Re: [Json] Media types, extensibility in draft-ie… Larry Masinter