IETF Logo Mail Archive

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

John Cowan <cowan@mercury.ccil.org> Thu, 04 July 2013 03:05 UTC

Return-Path: <cowan@ccil.org>
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 2FAAA11E8117 for <json@ietfa.amsl.com>; Wed, 3 Jul 2013 20:05:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.58
X-Spam-Level:
X-Spam-Status: No, score=-3.58 tagged_above=-999 required=5 tests=[AWL=0.019, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 fPEuORmFnzhY for <json@ietfa.amsl.com>; Wed, 3 Jul 2013 20:05:39 -0700 (PDT)
Received: from earth.ccil.org (earth.ccil.org [192.190.237.11]) by ietfa.amsl.com (Postfix) with ESMTP id 5E48311E80AD for <json@ietf.org>; Wed, 3 Jul 2013 20:05:36 -0700 (PDT)
Received: from cowan by earth.ccil.org with local (Exim 4.72) (envelope-from <cowan@ccil.org>) id 1UuZrQ-00076o-Er; Wed, 03 Jul 2013 23:05:32 -0400
Date: Wed, 03 Jul 2013 23:05:32 -0400
From: John Cowan <cowan@mercury.ccil.org>
To: Tatu Saloranta <tsaloranta@gmail.com>
Message-ID: <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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CAGrxA25aFJGvO-RepGP4tOdjVHVzEuP8H-F37Qrt8SNX9GqFdQ@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Sender: John Cowan <cowan@ccil.org>
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 03:05:44 -0000

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.

-- 
John Cowan    http://www.ccil.org/~cowan   <cowan@ccil.org>
    "Any legal document draws most of its meaning from context.  A telegram
    that says 'SELL HUNDRED THOUSAND SHARES IBM SHORT' (only 190 bits in
    5-bit Baudot code plus appropriate headers) is as good a legal document
    as any, even sans digital signature." --me

v2.23.0 | Report a Bug | By Email