Re: [apps-discuss] draft-ietf-appsawg-json-patch and draft-ietf-appsawg-json-pointer

Mark Nottingham <> Thu, 24 May 2012 01:55 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 51D4221F867E for <>; Wed, 23 May 2012 18:55:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -103.17
X-Spam-Status: No, score=-103.17 tagged_above=-999 required=5 tests=[AWL=-0.571, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id SzHyzMmSllqG for <>; Wed, 23 May 2012 18:55:52 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 80D5621F867C for <>; Wed, 23 May 2012 18:55:52 -0700 (PDT)
Received: from (unknown []) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPSA id CFAD722E257; Wed, 23 May 2012 21:55:45 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1278)
Content-Type: text/plain; charset="windows-1252"
From: Mark Nottingham <>
In-Reply-To: <>
Date: Thu, 24 May 2012 11:55:42 +1000
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <>
To: "Murray S. Kucherawy" <>
X-Mailer: Apple Mail (2.1278)
Cc: "" <>
Subject: Re: [apps-discuss] draft-ietf-appsawg-json-patch and draft-ietf-appsawg-json-pointer
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 24 May 2012 01:55:53 -0000

FWIW, I think JSON-Patch is good to go, and I'd really like to see it progress (I have a number of use cases for it).

JSON-Pointer seems to be in reasonable shape; I might have made some difference choices about its syntax, but that's largely bikeshedding. Because I want JSON-Patch, I want this too.

Perhaps it'd help to get the outstanding issues into the tracker?


On 23/05/2012, at 4:42 AM, Murray S. Kucherawy wrote:

> Hi appsawg folks,
> The above two drafts haven’t received much attention lately.  In March and April they each had some independent threads of discussion but they weren’t resolved, and no new version or specific proposed changes with consensus have appeared.  In particular, there is no apparent consensus to progress them as-is nor is there consensus that the issues raised are off in the weeds.  So we’re stuck.
> It might be helpful to the author to have a few more reviewers.  They are both short documents.  Please take a moment to review them, perhaps in the context of the previous threads, and provide some commentary.  Those of you that have commented before, perhaps you could summarize your concerns (or simply reference them) to help the author collate and apply feedback.
> As has been pointed out, we have several documents in progress here and a couple in Call For Adoption that we are now holding until some of the current docket clears.  Having two that are fully idle is, thus, a concern.
> If they continue to remain inactive, we may consider officially “parking” them and trying to resume work on them later, or simply consider them dead if there truly is no interest in pursuing their publication.
> -MSK, APPSAWG co-chair
> _______________________________________________
> apps-discuss mailing list

Mark Nottingham