Message from discussion
About the latest JSON Pointer draft: the role of the caret ('^')
Received: by 10.52.21.68 with SMTP id t4mr946932vde.8.1334316273558;
Fri, 13 Apr 2012 04:24:33 -0700 (PDT)
X-BeenThere: json-schema@googlegroups.com
Received: by 10.220.248.81 with SMTP id mf17ls1441965vcb.7.gmail; Fri, 13 Apr
2012 04:24:32 -0700 (PDT)
Received: by 10.52.155.240 with SMTP id vz16mr959331vdb.3.1334316272944;
Fri, 13 Apr 2012 04:24:32 -0700 (PDT)
Received: by 10.52.155.240 with SMTP id vz16mr959329vdb.3.1334316272935;
Fri, 13 Apr 2012 04:24:32 -0700 (PDT)
Return-Path: <fgalie...@gmail.com>
Received: from mail-vb0-f53.google.com (mail-vb0-f53.google.com [209.85.212.53])
by gmr-mx.google.com with ESMTPS id hc9si3964975vdb.2.2012.04.13.04.24.32
(version=TLSv1/SSLv3 cipher=OTHER);
Fri, 13 Apr 2012 04:24:32 -0700 (PDT)
Received-SPF: pass (google.com: domain of fgalie...@gmail.com designates 209.85.212.53 as permitted sender) client-ip=209.85.212.53;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of fgalie...@gmail.com designates 209.85.212.53 as permitted sender) smtp.mail=fgalie...@gmail.com; dkim=pass header...@gmail.com
Received: by vbbfc26 with SMTP id fc26so2438240vbb.40
for <json-schema@googlegroups.com>; Fri, 13 Apr 2012 04:24:32 -0700 (PDT)
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
:content-type:content-transfer-encoding;
bh=McdbM5nuf8IFX5LiiS6oe0vyoMtQXL88pXjTXGlTwLw=;
b=coiJtZlWPH0YttCmex+MyhGCi17tkONBfd2ljR6v+5u04YsP1CCm3y43VVZ204rj9b
qCzT8NnAjix6xCEDnSFlK1N3rMr74E+gEviWIAC7EzUvSu/JGelI8JR66yIyhYiZBf9A
/z3DquMXNlAEo1p1tioT4Xq86byF5PXK2TI/d3UfJN1mDwKmDv5QVvm19RbBJQOs/FsA
KRqqNBgC2mBgnLo70QJgvfaAUPWlmPehtWVh378ewJBAFOUIWpGgiEdGDyBKlkosfzY3
pvBIF6GCWAHL1j72Ch0z55pocxt46g92lEf8MBSox6XJM4XV7HDKMUcHEgS4qolHVYaC
RPIA==
MIME-Version: 1.0
Received: by 10.220.185.136 with SMTP id co8mr638712vcb.5.1334316272845; Fri,
13 Apr 2012 04:24:32 -0700 (PDT)
Received: by 10.52.114.104 with HTTP; Fri, 13 Apr 2012 04:24:32 -0700 (PDT)
In-Reply-To: <CANMS5vGCFGORGFkZKU=Hr6jKr+LObbhfOYnf_W-h2TwPapo...@mail.gmail.com>
References: <CALcybBDPOt=oHQntqOZzBaRJCSZmjH3ZYxHJbTOGeATHu7y...@mail.gmail.com>
<1333949114.18831.1.camel@neutron>
<1440837.1262.1334041090372.JavaMail.geo-discussion-forums@vbug19>
<CALcybBCxZhRhcswm+kS_eeOXGDBJ=BZo8nW8FBXu7jmztg3...@mail.gmail.com>
<14593282.1629.1334046902305.JavaMail.geo-discussion-forums@vbex14>
<1334157106.2396.3.camel@neutron>
<CANMS5vGUYJhF81ec_CCjbjt+5oLeyhAu3UFJMCj5WBGNxh9...@mail.gmail.com>
<CALcybBBo9+RzYDuJijR1wQ4xC+o7nEq_=EbXz0jMVQc=6Mg...@mail.gmail.com>
<CALcybBAxxDCj_aHBU1ozM-vcDpFKnGpNtd-G4BSjgpMe+=-...@mail.gmail.com>
<CANMS5vGCFGORGFkZKU=Hr6jKr+LObbhfOYnf_W-h2TwPapo...@mail.gmail.com>
Date: Fri, 13 Apr 2012 13:24:32 +0200
Message-ID: <CALcybBCj_0eA0Ybd=uB4n_Arg4dQMkecZvXjoGk=GK0tiUc...@mail.gmail.com>
Subject: Re: [json-schema] About the latest JSON Pointer draft: the role of
the caret ('^')
From: Francis Galiegue <fgalie...@gmail.com>
To: json-schema@googlegroups.com
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
On Fri, Apr 13, 2012 at 01:16, Gary Court <gary.co...@gmail.com> wrote:
[...]
>
> Wrong; all escaping mechanisms have this problem. Example:
>
> {"^^":true} =3D=3D "/^^^^"
> escape(escape("/^^^^")) =3D=3D "/^"
>
No, you didn't understand what I mean.
JSON Pointer data will be transmitted via JSON files or URIs. Which
means, they MAY be JSON encoded or URI encoded. MAY, not MUST.
Which means that if you choose either of these two methods, you get in
the situation where you don't know whether your string is encoded in
either way. Conflict. Conundrum. Call it what you want. But in all
cases, a source of bugs.
With the spec as it currently is, this problem just doesn't surface _at all=
_.
--=20
Francis Galiegue, fgalie...@gmail.com
"It seems obvious [...] that at least some 'business intelligence'
tools invest so much intelligence on the business side that they have
nothing left for generating SQL queries" (St=C3=A9phane Faroult, in "The
Art of SQL", ISBN 0-596-00894-5)