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

James M Snell <jasnell@gmail.com> Fri, 14 December 2012 16:41 UTC

Return-Path: <jasnell@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 D684121F89E9; Fri, 14 Dec 2012 08:41:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.707
X-Spam-Level:
X-Spam-Status: No, score=-3.707 tagged_above=-999 required=5 tests=[AWL=-0.109, 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 cUm6sSIM2Ni5; Fri, 14 Dec 2012 08:41:02 -0800 (PST)
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by ietfa.amsl.com (Postfix) with ESMTP id CF5A321F894D; Fri, 14 Dec 2012 08:41:01 -0800 (PST)
Received: by mail-ie0-f172.google.com with SMTP id c13so6252261ieb.31 for <multiple recipients>; Fri, 14 Dec 2012 08:40:56 -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=Z4cmBJ7oAY29bR3/a8ACPI4H06Lrrmh4SGAYfcHCLrI=; b=NecIG+gej7MZatR1XcBVIlmAmywKjNBqYE/2JbXCXkdX+vWNLX8W3RbBAs5gTJSZ80 TvU7H0xNd5P0ZakWZkdDVSKalvMzG2M9Nw+xD3KIITqyMaJg8nNPR/dipmGqV/WhY5kB /BWKqC3/3+EXT3eThhZdBYehv/10LHLbgmfqWgToYFIaj8GSxyYmeOi4SJguzQNdn4yD iRFzGAQ0jrxyxo3bLtYPI+5+/bz41PbQt6ubN8ZWm5CSgIVs6bFlVQuQSYmUcaM5bZyt O+NmHCwou/lCkqBjP80eG9gSfSAfCue5PWQqMN9kKhSc+gi0zOGxLB7wdf1wcdxpBBvb ax/A==
Received: by 10.50.6.169 with SMTP id c9mr2179709iga.24.1355503256744; Fri, 14 Dec 2012 08:40:56 -0800 (PST)
MIME-Version: 1.0
Received: by 10.64.7.19 with HTTP; Fri, 14 Dec 2012 08:40:36 -0800 (PST)
In-Reply-To: <50cb04b9.86df440a.72fe.1e20SMTPIN_ADDED_BROKEN@mx.google.com>
References: <20121211150057.28223.93310.idtracker@ietfa.amsl.com> <50cb04b9.86df440a.72fe.1e20SMTPIN_ADDED_BROKEN@mx.google.com>
From: James M Snell <jasnell@gmail.com>
Date: Fri, 14 Dec 2012 08:40:36 -0800
Message-ID: <CABP7RbeNsZ_rBWRjou=VG+hBhUKaOz+y1a0sSChwWiHte9znnQ@mail.gmail.com>
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Standard
To: Markus Lanthaler <markus.lanthaler@gmx.net>
Content-Type: multipart/alternative; boundary="e89a8f6467171c338604d0d2b2c4"
X-Mailman-Approved-At: Fri, 14 Dec 2012 09:26:57 -0800
Cc: 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: Fri, 14 Dec 2012 16:41:03 -0000

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
>