IETF Logo Mail Archive

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

Nico Williams <nico@cryptonector.com> Wed, 27 November 2013 00:39 UTC

Return-Path: <nico@cryptonector.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 65F1B1AE0CB for <json@ietfa.amsl.com>; Tue, 26 Nov 2013 16:39:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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_NONE=-0.0001] 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 4iwEA7092K5Q for <json@ietfa.amsl.com>; Tue, 26 Nov 2013 16:39:50 -0800 (PST)
Received: from homiemail-a96.g.dreamhost.com (caiajhbdcagg.dreamhost.com [208.97.132.66]) by ietfa.amsl.com (Postfix) with ESMTP id 2D9851AE0A4 for <json@ietf.org>; Tue, 26 Nov 2013 16:39:50 -0800 (PST)
Received: from homiemail-a96.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a96.g.dreamhost.com (Postfix) with ESMTP id F15933B805B; Tue, 26 Nov 2013 16:39:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=qACmxpGXYl5HGR IogCbbeaHOpDo=; b=vX5r40iwdDW9Eh7zXx0yHZcVP+jk9Deq619uKOQFGHU5Eg hIU1iCeAbcqY+vCDLcEecuzR6DBz7r3A+dJ1+siwJd7lBvELa1UnkUJ/MRr79h0J 4QfAH5p7sLXn/pxjmQhsxGSAHYAUYn6zU9ShXTTHPZY4Muk/WluZCMatwWtMY=
Received: from localhost (108-207-244-174.lightspeed.austtx.sbcglobal.net [108.207.244.174]) (Authenticated sender: nico@cryptonector.com) by homiemail-a96.g.dreamhost.com (Postfix) with ESMTPA id 9B7EE3B8005; Tue, 26 Nov 2013 16:39:49 -0800 (PST)
Date: Tue, 26 Nov 2013 18:39:49 -0600
From: Nico Williams <nico@cryptonector.com>
To: Bjoern Hoehrmann <derhoermi@gmx.net>
Message-ID: <20131127003945.GK21240@localhost>
References: <20131121165615.GA12138@mercury.ccil.org> <CANXqsRKrcR54TzSFng0ysyTV60-uZZ7QQ-G4xJOB0gO29C7-Ag@mail.gmail.com> <54E53D571E5E4589B2E9FA17DC816002@codalogic> <CANXqsRJi8dv0Giw7CZWP=10qEJEXGyRTb0HFnE9MpeAxc2_0rA@mail.gmail.com> <20131126160127.GE20755@mercury.ccil.org> <CAO1wJ5Qz2-vue_OGp79JZ+DW0ELofwdh8vy=9UZk53SMYs1bOg@mail.gmail.com> <20131126172410.GC21240@localhost> <mev999tgjoao5cj84fuk4t8pvi4t9pj6hs@hive.bjoern.hoehrmann.de> <20131126220036.GG21240@localhost> <fbba99l1gugiq5idqm7h5afk1o0p5j3teq@hive.bjoern.hoehrmann.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <fbba99l1gugiq5idqm7h5afk1o0p5j3teq@hive.bjoern.hoehrmann.de>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: es-discuss <es-discuss@mozilla.org>, www-tag <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: Wed, 27 Nov 2013 00:39:51 -0000

On Wed, Nov 27, 2013 at 01:14:00AM +0100, Bjoern Hoehrmann wrote:
>   HTTP/1.1 200 OK
>   Content-Type: application/json
>   ...
> 
>   ABCD...
> 
> There would be at least two specifications that apply here, the HTTP
> and the application/json specification. Would you like them to say
> that you are on your own, "ABCD..." could mean anything? [...]

Absolutely not, and I didn't say that either.  The application/json
media type absolutely has to be in a UTF, and preferably UTF-8.

> I cannot build robust software based on "well, maybe it's EBCDIC?
> Have you tried GB 18030? UTF-7 might be worth a try otherwise. Are
> you sure this matters at all?"

That is not even remotely what I want.  Either you misunderstood me or I
wasn't specific or clear enough.  Either way, I think it should be clear
as of my last message (though you might find things there to disagree
with).

Nico
--

v2.23.0 | Report a Bug | By Email