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

Julian Reschke <julian.reschke@gmx.de> Thu, 29 December 2011 16:46 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 85A5821F8A55 for <apps-discuss@ietfa.amsl.com>; Thu, 29 Dec 2011 08:46:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.999
X-Spam-Level:
X-Spam-Status: No, score=-104.999 tagged_above=-999 required=5 tests=[AWL=-2.400, 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 D+HDEXCSeiQS for <apps-discuss@ietfa.amsl.com>; Thu, 29 Dec 2011 08:46:10 -0800 (PST)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id 9CD7421F84BD for <apps-discuss@ietf.org>; Thu, 29 Dec 2011 08:46:09 -0800 (PST)
Received: (qmail invoked by alias); 29 Dec 2011 16:46:07 -0000
Received: from p3EE2751C.dip.t-dialin.net (EHLO [192.168.178.36]) [62.226.117.28] by mail.gmx.net (mp029) with SMTP; 29 Dec 2011 17:46:07 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1/Fu94lupDFWyJrJj0LRqaepUqqrlssJSsu3MP06h z0qcODL8HQNOlj
Message-ID: <4EFC994C.7080307@gmx.de>
Date: Thu, 29 Dec 2011 17:46:04 +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: mike amundsen <mamund@yahoo.com>
References: <4EFC8C98.10901@gmx.de> <CAPW_8m7oLLLVkinrjEdUvtZYjUDM5V9HVtVH_HnhNOBGixHfAQ@mail.gmail.com>
In-Reply-To: <CAPW_8m7oLLLVkinrjEdUvtZYjUDM5V9HVtVH_HnhNOBGixHfAQ@mail.gmail.com>
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: Thu, 29 Dec 2011 16:46:10 -0000

On 2011-12-29 17:07, mike amundsen wrote:
> Julian:
>
>
> I think there is already an XML format for PATCH, right? (can't seem
> to find it right now) It might not bee too much work to spin up a
> parallel media type definition using the JSON format.

Oh, there is already a proposal for a JSON-based patch format as well.

> That document might be proper place to describe a typical PATCH media
> type as (improvising here) "a format designed to *modify* an existing
> entity rather than replace all or part of an existing entity and/or
> introduce the notion of "partial updates" through the description of
> the PATCH method.

Why would you want to describe this as part of a spec for an XML format?

Best regards, Julian