Re: [Json] What are we trying to do?

Tatu Saloranta <tsaloranta@gmail.com> Thu, 04 July 2013 22:27 UTC

Return-Path: <tsaloranta@gmail.com>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2517F11E81E9 for <json@ietfa.amsl.com>; Thu, 4 Jul 2013 15:27:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 53w0gwYZgRU9 for <json@ietfa.amsl.com>; Thu, 4 Jul 2013 15:27:12 -0700 (PDT)
Received: from mail-wg0-x22a.google.com (mail-wg0-x22a.google.com [IPv6:2a00:1450:400c:c00::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 4B90911E81AD for <json@ietf.org>; Thu, 4 Jul 2013 15:27:11 -0700 (PDT)
Received: by mail-wg0-f42.google.com with SMTP id z11so6779606wgg.5 for <json@ietf.org>; Thu, 04 Jul 2013 15:27:10 -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 :cc:content-type; bh=BiUwUFeevGJoyNMo37g66uqv2E/dGbSjy2fk0OEHbr0=; b=Jqm/YTNc/rvjQwDIbCczHsTaAupvoX35rMH/jAV8QgBrhOsI+PGDqSlRJBGG/a4Xel NrSL0KqsVfJbWUpDM+zqAF0uu/TzzeuMtI7vYPcgWAbuc51Ix4jMG1VqlG4w2Vw9b6vG ixZUuowneVyGvLa3stQ8QeXz/ZRK03Zwrq+Gei2gJvh9f3DeKrBzVGU/v+5PRgyRA5n5 o+/WoF5VEkUzCXaxZoYubfM3bIWSkK2KA42gQZ0PC/9kMLVztVlYygfg1rgFpz0YbXuO dp3Vwe987MDhp1RGSO8KwEJCMi21Tjxwbsk2cVhqtAm3sXb6KLoVJv+glXXMXVF25usL MRdg==
MIME-Version: 1.0
X-Received: by 10.180.12.45 with SMTP id v13mr21984214wib.7.1372976830380; Thu, 04 Jul 2013 15:27:10 -0700 (PDT)
Received: by 10.227.34.199 with HTTP; Thu, 4 Jul 2013 15:27:10 -0700 (PDT)
In-Reply-To: <20130704030532.GA14538@mercury.ccil.org>
References: <CAHBU6iv0wXYvAyasSE8Wga0K_sD_pKL6o-a-ca9yemhy3m6zzw@mail.gmail.com> <FB90FFED-5128-4B5C-85DE-78DFE2674310@vpnc.org> <CAK3OfOjvtU6=3EowmU0ccWAfQPSoGaUhPMLe+uK6pVR_sQDGFg@mail.gmail.com> <CAGrxA25aFJGvO-RepGP4tOdjVHVzEuP8H-F37Qrt8SNX9GqFdQ@mail.gmail.com> <20130704030532.GA14538@mercury.ccil.org>
Date: Thu, 04 Jul 2013 15:27:10 -0700
Message-ID: <CAGrxA25hem=shweXvhsZEpUrX4=+8rjFagJ77cK6OndNZUb7XA@mail.gmail.com>
From: Tatu Saloranta <tsaloranta@gmail.com>
To: John Cowan <cowan@mercury.ccil.org>
Content-Type: multipart/alternative; boundary="001a11c22ac0427faf04e0b7142d"
Cc: Nico Williams <nico@cryptonector.com>, Tim Bray <tbray@textuality.com>, Paul Hoffman <paul.hoffman@vpnc.org>, "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] What are we trying to do?
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "JavaScript Object Notation \(JSON\) WG mailing list" <json.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/json>, <mailto:json-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/json>
List-Post: <mailto:json@ietf.org>
List-Help: <mailto:json-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/json>, <mailto:json-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Jul 2013 22:27:13 -0000

On Wed, Jul 3, 2013 at 8:05 PM, John Cowan <cowan@mercury.ccil.org> wrote:

> Tatu Saloranta scripsit:
>
> > On unpaired surrogates: since their potential use has been outlined
> > multiple times, I am wondering if this has been substantiated by links to
> > systems that make use of this ability? I assume this potential exists
> only
> > on some platforms (and specifically not useful for platforms I typically
> > work on), but it would good to see links, similar to recent listing of
> > Streaming JSON processors one can find with bit of googling (happy to see
> > my SO answer being linked :) ).
>
> I would say that the potential is there for any JSON system running on
> a JVM, CLR, or JavaScript platform, since in all of these a string is
> a sequence of 16-bit code points.
>

Right I am not saying there is not potential -- potential is pretty clear
to me.

But is that potential used by anyone to substantial degree? Is there
existing use that would be hampered? What would break?

-+ Tatu +-