IETF Logo Mail Archive

Re: [Json] Encoding detection (Was: Re: JSON: remove gap between Ecma-404 and IETF draft)

"Matt Miller (mamille2)" <mamille2@cisco.com> Fri, 22 November 2013 19:06 UTC

Return-Path: <mamille2@cisco.com>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CF1C1AE230 for <json@ietfa.amsl.com>; Fri, 22 Nov 2013 11:06:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.025
X-Spam-Level:
X-Spam-Status: No, score=-15.025 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.525, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, WEIRD_QUOTING=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lR3DuXgb6GQl for <json@ietfa.amsl.com>; Fri, 22 Nov 2013 11:06:05 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id A1FD51AE231 for <json@ietf.org>; Fri, 22 Nov 2013 11:06:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2089; q=dns/txt; s=iport; t=1385147159; x=1386356759; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=PkuhQd8SgVIQfwXh6kLDDG0Od0r6FjgzjBCcubFfDZI=; b=QeKSU/hJa0c4zNGy96yQ5TY1SPbQWVMThcI2uQEj9ZDEnTWRMhL9+dH2 MGHwECEHFJCakC9TvwUztQ/j3hvDxizsvYVzKvkOKU/iGURKHsgIMEMxd BgfqdMgdHjOiE3fUWqm0iT5Tzhq8pA99moR3OPQG9p+xrZ0q04ehC2WLK 8=;
X-Files: signature.asc : 496
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AisFAKCqj1KtJXG//2dsb2JhbABZgweBC7wVgSIWdIIlAQEBAwF5BQsCAQgYLjIlAgQOBQ6HYQMJBsEuF4x4gg8HgyCBEgOQMYExhjKSEoFqgT6CKg
X-IronPort-AV: E=Sophos; i="4.93,753,1378857600"; d="asc'?scan'208"; a="286891641"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-2.cisco.com with ESMTP; 22 Nov 2013 19:05:58 +0000
Received: from xhc-aln-x01.cisco.com (xhc-aln-x01.cisco.com [173.36.12.75]) by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id rAMJ5wdx017584 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 22 Nov 2013 19:05:58 GMT
Received: from xmb-aln-x11.cisco.com ([169.254.6.19]) by xhc-aln-x01.cisco.com ([173.36.12.75]) with mapi id 14.03.0123.003; Fri, 22 Nov 2013 13:05:57 -0600
From: "Matt Miller (mamille2)" <mamille2@cisco.com>
To: Julian Reschke <julian.reschke@gmx.de>
Thread-Topic: [Json] Encoding detection (Was: Re: JSON: remove gap between Ecma-404 and IETF draft)
Thread-Index: AQHO57KBUSEw68NY50iGvhEm1Fjae5oyAO+A
Date: Fri, 22 Nov 2013 19:05:57 +0000
Message-ID: <D922D194-968D-4528-85C5-51136C13BB3E@cisco.com>
References: <8413609C8A86497F856897AF2AA24960@codalogic> <CEAA3067.2D132%jhildebr@cisco.com> <CANXqsRJEtBoprQFrftz80ZigmBR_NHoEXK1sR4GyBtz5B2KC8Q@mail.gmail.com> <20131120223305.GB5476@mercury.ccil.org> <CANXqsRJmNmSRXssBnw3tGUt0veViENLoS=dp+gEr2RqvNAf4JQ@mail.gmail.com> <20131121165615.GA12138@mercury.ccil.org> <CANXqsRKrcR54TzSFng0ysyTV60-uZZ7QQ-G4xJOB0gO29C7-Ag@mail.gmail.com> <54E53D571E5E4589B2E9FA17DC816002@codalogic> <CAHBU6itwNwAy__Yy3n2bGMjuZnXAhK+qNbLq36piFy666m-Cng@mail.gmail.com> <EF7034DE-EA4D-43E4-9A5A-159E4A9DAB02@wirfs-brock.com> <BAC0485B-3C8F-43D5-9F14-52615AB00D4B@cisco.com> <528FA55F.30000@gmx.de>
In-Reply-To: <528FA55F.30000@gmx.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [64.101.72.44]
Content-Type: multipart/signed; boundary="Apple-Mail=_68EFC27F-866D-4995-AA12-DC70BBE2A989"; protocol="application/pgp-signature"; micalg="pgp-sha512"
MIME-Version: 1.0
Cc: es-discuss <es-discuss@mozilla.org>, "www-tag@w3.org" <www-tag@w3.org>, JSON WG <json@ietf.org>
Subject: Re: [Json] Encoding detection (Was: Re: JSON: remove gap between Ecma-404 and IETF draft)
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.15
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, 22 Nov 2013 19:06:07 -0000

On Nov 22, 2013, at 11:41 AM, Julian Reschke <julian.reschke@gmx.de> wrote:

> On 2013-11-22 19:33, Matt Miller (mamille2) wrote:
>> There does seem to be rough consensus that using an encoding other than UTF-8 can have interoperability issues.  The also seems to be rough consensus that the current text and table in section 8.1 for detecting the encoding will be inaccurate (and potentially harmful).
>> 
>> That appears to mean the approach with the most consensus is to remove the encoding detection entirely, leaving only:
>> 
>> """"
>>    JSON text SHALL be encoded in Unicode.  The default encoding is
>>    UTF-8.
>> """"
>> 
>> 
>> - Paul Hoffman and Matt Miller
> 
> Again:
> 
>  "JSON text SHALL be encoded in Unicode."
> 
> doesn't make any sense. "Unicode" is not a character encoding.
> 
> Can we please use proper terminology here?
> 
> Best regards, Julian

This was merely quoting the existing text in section 8.1, minus the encoding detection text.


- m&m

Matt Miller < mamille2@cisco.com >
Cisco Systems, Inc.

v2.23.0 | Report a Bug | By Email