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

How so? Doesn't appear to be a problem in practice.

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.****
>
> ** **
>
> ** **
>
> --****
>
> 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****
>
> ** **
>