Re: [apps-discuss] Review of draft-ietf-appsawg-json-pointer

James M Snell <jasnell@gmail.com> Thu, 15 November 2012 17:28 UTC

Return-Path: <jasnell@gmail.com>
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 802B421F89C3 for <apps-discuss@ietfa.amsl.com>; Thu, 15 Nov 2012 09:28:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.886
X-Spam-Level:
X-Spam-Status: No, score=-3.886 tagged_above=-999 required=5 tests=[AWL=-0.288, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 dttICDybCRcK for <apps-discuss@ietfa.amsl.com>; Thu, 15 Nov 2012 09:28:05 -0800 (PST)
Received: from mail-oa0-f44.google.com (mail-oa0-f44.google.com [209.85.219.44]) by ietfa.amsl.com (Postfix) with ESMTP id BF61F21F89BC for <apps-discuss@ietf.org>; Thu, 15 Nov 2012 09:28:04 -0800 (PST)
Received: by mail-oa0-f44.google.com with SMTP id n5so1992116oag.31 for <apps-discuss@ietf.org>; Thu, 15 Nov 2012 09:28:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=HB4EyUSUbvmMJGSC9ig67s9uUi4PXww6zII/ME4Ug7Y=; b=cOYapMM/1Bz/vlNemrIxGdCJW0GPOJEA1Rot5mFnmu5X/55sI5KAcZ8rfCnqeU0Yc9 0IQvjDywxlPVCQTiZVlcXjM6vNP6XilNdgsl77PAR07J89iLZgRxy6VEhzcuGYwpdQPg TE/VfrxtC5upRUzJwsFwSGndcXKaiPKnYNFETTbv0uVa0qpbhh2eaqq42bxONPM1K/VN TP1ituMpJWPqtGSAYjWi+sxA6pLiSr1Wk4gsWMTKIQyZhRQBvjshMYiszBVb2eLhTkgx 5STif4Ja5r+Fj1fqyR5WfaPEyA2PoI7M++vTISnQ3g7XuF2WDP5niVvymJcx1oSsWp4D VyEA==
Received: by 10.182.18.196 with SMTP id y4mr1505604obd.52.1353000484323; Thu, 15 Nov 2012 09:28:04 -0800 (PST)
MIME-Version: 1.0
Received: by 10.76.68.37 with HTTP; Thu, 15 Nov 2012 09:27:44 -0800 (PST)
In-Reply-To: <D8B6B887-7206-4197-B78D-7E2B38A20EF9@vpnc.org>
References: <D8B6B887-7206-4197-B78D-7E2B38A20EF9@vpnc.org>
From: James M Snell <jasnell@gmail.com>
Date: Thu, 15 Nov 2012 09:27:44 -0800
Message-ID: <CABP7RbdkyCwvLDAJYMwPf-HCLtxKrM0ttS7h7PziFYDMVcv0ww@mail.gmail.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: multipart/alternative; boundary="f46d04388ef53fc0ee04ce8bf932"
Cc: "apps-discuss@ietf.org Discuss" <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] Review of draft-ietf-appsawg-json-pointer
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, 15 Nov 2012 17:28:05 -0000

On Thu, Nov 15, 2012 at 7:24 AM, Paul Hoffman <paul.hoffman@vpnc.org> wrote:

> This document mostly looks fine.
>
> - I do not understand the use of "-"; at least one use of it in an
> application should be given.
>
> - If "-" is useful, wouldn't it also be useful to have something that
> indicates the (non-existant) member before the first array element?
>
>
This came from a requirement with json patch to allow a way of appending
new array items to the end. This was fairly extensively discussed and
concluded that the - was the least-complicated option that met the
requirement.

- James


> - Editorial nit in section 4:
>       *  characters that represent an unsigned base-10 integer value
>          (possibly with leading zeros), making the new referenced value
>          is the array element with the zero-based index identified by
>          the token, or
> That should either be "the new referenced value is the" or "making the new
> referenced value the", I believe.
>
> - One of the security considerations is too limited.
>    Note that JSON pointers can contain the NUL (Unicode U+0000)
>    character, which may not be representable in all programming
>    languages.
> The same is true for all control characters, and for some programming
> languages, all non-ASCII characters. Proposed rewording:
>    Note that JSON pointers can contain the NUL (Unicode U+0000)
>    character, control characters, non-ASCII characters, and so
>    on. These characters may not be representable in all programming
>    languages.


> --Paul Hoffman
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss
>