Re: [apps-discuss] feedback on draft-ietf-appsawg-json-patch-01.txt

Julian Reschke <julian.reschke@gmx.de> Tue, 20 March 2012 21:13 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 827CE21F866A for <apps-discuss@ietfa.amsl.com>; Tue, 20 Mar 2012 14:13:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.649
X-Spam-Level:
X-Spam-Status: No, score=-103.649 tagged_above=-999 required=5 tests=[AWL=-1.050, 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 sZR467URduYp for <apps-discuss@ietfa.amsl.com>; Tue, 20 Mar 2012 14:13:32 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id 31AAD21F8679 for <apps-discuss@ietf.org>; Tue, 20 Mar 2012 14:13:31 -0700 (PDT)
Received: (qmail invoked by alias); 20 Mar 2012 21:13:30 -0000
Received: from p57A6E8EB.dip.t-dialin.net (EHLO [192.168.178.36]) [87.166.232.235] by mail.gmx.net (mp001) with SMTP; 20 Mar 2012 22:13:30 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1+5GjkRoYq5gmrg2+H3RJku5CO6z9FMLbt/OS4OOw 76Ss3idLVyj4m+
Message-ID: <4F68F2F8.7000207@gmx.de>
Date: Tue, 20 Mar 2012 22:13:28 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: "Paul C. Bryan" <pbryan@anode.ca>
References: <20120309212231.16366.52439.idtracker@ietfa.amsl.com> <4F689626.9070500@gmx.de> <1332261146.2171.7.camel@neutron> <4F68B37E.9060608@gmx.de> <1332262482.2171.11.camel@neutron> <4F68BDB7.7030808@gmx.de> <1332269074.2171.21.camel@neutron> <4F68D295.2040401@gmx.de> <1332277294.2171.25.camel@neutron>
In-Reply-To: <1332277294.2171.25.camel@neutron>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: apps-discuss@ietf.org
Subject: Re: [apps-discuss] feedback on draft-ietf-appsawg-json-patch-01.txt
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: Tue, 20 Mar 2012 21:13:33 -0000

On 2012-03-20 22:01, Paul C. Bryan wrote:
> On Tue, 2012-03-20 at 19:55 +0100, Julian Reschke wrote:
>
>> So is the intent to define the fragment identifier syntax for
>> application/json or not?
>
> It wasn't my intent originally, though your concerns have me think that
> perhaps we should consider it. It was to define a fragment identifier
> syntax, which other specifications (e.g. JSON Schema, JSON Reference)
> can reference.
>
>> If it is, we need to normatively update the JSON RFC, and need to make
>> sure there's really consensus on this.
>
> Question: Do you think it should?

I'm not sure.

>> If it is not, the way the Pointer spec currently is written is very
>> confusing.
>
> Any text suggestions to resolve this?

Section 6 should clarify that the fragment identifier syntax applies to 
Internet Media Types that explicitly choose it, and that 
application/json hasn't (yet).

The examples in the appendix should get an explanation that they apply 
to a JSON-shaped example media type that indeed has choosen the fragid 
syntax...

Best regards, Julian