Re: [Json] Call for WG Consensus to Adopt I-JSON as a WG Item in the Charter
Bjoern Hoehrmann <derhoermi@gmx.net> Sat, 15 March 2014 16:17 UTC
Return-Path: <derhoermi@gmx.net>
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 606121A00F3 for <json@ietfa.amsl.com>; Sat, 15 Mar 2014 09:17:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level:
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.547, SPF_PASS=-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 wctjEx0VKKX3 for <json@ietfa.amsl.com>; Sat, 15 Mar 2014 09:17:15 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) by ietfa.amsl.com (Postfix) with ESMTP id 9EE241A00C3 for <json@ietf.org>; Sat, 15 Mar 2014 09:17:14 -0700 (PDT)
Received: from netb ([89.204.139.147]) by mail.gmx.com (mrgmx102) with ESMTPSA (Nemesis) id 0LjuR3-1X0ezF3LcP-00bpkT; Sat, 15 Mar 2014 17:16:47 +0100
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: John Cowan <cowan@mercury.ccil.org>
Date: Sat, 15 Mar 2014 17:16:43 +0100
Message-ID: <72u8i9dj6ih7o95cibq44o8kuq8k2dm40l@hive.bjoern.hoehrmann.de>
References: <53238F21.2030508@cisco.com> <nll8i999lis5u0f719iv6bgte71d8uus52@hive.bjoern.hoehrmann.de> <20140315143553.GC30147@mercury.ccil.org>
In-Reply-To: <20140315143553.GC30147@mercury.ccil.org>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Provags-ID: V03:K0:BbZEfBSMn73AE2x+cjYr94rtsXaGI+38KP9jI//lCmnuax3cw0V BCyljkSpsGzmc8EayuQLoKnkb+rsqtiIagE2IL8jWBzVO1MYuIu1fUxe+p4OLmMXbP2Qy5l oZMFdKSMIZJrKHUYH3vr77kGEbmiYFmuI9Bs2FHENVcwIsQzpS33EzId8kSEc37ghGcUs2k mbAbuA7xUFs53aGtBMl2Q==
Archived-At: http://mailarchive.ietf.org/arch/msg/json/bDO2PpmyWSNIHaky-0Plp5re6ns
Cc: Matt Miller <mamille2@cisco.com>, IETF JSON WG <json@ietf.org>
Subject: Re: [Json] Call for WG Consensus to Adopt I-JSON as a WG Item in the Charter
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: Sat, 15 Mar 2014 16:17:17 -0000
* John Cowan wrote: >Bjoern Hoehrmann scripsit: > >> No, not without changing the nature of the document considerably. These >> are just best practises and not a separate format with its own name. > >The idea, I think, is that if the receiver sees the new name it can make >more stringent assumptions about the input. Indeed, given a name, certain >receivers can say they will *only* accept I-JSON. It is analogous to the >"strict" declaration in JavaScript (or Perl, for that matter). For human-readable documentation purposes it is entirely sufficient to say "follows RFC XXXX conventions" and implementations can just assume the conventions are being followed until they detect otherwise (which "I-JSON" implementations are required to do as currently proposed). -- Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de 25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/
- Re: [Json] Call for WG Consensus to Adopt I-JSON … Nico Williams
- Re: [Json] Call for WG Consensus to Adopt I-JSON … Tony Hansen
- [Json] Call for WG Consensus to Adopt I-JSON as a… Matt Miller
- Re: [Json] Call for WG Consensus to Adopt I-JSON … Tim Bray
- Re: [Json] Call for WG Consensus to Adopt I-JSON … John Cowan
- Re: [Json] Call for WG Consensus to Adopt I-JSON … Phillip Hallam-Baker
- Re: [Json] Call for WG Consensus to Adopt I-JSON … Nat Sakimura
- Re: [Json] Call for WG Consensus to Adopt I-JSON … Dave Cottlehuber
- Re: [Json] Call for WG Consensus to Adopt I-JSON … John Levine
- Re: [Json] Call for WG Consensus to Adopt I-JSON … Martin J. Dürst
- Re: [Json] Call for WG Consensus to Adopt I-JSON … Stefan Drees
- Re: [Json] Call for WG Consensus to Adopt I-JSON … Bjoern Hoehrmann
- Re: [Json] Call for WG Consensus to Adopt I-JSON … John Cowan
- Re: [Json] Call for WG Consensus to Adopt I-JSON … Bjoern Hoehrmann
- Re: [Json] Call for WG Consensus to Adopt I-JSON … Tim Bray
- Re: [Json] Call for WG Consensus to Adopt I-JSON … John Cowan
- Re: [Json] Call for WG Consensus to Adopt I-JSON … Bjoern Hoehrmann
- Re: [Json] Call for WG Consensus to Adopt I-JSON … Larry Masinter
- Re: [Json] Call for WG Consensus to Adopt I-JSON … Phillip Hallam-Baker
- Re: [Json] Call for WG Consensus to Adopt I-JSON … Nico Williams
- Re: [Json] Call for WG Consensus to Adopt I-JSON … Phillip Hallam-Baker