Re: [apps-discuss] JSON Patch name
"Manger, James H" <James.H.Manger@team.telstra.com> Wed, 23 January 2013 21:54 UTC
Return-Path: <James.H.Manger@team.telstra.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D721D21F87EE for <apps-discuss@ietfa.amsl.com>; Wed, 23 Jan 2013 13:54:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.901
X-Spam-Level:
X-Spam-Status: No, score=-0.901 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, RELAY_IS_203=0.994]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iRpmGHkDOVKg for <apps-discuss@ietfa.amsl.com>; Wed, 23 Jan 2013 13:54:11 -0800 (PST)
Received: from ipxavo.tcif.telstra.com.au (ipxavo.tcif.telstra.com.au [203.35.135.200]) by ietfa.amsl.com (Postfix) with ESMTP id 08E2721F87ED for <apps-discuss@ietf.org>; Wed, 23 Jan 2013 13:54:09 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.84,524,1355058000"; d="scan'208";a="114239579"
Received: from unknown (HELO ipcdvi.tcif.telstra.com.au) ([10.97.217.212]) by ipoavi.tcif.telstra.com.au with ESMTP; 24 Jan 2013 08:54:07 +1100
X-IronPort-AV: E=McAfee;i="5400,1158,6964"; a="107659400"
Received: from wsmsg3751.srv.dir.telstra.com ([172.49.40.172]) by ipcdvi.tcif.telstra.com.au with ESMTP; 24 Jan 2013 08:54:06 +1100
Received: from WSMSG3153V.srv.dir.telstra.com ([172.49.40.159]) by WSMSG3751.srv.dir.telstra.com ([172.49.40.172]) with mapi; Thu, 24 Jan 2013 08:54:06 +1100
From: "Manger, James H" <James.H.Manger@team.telstra.com>
To: "barryleiba@computer.org" <barryleiba@computer.org>
Date: Thu, 24 Jan 2013 08:54:05 +1100
Thread-Topic: [apps-discuss] JSON Patch name
Thread-Index: Ac35gLf4ztlPm7+uSF+EKlME8dLLfQAM3G1X
Message-ID: <EC987577-EC01-4BF3-A67A-145D48A4AAF3@team.telstra.com>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US, en-AU
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "apps-discuss@ietf.org" <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] JSON Patch name
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Jan 2013 21:54:18 -0000
Ok. I don't object. -- James Manger ----- Reply message ----- From: "Barry Leiba" <barryleiba@computer.org> Date: Thu, Jan 24, 2013 2:45 am Subject: [apps-discuss] JSON Patch name To: "Julian Reschke" <julian.reschke@gmx.de> Cc: "Manger, James H" <James.H.Manger@team.telstra.com>, "apps-discuss@ietf.org" <apps-discuss@ietf.org> >>> Given the agreement posted so far to this, it sounds like that's an >>> acceptable way to go. Let me ask, then, for any objections to this >>> path, which will make the media type name "application/json- >>> patch+json". If you *object* to that change, post here very soon. I >>> will put it in as an editor note now. >> >> If we really want a +json suffix, just make it: >> application/patch+json >> >> Repeating "json" twice, with "-" and "+", just guarantees typos and >> confusion. > > I agree that this simpler, but wouldn't object to Barry's choice. Indeed, and what James wants is not an option -- it's exactly that discussion that had me initially say that we don't have consensus on where to go. The only options on the table for now, because of the late change, are these: 1. application/json-patch 2. application/json-patch+json I see strong consensus for (2), and am *only* asking for objections to that. You might prefer something else, but do you *object* to (2)? That's the only question. James, are you OK with (2), given that it's not your preference? [By the way: IANA made the registration for (2) yesterday: http://www.iana.org/assignments/media-types/application If we have to revert it because of objections here, we can.] Barry
- Re: [apps-discuss] JSON Patch name Ben Longden
- Re: [apps-discuss] JSON Patch name Julian Reschke
- Re: [apps-discuss] JSON Patch name Conal Tuohy
- Re: [apps-discuss] JSON Patch name Erik Wilde
- [apps-discuss] JSON Patch name Mark Nottingham
- Re: [apps-discuss] JSON Patch name Martin J. Dürst
- Re: [apps-discuss] JSON Patch name Mark Nottingham
- Re: [apps-discuss] JSON Patch name Cyrus Daboo
- Re: [apps-discuss] JSON Patch name James M Snell
- Re: [apps-discuss] JSON Patch name Barry Leiba
- Re: [apps-discuss] JSON Patch name Martin J. Dürst
- Re: [apps-discuss] JSON Patch name Erik Wilde
- Re: [apps-discuss] JSON Patch name Mark Nottingham
- Re: [apps-discuss] JSON Patch name Conal Tuohy
- Re: [apps-discuss] JSON Patch name Erik Wilde
- Re: [apps-discuss] JSON Patch name Barry Leiba
- Re: [apps-discuss] JSON Patch name Conal Tuohy
- Re: [apps-discuss] JSON Patch name Martin J. Dürst
- Re: [apps-discuss] JSON Patch name stefan
- Re: [apps-discuss] JSON Patch name Julian Reschke
- Re: [apps-discuss] JSON Patch name Markus Lanthaler
- Re: [apps-discuss] JSON Patch name Barry Leiba
- Re: [apps-discuss] JSON Patch name Manger, James H
- Re: [apps-discuss] JSON Patch name Julian Reschke
- Re: [apps-discuss] JSON Patch name Barry Leiba
- Re: [apps-discuss] JSON Patch name Manger, James H