Re: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Standard

Robert Sayre <sayrer@gmail.com> Sun, 16 December 2012 04:36 UTC

Return-Path: <sayrer@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 620A521F8566; Sat, 15 Dec 2012 20:36:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 S+8+NmIFK6ak; Sat, 15 Dec 2012 20:36:08 -0800 (PST)
Received: from mail-we0-f172.google.com (mail-we0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 5F39321F845A; Sat, 15 Dec 2012 20:36:08 -0800 (PST)
Received: by mail-we0-f172.google.com with SMTP id r3so2276856wey.31 for <multiple recipients>; Sat, 15 Dec 2012 20:36:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=1UpRj7ApAA8YI+lkyR1A8ofFuuzUDbqp+QVzkAfqgo0=; b=KOK7Wne6kLpWvaLv/3u3k9nswRvD4600bul0L5//jRJQ/5cG/EwDqrKoVwPzc7SHcQ 6SoQrydvKHHnfgK+rVnL7SOxPHswYhbX3x2V8JKnBEWsGtk0lNOPKHKJsZaiQVFz0R4r XAyBHrPHjjUNDZFH8vgqwK4xrwmlMS5Vh2W11fRkc3q86uo5f1iWJmWYacB4kDVmE3hj TCOU3glKrTjuVYfa6xAdYDf5n1xJj4T+LnyOAUWZZNRg8hdBrJfRjA65GlhCojwGhsgX dQM4Fw1xZVzZkzjUZMJWHa/RJ2fWl4P8P5ZxwJRyCCis1i8bIJl08IFHv7vvn10Tdy8P PQew==
MIME-Version: 1.0
Received: by 10.194.23.37 with SMTP id j5mr10657051wjf.28.1355632567498; Sat, 15 Dec 2012 20:36:07 -0800 (PST)
Received: by 10.194.1.101 with HTTP; Sat, 15 Dec 2012 20:36:07 -0800 (PST)
In-Reply-To: <50cb5f3c.694c420a.38fb.39afSMTPIN_ADDED_BROKEN@mx.google.com>
References: <20121211150057.28223.93310.idtracker@ietfa.amsl.com> <50cb04b9.86df440a.72fe.1e20SMTPIN_ADDED_BROKEN@mx.google.com> <CABP7RbeNsZ_rBWRjou=VG+hBhUKaOz+y1a0sSChwWiHte9znnQ@mail.gmail.com> <50cb5f3c.694c420a.38fb.39afSMTPIN_ADDED_BROKEN@mx.google.com>
Date: Sat, 15 Dec 2012 20:36:07 -0800
Message-ID: <CAChr6SxZRc3B_HCbw76kLe2dsRSr43r-gLpfMVnCUfJTrZdTLA@mail.gmail.com>
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Standard
From: Robert Sayre <sayrer@gmail.com>
To: Markus Lanthaler <markus.lanthaler@gmx.net>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
Cc: James M Snell <jasnell@gmail.com>, IETF Discussion <ietf@ietf.org>, IETF Apps Discuss <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Dec 2012 04:36:09 -0000

On Fri, Dec 14, 2012 at 9:17 AM, Markus Lanthaler
<markus.lanthaler@gmx.net> wrote:
>
> Hmm.. I think that’s quite problematic. Especially considering how JSON Pointer is used in JSON Patch.

I agree--I provided the same feedback privately. It seems
straightforwardly unsound.

- Rob


>
> --
>
> Markus Lanthaler
>
> @markuslanthaler
>
>
>
>
>
>
>
> From: James M Snell [mailto:jasnell@gmail.com]
> Sent: Friday, December 14, 2012 5:41 PM
> To: Markus Lanthaler
> Cc: IETF Discussion; IETF Apps Discuss
> Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Standard
>
>
>
> JSON Pointer does not distinguish between objects and arrays. That is not determined until the pointer is applied to an actual object instance... the pointer "/1" is valid against {"1":"a"} or ["a","b"]
>
>
>
> On Fri, Dec 14, 2012 at 2:51 AM, Markus Lanthaler <markus.lanthaler@gmx.net> wrote:
>
> I've asked that before but didn't get an answer. So let me ask again (even
> though I'm quite sure it has already been asked by somebody else).
>
> How does JSON Pointer distinguish between objects and arrays? E.g. consider
> the following JSON document:
>
> {
>   "foo": "bar",
>   "1": "baz"
> }
>
> As I read the draft, the JSON Pointer "/1" would evaluate to "baz" even
> though that's probably not what the author intended. Is there a way to avoid
> that?
>
>
> Thanks,
> Markus
>
>
>
> --
> Markus Lanthaler
> @markuslanthaler
>
>
>
>
>
> > -----Original Message-----
> > From: apps-discuss-bounces@ietf.org [mailto:apps-discuss-
> > bounces@ietf.org] On Behalf Of The IESG
> > Sent: Tuesday, December 11, 2012 4:01 PM
> > To: IETF-Announce
> > Cc: apps-discuss@ietf.org
> > Subject: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-
> > 07.txt> (JSON Pointer) to Proposed Standard
> >
> >
> > The IESG has received a request from the Applications Area Working
> > Group
> > WG (appsawg) to consider the following document:
> > - 'JSON Pointer'
> >   <draft-ietf-appsawg-json-pointer-07.txt> as Proposed Standard
> >
> > The IESG plans to make a decision in the next few weeks, and solicits
> > final comments on this action. Please send substantive comments to the
> > ietf@ietf.org mailing lists by 2012-12-25. Exceptionally, comments may
> > be
> > sent to iesg@ietf.org instead. In either case, please retain the
> > beginning of the Subject line to allow automated sorting.
> >
> > Abstract
> >
> >
> >    JSON Pointer defines a string syntax for identifying a specific
> > value
> >    within a JSON document.
> >
> >
> >
> >
> > The file can be obtained via
> > http://datatracker.ietf.org/doc/draft-ietf-appsawg-json-pointer/
> >
> > IESG discussion can be tracked via
> > http://datatracker.ietf.org/doc/draft-ietf-appsawg-json-pointer/ballot/
> >
> >
> > No IPR declarations have been submitted directly on this I-D.
> >
> >
> > _______________________________________________
> > apps-discuss mailing list
> > apps-discuss@ietf.org
> > https://www.ietf.org/mailman/listinfo/apps-discuss
>
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss
>
>
>
>
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss
>