[Json] Serializing to File? Re: I-D Action: draft-ietf-jsonbis-rfc7159bis-04.txt

Anders Rundgren <anders.rundgren.net@gmail.com> Sat, 22 July 2017 09:18 UTC

Return-Path: <anders.rundgren.net@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 7BA681317C1 for <json@ietfa.amsl.com>; Sat, 22 Jul 2017 02:18:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 6u9KZpbYrI_d for <json@ietfa.amsl.com>; Sat, 22 Jul 2017 02:18:06 -0700 (PDT)
Received: from mail-wm0-x231.google.com (mail-wm0-x231.google.com [IPv6:2a00:1450:400c:c09::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 209E0129AEB for <json@ietf.org>; Sat, 22 Jul 2017 02:18:06 -0700 (PDT)
Received: by mail-wm0-x231.google.com with SMTP id w191so23658295wmw.1 for <json@ietf.org>; Sat, 22 Jul 2017 02:18:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:references:from:to:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=VzOgISNkPZRZyAvpEl+c6P1BqpV+hU6r6z1SDFsiO84=; b=IUpK2aRJN85CHd7UX2BYSTAaAD4eVg+GbqBvzP9Xxltg1KuPkB6lnAt2x2xFvf3DXs USAztwQLBRASmCI/xAvniyb3YGywLzhnC2WxF2vCmfZ+SUso7oU4qGdktqr5/rnmllCU bes312EVigr1/lU0t3OgV1E/ydqrig/vjN1vT2nZ03eaWXvtZdtxrt8dW3A9zMBS1STf QCSCT0jl+D2KYfCRsmBjs88GNd3CNe+djS7jaoBmFHGYhbdfwHYiorVUQPuBiDeOg02G BUzQBV4rWrtTMpfLX/muWRhD7Tb5UBVvOh7dedNdQD+QkNoN1HsjSVltY915zr6A1v0c 9GDw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:references:from:to:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=VzOgISNkPZRZyAvpEl+c6P1BqpV+hU6r6z1SDFsiO84=; b=sPbsDxx/KQJEr2Tq8me5Fk/ksoU9lU5enWWXKEW9BwVbq0soMHzppo+Yuf/Q5mq/gM aexB0NUGsa2+ADeFi8dyFryXPhrNK3OmsT1AUEMedMO3paxEfLhrwj8pB3VyH+DPaRm9 Ua4ZyjYYkMXeiEKorzXqYHu6lCYEnjkkeCXcnY4OVFXv0sED9ZbWscB1kN+vGo/1gF5D t9t1eqCUPl793D9/4LkcVLhYVQMFb598EbeNxda3nGrUgpQ0cY+ixnLJIaB17pG7gIhv Pmn3JfkWvSlXoWGnc8xLSxXZ+brMROAN86/MtL338npErEsxQvpZVZxVCXqMuBgtXHHG ZjWA==
X-Gm-Message-State: AIVw112DrxvHnMseBQMb4H3EAv6YxbQhVuolCbxF8AjitOJjfYyM5Puy Dp2fzhdsJKuX2u2u
X-Received: by 10.28.19.207 with SMTP id 198mr1054366wmt.166.1500715084405; Sat, 22 Jul 2017 02:18:04 -0700 (PDT)
Received: from [192.168.1.79] (25.131.146.77.rev.sfr.net. [77.146.131.25]) by smtp.googlemail.com with ESMTPSA id q185sm5558772wmd.19.2017.07.22.02.18.03 for <json@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 22 Jul 2017 02:18:03 -0700 (PDT)
References: <150047191184.7507.7143481683564082881@ietfa.amsl.com> <DB9BA7EA-D393-4079-B347-620A09280B26@isode.com> <CAC4RtVBYMrRCrUZ1qqD+_rH4M8N23GOgbbh=921fEYqH+gCm5Q@mail.gmail.com> <c06e583a-965e-9eaf-975f-e6876ac056ed@filament.com> <f1a6b553-c787-e248-67bd-74d68d98a845@gmx.de> <262E8314-263A-4443-B912-AFCF1A3277B2@tzi.org> <166957c4-26fc-90b5-a798-59280c91b466@filament.com> <8B60039F-96DD-4F72-8139-D80B6F11566C@tzi.org> <3760a157-5b88-e334-712c-03eecd675794@codalogic.com>
From: Anders Rundgren <anders.rundgren.net@gmail.com>
To: json@ietf.org
Message-ID: <75178e2b-f727-2e2e-796d-8e0bc7976bf7@gmail.com>
Date: Sat, 22 Jul 2017 11:18:02 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <3760a157-5b88-e334-712c-03eecd675794@codalogic.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/Q5K1PtrvbiUM1_wShFQGUhjcXEg>
Subject: [Json] Serializing to File? Re: I-D Action: draft-ietf-jsonbis-rfc7159bis-04.txt
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Sat, 22 Jul 2017 09:18:07 -0000

Since the most basic use case of all obviously doesn't work well if people
use different character encodings (unless you do "byte sniffing" which seems
like a bad thing to *have* to do).

I would consider "external form" as an alternative to limiting the specification
to special cases like networks and or protocols.

Just my two "öres".

Anders