IETF Logo Mail Archive

Re: [apps-discuss] JSON Patch name

Erik Wilde <dret@berkeley.edu> Fri, 18 January 2013 12:43 UTC

Return-Path: <dret@berkeley.edu>
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 8837C21F889A for <apps-discuss@ietfa.amsl.com>; Fri, 18 Jan 2013 04:43:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 1FaUdURODQ0f for <apps-discuss@ietfa.amsl.com>; Fri, 18 Jan 2013 04:43:52 -0800 (PST)
Received: from cm02fe.IST.Berkeley.EDU (cm02fe.IST.Berkeley.EDU [169.229.218.143]) by ietfa.amsl.com (Postfix) with ESMTP id 2851B21F874F for <apps-discuss@ietf.org>; Fri, 18 Jan 2013 04:43:42 -0800 (PST)
Received: from 46-126-158-51.dynamic.hispeed.ch ([46.126.158.51] helo=dretair.local) by cm02fe.ist.berkeley.edu with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.76) (auth plain:dret@berkeley.edu) (envelope-from <dret@berkeley.edu>) id 1TwBIJ-0004zD-7Z; Fri, 18 Jan 2013 04:43:42 -0800
Message-ID: <50F94379.1060005@berkeley.edu>
Date: Fri, 18 Jan 2013 13:43:37 +0100
From: Erik Wilde <dret@berkeley.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: apps-discuss@ietf.org
References: <030009EF-15AD-4CAC-B2BF-036936FC68FD@mnot.net> <50F92A6D.1030105@it.aoyama.ac.jp> <16C16775-CCE9-4010-9566-A0D24480665B@mnot.net> <50F941B8.40009@versi.edu.au>
In-Reply-To: <50F941B8.40009@versi.edu.au>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
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: Fri, 18 Jan 2013 12:43:53 -0000

hello.

On 2013-01-18 13:36 , Conal Tuohy wrote:
> On 18/01/13 20:59, Mark Nottingham wrote:
>> On 18/01/2013, at 9:56 PM, "Martin J. Dürst"<duerst@it.aoyama.ac.jp>  wrote:
>>> Shouldn't the name end in +json, because the patch data itself is JSON?
>> The answer we've come to is that it isn't, because the important bit is that this is a patch format *for* JSON; the fact that it's encoded in JSON is (relatively) insignificant.
> I agree with Martin, that the Internet Media Type name should end in
> "+json".
> It's true that in an obvious sense the semantics of JSON Patch documents
> are more significant that their syntax, but I don't think that has any
> bearing on whether to use the "+json" suffix or not.

+1, and fwiw, http://tools.ietf.org/html/draft-wilde-xml-patch-01 now 
has changed from application/xml-patch to application/xml-patch+xml, 
because according to 
http://tools.ietf.org/id/draft-ietf-appsawg-media-type-suffix-regs-08.txt, 
media types should use the suffix, unless there's a good reason not to.

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 |

v2.23.0 | Report a Bug | By Email