IETF Logo Mail Archive

Re: [Json] [apps-discuss] JSON mailing list and BoF

Gonzalo Salgueiro <gsalguei@cisco.com> Tue, 19 February 2013 15:59 UTC

Return-Path: <gsalguei@cisco.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 E624B21F8DF7 for <json@ietfa.amsl.com>; Tue, 19 Feb 2013 07:59:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.508
X-Spam-Level:
X-Spam-Status: No, score=-10.508 tagged_above=-999 required=5 tests=[AWL=0.091, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zx8IzZKtF7iC for <json@ietfa.amsl.com>; Tue, 19 Feb 2013 07:59:29 -0800 (PST)
Received: from av-tac-rtp.cisco.com (av-tac-rtp.cisco.com [64.102.19.209]) by ietfa.amsl.com (Postfix) with ESMTP id 2476721F8DF1 for <json@ietf.org>; Tue, 19 Feb 2013 07:59:29 -0800 (PST)
X-TACSUNS: Virus Scanned
Received: from chook.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-rtp.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r1JFxSCK028313 for <json@ietf.org>; Tue, 19 Feb 2013 10:59:28 -0500 (EST)
Received: from rtp-gsalguei-8917.cisco.com (rtp-gsalguei-8917.cisco.com [10.116.132.56]) by chook.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r1JFxRFC025146; Tue, 19 Feb 2013 10:59:28 -0500 (EST)
Content-Type: text/plain; charset="iso-8859-1"
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Gonzalo Salgueiro <gsalguei@cisco.com>
In-Reply-To: <A723FC6ECC552A4D8C8249D9E07425A70F895E88@xmb-rcd-x10.cisco.com>
Date: Tue, 19 Feb 2013 10:59:27 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <28432E24-E917-4510-9F23-DF563B38032E@cisco.com>
References: <A723FC6ECC552A4D8C8249D9E07425A70F895E88@xmb-rcd-x10.cisco.com>
To: Joe Hildebrand <jhildebr@cisco.com>
X-Mailer: Apple Mail (2.1499)
Cc: Bjoern Hoehrmann <derhoermi@gmx.net>, Tim Bray <tbray@textuality.com>, json@ietf.org
Subject: Re: [Json] [apps-discuss] JSON mailing list and BoF
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion related to JavaScript Object Notation \(JSON\)." <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: Tue, 19 Feb 2013 15:59:30 -0000

On Feb 19, 2013, at 10:25 AM, Joe Hildebrand (jhildebr) <jhildebr@cisco.com> wrote:

> On 2/19/13 12:05 AM, "Tim Bray" <tbray@textuality.com> wrote:
> 
>> Easily solved: ³In all instances when JSON is transmitted over a network,
>> it MUST be encoded in UTF-8; a charset argument on the Content-type MAY
>> be provided, but its value MUST be utf-8.²
> 
> Could we change section 3 to explain that if you want to liberal in what
> you accept you can parse according to the older rules (including dealing
> with a BOM), but that you MUST always generate UTF-8 with no BOM if you're
> going to be 4627bis compliant?

I think that is reasonable, and it maintains the backwards compatibility you stressed as critical to this effort.

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

v2.23.0 | Report a Bug | By Email