Re: [Json] Response to Statement from W3C TAG
Carsten Bormann <cabo@tzi.org> Thu, 05 December 2013 07:39 UTC
Return-Path: <cabo@tzi.org>
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 5741E1AC3DD for <json@ietfa.amsl.com>; Wed, 4 Dec 2013 23:39:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.551
X-Spam-Level:
X-Spam-Status: No, score=-1.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, SPF_HELO_PASS=-0.001] autolearn=no
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 iCA-cKLuurCW for <json@ietfa.amsl.com>; Wed, 4 Dec 2013 23:39:35 -0800 (PST)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 091CE1A8026 for <json@ietf.org>; Wed, 4 Dec 2013 23:39:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id rB57dPeJ023213; Thu, 5 Dec 2013 08:39:25 +0100 (CET)
Received: from [192.168.217.105] (p548901B4.dip0.t-ipconnect.de [84.137.1.180]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id A013780E; Thu, 5 Dec 2013 08:39:22 +0100 (CET)
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
Content-Type: text/plain; charset="windows-1252"
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CAHBU6itM4haCemNe-MzPFwHf659KWfqXA+yACLCyQFfPrw_w2A@mail.gmail.com>
Date: Thu, 05 Dec 2013 08:39:20 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <CF7C2C14-996C-4AC4-BBCB-EF4FD46C123C@tzi.org>
References: <799C8AFA-53C3-4698-A14A-96CB79981DE5@cisco.com> <CAHBU6itM4haCemNe-MzPFwHf659KWfqXA+yACLCyQFfPrw_w2A@mail.gmail.com>
To: Tim Bray <tbray@textuality.com>
X-Mailer: Apple Mail (2.1822)
Cc: JSON WG <json@ietf.org>, "Matt Miller (mamille2)" <mamille2@cisco.com>
Subject: Re: [Json] Response to Statement from W3C TAG
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: Thu, 05 Dec 2013 07:39:36 -0000
On 05 Dec 2013, at 06:08, Tim Bray <tbray@textuality.com> wrote: > FWIW, I have never understood what the ECMAnauts mean by the word “semantics” in this context, so I have no idea whether I agree with this statement. You know this, but just for the record: we could be applying the meaning we have for these terms in CS. The syntax just tells you which sequences of symbols are part of the language. (This is what we have ABNF for; ECMA-404 uses racetracks plus some English language that maps the characters to the tokens in the syntax-level racetracks for value, object, and array, and to the English language components of the token-level racetracks for number and string.) Semantics is needed to describe e.g. that some whitespace is “insignificant” (not contributing to the semantics), describe the intended interpretation of escape sequences in strings, that the sequences of symbols enabled by the production “number” are to be interpreted in base 10, or that “the order of the values is significant” in arrays (which seems to be intended to contrast them to JSON objects, where ECMA-404 weasels out of saying whether the order is significant). ECMA-404 does quite a bit of of the latter, so indeed I also have trouble interpreting such a statement. (That doesn’t mean that the chairs’ echo of statements of this kind having been made is incorrect.) Grüße, Carsten
- [Json] Response to Statement from W3C TAG Matt Miller (mamille2)
- Re: [Json] Response to Statement from W3C TAG Tim Bray
- Re: [Json] Response to Statement from W3C TAG Carsten Bormann
- Re: [Json] Response to Statement from W3C TAG Paul Hoffman
- Re: [Json] Response to Statement from W3C TAG Allen Wirfs-Brock
- Re: [Json] Response to Statement from W3C TAG Carsten Bormann
- Re: [Json] Response to Statement from W3C TAG Allen Wirfs-Brock
- Re: [Json] Response to Statement from W3C TAG Nico Williams
- Re: [Json] Response to Statement from W3C TAG Allen Wirfs-Brock
- Re: [Json] Response to Statement from W3C TAG Nico Williams
- Re: [Json] Response to Statement from W3C TAG Carsten Bormann
- Re: [Json] Response to Statement from W3C TAG Allen Wirfs-Brock
- Re: [Json] Response to Statement from W3C TAG Carsten Bormann
- Re: [Json] Response to Statement from W3C TAG Allen Wirfs-Brock
- Re: [Json] Response to Statement from W3C TAG Bjoern Hoehrmann
- Re: [Json] Response to Statement from W3C TAG Nico Williams
- Re: [Json] Response to Statement from W3C TAG Nico Williams
- Re: [Json] Response to Statement from W3C TAG Carsten Bormann
- Re: [Json] Response to Statement from W3C TAG Tim Bray
- Re: [Json] Response to Statement from W3C TAG John Cowan
- Re: [Json] Response to Statement from W3C TAG John Cowan
- Re: [Json] Response to Statement from W3C TAG Allen Wirfs-Brock
- Re: [Json] Response to Statement from W3C TAG Bjoern Hoehrmann
- Re: [Json] Response to Statement from W3C TAG John Cowan
- Re: [Json] Response to Statement from W3C TAG Allen Wirfs-Brock
- Re: [Json] Response to Statement from W3C TAG Allen Wirfs-Brock
- Re: [Json] Response to Statement from W3C TAG Martin J. Dürst
- Re: [Json] Response to Statement from W3C TAG Martin J. Dürst
- Re: [Json] Response to Statement from W3C TAG Nico Williams
- Re: [Json] Response to Statement from W3C TAG Martin J. Dürst
- Re: [Json] Response to Statement from W3C TAG Carsten Bormann
- Re: [Json] Response to Statement from W3C TAG Bjoern Hoehrmann
- Re: [Json] Response to Statement from W3C TAG Carsten Bormann
- Re: [Json] Response to Statement from W3C TAG John Cowan
- Re: [Json] Response to Statement from W3C TAG Jorge Chamorro
- Re: [Json] Response to Statement from W3C TAG Allen Wirfs-Brock
- Re: [Json] Response to Statement from W3C TAG John Cowan
- Re: [Json] Response to Statement from W3C TAG Nico Williams
- Re: [Json] Response to Statement from W3C TAG Tim Bray
- Re: [Json] Response to Statement from W3C TAG Julian Reschke
- Re: [Json] Response to Statement from W3C TAG Allen Wirfs-Brock
- Re: [Json] Response to Statement from W3C TAG Allen Wirfs-Brock
- Re: [Json] Response to Statement from W3C TAG Tim Bray
- Re: [Json] Response to Statement from W3C TAG Allen Wirfs-Brock
- Re: [Json] Response to Statement from W3C TAG Carsten Bormann
- Re: [Json] Response to Statement from W3C TAG Tim Bray
- Re: [Json] Response to Statement from W3C TAG Bjoern Hoehrmann
- Re: [Json] Response to Statement from W3C TAG Julian Reschke
- Re: [Json] Response to Statement from W3C TAG Manger, James H
- Re: [Json] Response to Statement from W3C TAG Nico Williams
- Re: [Json] Response to Statement from W3C TAG Martin J. Dürst
- Re: [Json] Response to Statement from W3C TAG Martin J. Dürst
- Re: [Json] Response to Statement from W3C TAG James Clark
- Re: [Json] Response to Statement from W3C TAG Carsten Bormann
- Re: [Json] Response to Statement from W3C TAG Martin J. Dürst
- Re: [Json] Response to Statement from W3C TAG Carsten Bormann
- Re: [Json] Response to Statement from W3C TAG Allen Wirfs-Brock
- Re: [Json] Response to Statement from W3C TAG Bjoern Hoehrmann
- Re: [Json] Response to Statement from W3C TAG Allen Wirfs-Brock
- Re: [Json] Response to Statement from W3C TAG Brendan Eich
- Re: [Json] Response to Statement from W3C TAG Carsten Bormann
- Re: [Json] Response to Statement from W3C TAG Carsten Bormann
- Re: [Json] Response to Statement from W3C TAG Martin J. Dürst
- Re: [Json] Response to Statement from W3C TAG Pete Cordell
- Re: [Json] Response to Statement from W3C TAG Carsten Bormann
- Re: [Json] Response to Statement from W3C TAG Carsten Bormann
- Re: [Json] Response to Statement from W3C TAG Ladislav Lhotka
- Re: [Json] Response to Statement from W3C TAG Carsten Bormann
- Re: [Json] Response to Statement from W3C TAG James Clark
- Re: [Json] Response to Statement from W3C TAG Tim Bray
- Re: [Json] Response to Statement from W3C TAG Jacob Davies
- Re: [Json] Response to Statement from W3C TAG Bjoern Hoehrmann
- Re: [Json] Response to Statement from W3C TAG Allen Wirfs-Brock
- Re: [Json] Response to Statement from W3C TAG Allen Wirfs-Brock
- Re: [Json] Response to Statement from W3C TAG Allen Wirfs-Brock
- Re: [Json] Response to Statement from W3C TAG Allen Wirfs-Brock
- Re: [Json] Response to Statement from W3C TAG James Clark
- Re: [Json] Response to Statement from W3C TAG R S
- Re: [Json] Response to Statement from W3C TAG James Clark
- Re: [Json] Response to Statement from W3C TAG R S
- Re: [Json] Response to Statement from W3C TAG Carsten Bormann
- Re: [Json] Response to Statement from W3C TAG John Cowan
- Re: [Json] Response to Statement from W3C TAG Carsten Bormann
- Re: [Json] Response to Statement from W3C TAG Tim Bray
- Re: [Json] Response to Statement from W3C TAG Allen Wirfs-Brock
- Re: [Json] Response to Statement from W3C TAG Carsten Bormann
- Re: [Json] Response to Statement from W3C TAG John Cowan
- Re: [Json] Response to Statement from W3C TAG Martin J. Dürst
- Re: [Json] Response to Statement from W3C TAG Martin J. Dürst
- [Json] Data Model and Infoset (was: Re: Response … Martin J. Dürst
- [Json] object element order Manger, James
- Re: [Json] object element order Alexandre Morgaut
- Re: [Json] object element order Allen Wirfs-Brock
- Re: [Json] object element order Allen Wirfs-Brock
- Re: [Json] Response to Statement from W3C TAG Allen Wirfs-Brock
- Re: [Json] object element order Manger, James
- Re: [Json] object element order Allen Wirfs-Brock
- Re: [Json] object element order Julian Reschke
- [Json] JSON as an interoperability specification … Carsten Bormann
- Re: [Json] JSON as an interoperability specificat… John Cowan
- Re: [Json] object element order Allen Wirfs-Brock
- Re: [Json] object element order Nico Williams
- Re: [Json] object element order Tim Bray
- Re: [Json] object element order Stefan Drees
- Re: [Json] object element order Peter F. Patel-Schneider
- Re: [Json] object element order Matthew Morley