IETF Logo Mail Archive

Re: [Json] Proposal for strings/Unicode text

R S <sayrer@gmail.com> Wed, 12 June 2013 23:56 UTC

Return-Path: <sayrer@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 94EE021E80BA for <json@ietfa.amsl.com>; Wed, 12 Jun 2013 16:56:31 -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=[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 kbjMFn7wf39e for <json@ietfa.amsl.com>; Wed, 12 Jun 2013 16:56:31 -0700 (PDT)
Received: from mail-we0-x22d.google.com (mail-we0-x22d.google.com [IPv6:2a00:1450:400c:c03::22d]) by ietfa.amsl.com (Postfix) with ESMTP id C286A21E8087 for <json@ietf.org>; Wed, 12 Jun 2013 16:56:30 -0700 (PDT)
Received: by mail-we0-f173.google.com with SMTP id x54so6528666wes.18 for <json@ietf.org>; Wed, 12 Jun 2013 16:56:29 -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=xvwkfP/7n7FxGOr1Vtu1m3Ld2iqqneKDF9FgskiKtQE=; b=04nMc4slYZo5dbFlof3SLXBWsyR61MyxdlrER18Mqnx305pH13jAiwPFBlXvasOBZu wZa87oAqV1lNivp0EGYkYjQGpKh8K3Zlx0jNMSoASd/2U3tpA0+PW2U6mPT6KAdmmmuF WFrJ8PyUNvaiJ/B6frhGsP18DihxxEn7Zq5FhqaovElCTIfA0aSZoOIuVgoaiw15Q661 +yBJyjhH+X+wWyFxrjjqyb7Guba/DodmZp6izHO9q/M/J8UlVglTYFG3JUfOxNbnirnL WYaIuyHakL9m+I+kIfm6pWfu80EXpHiHy7j9SQT1xczWYaIQECpeCcDiKbIQ/jwFAZx8 bCcg==
MIME-Version: 1.0
X-Received: by 10.180.185.4 with SMTP id ey4mr6000356wic.49.1371081389096; Wed, 12 Jun 2013 16:56:29 -0700 (PDT)
Received: by 10.194.83.35 with HTTP; Wed, 12 Jun 2013 16:56:28 -0700 (PDT)
In-Reply-To: <D6191FD1-7DF9-4433-8427-48F866A3DBBC@tzi.org>
References: <CAHBU6ivNjMUwN2Hsn-E8FKxjqXS6b4qz=_MeeaHahWBWqG_Hgg@mail.gmail.com> <3E2A194C-789F-4E75-ABB0-CE966319463E@tzi.org> <CAHBU6ivw=4WfTyXdBns-i30fvzhkb+Zs_puj=YhFw+fh6n3R7A@mail.gmail.com> <D6191FD1-7DF9-4433-8427-48F866A3DBBC@tzi.org>
Date: Wed, 12 Jun 2013 16:56:28 -0700
Message-ID: <CAChr6Sw7wqAnAbm6Sfr0EvoVDoMnVhvrtiQy6y=NtgQAyXEq_Q@mail.gmail.com>
From: R S <sayrer@gmail.com>
To: Carsten Bormann <cabo@tzi.org>
Content-Type: multipart/alternative; boundary="001a11c3502227c68704defdc381"
Cc: Tim Bray <tbray@textuality.com>, "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] Proposal for strings/Unicode text
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: Wed, 12 Jun 2013 23:56:31 -0000

On Wed, Jun 12, 2013 at 4:40 PM, Carsten Bormann <cabo@tzi.org> wrote:

>
> Again, can we focus on the correct usage and ban avenues for misuse to an
> appendix?
>

The document should refrain from value judgements. The "correct" use is
what JSON is already being used for. Even Tim's "breakage" language is a
little strong (although I can live with it).

- Rob

v2.29.0 | Report a Bug | By Email | System Status