Re: [Json] Two Documents

Tim Bray <tbray@textuality.com> Fri, 14 June 2013 02:01 UTC

Return-Path: <tbray@textuality.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 800DB21F9B06 for <json@ietfa.amsl.com>; Thu, 13 Jun 2013 19:01:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level:
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, 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 GX4Mw5Iccba3 for <json@ietfa.amsl.com>; Thu, 13 Jun 2013 19:01:29 -0700 (PDT)
Received: from mail-vc0-f178.google.com (mail-vc0-f178.google.com [209.85.220.178]) by ietfa.amsl.com (Postfix) with ESMTP id 6D21221F9AA4 for <json@ietf.org>; Thu, 13 Jun 2013 19:01:29 -0700 (PDT)
Received: by mail-vc0-f178.google.com with SMTP id m17so34631vca.23 for <json@ietf.org>; Thu, 13 Jun 2013 19:01:26 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=RmaaxF47pLA6O2dIVcpd2t2+JBNvXz5CL2bhJ1uwCLM=; b=WkRGpoD+9VyhSlZI74kF7I9m1Plj5Xw2gaqTmEeIGeJCx9h4j2MaLF/oJ24NpQcPDs BEYroXfqkw2Zswn2IAV2AuezPZ2IYzhOvKrEUHG7mWbZzjqA00m8uIz4QEbLAa/ZMmwQ ejpalArgxiSBfI0tl1rOlOdcj5kvokoQtveRJWl4k8bMcc+hl7FPqSZXSGquR8t+KJmF yoJTL9uSoXfwupynJZzFTnJ8TD8lPFGExen8UJwuV2nHybvsLTkaJDmVupCLdvx0wQKx D5i5m3e4O01zYTpGMWnlNDWxCWfPQHrbyZxrBlumaEBG2qwi255R4atc+Gti6jAIMU07 Hdag==
MIME-Version: 1.0
X-Received: by 10.220.67.81 with SMTP id q17mr85151vci.64.1371175286173; Thu, 13 Jun 2013 19:01:26 -0700 (PDT)
Received: by 10.220.25.199 with HTTP; Thu, 13 Jun 2013 19:01:25 -0700 (PDT)
X-Originating-IP: [209.52.105.82]
In-Reply-To: <CAChr6Sy4bKY2pfZbAxdvnQbH4=nBRLUssb351YXVXEs=vbKoRg@mail.gmail.com>
References: <51B9EA49.2050604@crockford.com> <CAO1wJ5SRb+NEP9yXrwzhUPOSJ6mPbkCfG_knnh0PJtZ=yGPC_g@mail.gmail.com> <CAChr6Sy4bKY2pfZbAxdvnQbH4=nBRLUssb351YXVXEs=vbKoRg@mail.gmail.com>
Date: Thu, 13 Jun 2013 19:01:25 -0700
Message-ID: <CAHBU6isTkjMTK86vco9W6R+2QJDJveESqN56GfoMEnQ-ifmyoQ@mail.gmail.com>
From: Tim Bray <tbray@textuality.com>
To: R S <sayrer@gmail.com>
Content-Type: multipart/alternative; boundary=047d7b343814dbbc9f04df139f5a
X-Gm-Message-State: ALoCoQmZr/FDN1gs6Y+C8UGPpuNurLp/70+YoGuruQdK1Qdf7UHtkgNIYZfhqZZuWK2n9vsle3zD
Cc: Jacob Davies <jacob@well.com>, Douglas Crockford <douglas@crockford.com>, "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] Two Documents
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: Fri, 14 Jun 2013 02:01:35 -0000

On Thu, Jun 13, 2013 at 6:42 PM, R S <sayrer@gmail.com> wrote:

> This dual-document proposal seems aimed at avoiding impractical character
> encoding requirements. I am sympathetic to that. I would prefer two
> documents over a single document with prescriptive and therefore incorrect
> encoding directives.
>

I think it’s pretty clear that 4627bis can’t retroactively rule out things
that are already in JSON like naked surrogates. So with luck we’re good
with a single JSON spec that says so, then another best-Internet-practices
one that says “don’t”. -T



>
> - Rob
>
> _______________________________________________
> json mailing list
> json@ietf.org
> https://www.ietf.org/mailman/listinfo/json
>
>