Re: [Json] Scope: Wire format or runtime format?

"Joe Hildebrand (jhildebr)" <jhildebr@cisco.com> Sat, 15 June 2013 20:35 UTC

Return-Path: <jhildebr@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 9F67721F9CF3 for <json@ietfa.amsl.com>; Sat, 15 Jun 2013 13:35:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 UDiMGEtgh6dz for <json@ietfa.amsl.com>; Sat, 15 Jun 2013 13:35:34 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id 18E1021F9CEF for <json@ietf.org>; Sat, 15 Jun 2013 13:35:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=557; q=dns/txt; s=iport; t=1371328534; x=1372538134; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=/AaxrmW/v0YZZe3sOk4MCy/e7LKL6IRYWWsfHWsx88g=; b=S0sk79N3E12fm5LsKQdE5bLfTAE94fGodzgMR8zDOYmDv+m/bTcg8TG3 cBC/KJetB84hJnxBLpx+/fxFm0xUE2gl4WquoE9dvGtRiw+dQl4Nti1/k vHR9kQv6FNDIjPWF82mpclMoZULxk2dewqRGeaz27BsoMzmWGJGB7TfwY g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqMFAJjPvFGtJXHA/2dsb2JhbABagwl6gji8EIEGFnSCJQEEOj8SAQgiFEIlAgQBDQUIiAa5Io8WMQeCf2EDqQSDD4Io
X-IronPort-AV: E=Sophos;i="4.87,872,1363132800"; d="scan'208";a="223274402"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-6.cisco.com with ESMTP; 15 Jun 2013 20:35:33 +0000
Received: from xhc-aln-x01.cisco.com (xhc-aln-x01.cisco.com [173.36.12.75]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id r5FKZXAt026052 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 15 Jun 2013 20:35:33 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.56]) by xhc-aln-x01.cisco.com ([173.36.12.75]) with mapi id 14.02.0318.004; Sat, 15 Jun 2013 15:35:33 -0500
From: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
To: John Cowan <cowan@mercury.ccil.org>, Tim Bray <tbray@textuality.com>
Thread-Topic: [Json] Scope: Wire format or runtime format?
Thread-Index: AQHOadzi0LDFyps3JkOZ3Lj86+cy5Jk3QdKAgAAC8wD//+aBgA==
Date: Sat, 15 Jun 2013 20:35:32 +0000
Message-ID: <A723FC6ECC552A4D8C8249D9E07425A70FC4E706@xmb-rcd-x10.cisco.com>
In-Reply-To: <20130615160648.GC30796@mercury.ccil.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.3.4.130416
x-originating-ip: [10.21.117.127]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <BBE4E74E914B9947A8FC6B4AFA916EBD@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Norbert Lindenberg <ietf@lindenbergsoftware.com>, Paul Hoffman <paul.hoffman@vpnc.org>, "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] Scope: Wire format or runtime format?
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: Sat, 15 Jun 2013 20:35:39 -0000

On 6/15/13 10:06 AM, "John Cowan" <cowan@mercury.ccil.org> wrote:

>Tim Bray scripsit:
>
>> I think the IETF, at least at the Apps area, is in the business of
>>network
>> protocols, so I see our job here primarily as getting the wire-format
>> aspects right.
>
>+1, but that still has at least two aspects, the character-level syntax
>and the mapping to an entity body.

Is that only because of the multiple encodings?  For example, if JSON was
UTF8-only, could we define a purely concrete syntax of octet sequences?

-- 
Joe Hildebrand