Re: [apps-discuss] media type for partial JSON updates?

Julian Reschke <julian.reschke@gmx.de> Fri, 30 December 2011 08:29 UTC

Return-Path: <julian.reschke@gmx.de>
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 2A32D21F8531 for <apps-discuss@ietfa.amsl.com>; Fri, 30 Dec 2011 00:29:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.539
X-Spam-Level:
X-Spam-Status: No, score=-103.539 tagged_above=-999 required=5 tests=[AWL=-0.940, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qjrkhYXQtKKw for <apps-discuss@ietfa.amsl.com>; Fri, 30 Dec 2011 00:29:48 -0800 (PST)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id 11EB221F84ED for <apps-discuss@ietf.org>; Fri, 30 Dec 2011 00:29:47 -0800 (PST)
Received: (qmail invoked by alias); 30 Dec 2011 08:29:46 -0000
Received: from p3EE2751C.dip.t-dialin.net (EHLO [192.168.178.36]) [62.226.117.28] by mail.gmx.net (mp058) with SMTP; 30 Dec 2011 09:29:46 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1/MLAEGIYTMfGaSvbrl2kCQKnH732SZRTmHtdR7PB kXAK8z5t4stoXZ
Message-ID: <4EFD7678.5080005@gmx.de>
Date: Fri, 30 Dec 2011 09:29:44 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: "Paul C. Bryan" <paul.bryan@forgerock.com>
References: <4EFC8C98.10901@gmx.de> <CAPW_8m7oLLLVkinrjEdUvtZYjUDM5V9HVtVH_HnhNOBGixHfAQ@mail.gmail.com> <4EFC994C.7080307@gmx.de> <CAPW_8m4OJtyHiu5rM6iw37OG=N3QjPuPccCmBCs0vRsNa8_H1w@mail.gmail.com> <4EFC9E9B.2040303@gmx.de> <1325223414.18477.31.camel@neutron>
In-Reply-To: <1325223414.18477.31.camel@neutron>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: IETF Apps Discuss <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] media type for partial JSON updates?
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, 30 Dec 2011 08:29:49 -0000

On 2011-12-30 06:36, Paul C. Bryan wrote:
> ...
>> I think it would be simpler to define it as something that can be
>> trivially transformed to the format defined in
>> https://tools.ietf.org/html/draft-pbryan-json-patch-04; in that case we
>> wouldn't even need to describe the actual semantics...
>
> Is this something that just reduces the verbosity of the operations, or
> are you talking something probably non-JSON for higher compactness? If
> the former, then I'm game to either choose shorter operation names or at
> least allow for aliases.

I personally don't think yet another format is needed.

But: people are doing this already with PUT (although they should not), 
and it might me good to offer them a way to fix what they do by 
switching PUT to PATCH and application/json to something that actually 
describes the semantics of what they are doing.

> ...

Best regards, Julian