IETF Logo Mail Archive

Re: [Json] I-JSON Tpic #2: Top-Level

Carsten Bormann <cabo@tzi.org> Wed, 21 May 2014 06:16 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 E59B71A0286 for <json@ietfa.amsl.com>; Tue, 20 May 2014 23:16:37 -0700 (PDT)
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 IoImzFdtSBEa for <json@ietfa.amsl.com>; Tue, 20 May 2014 23:16:36 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5835D1A027C for <json@ietf.org>; Tue, 20 May 2014 23:16:36 -0700 (PDT)
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 s4L6GXLX022284 for <json@ietf.org>; Wed, 21 May 2014 08:16:33 +0200 (CEST)
Received: from [192.168.217.145] (p5489092F.dip0.t-ipconnect.de [84.137.9.47]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id CDC911B24; Wed, 21 May 2014 08:16:32 +0200 (CEST)
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <537BB89E.2040305@cisco.com>
Date: Wed, 21 May 2014 08:16:31 +0200
X-Mao-Original-Outgoing-Id: 422345791.482902-20866ad70f184d7f64f66719fce418ea
Content-Transfer-Encoding: quoted-printable
Message-Id: <3BF9B252-3CCD-4BC3-9F30-8634B483FAEE@tzi.org>
References: <535EB119.4000908@cisco.com> <CAHBU6itycQmqzAuxWyrFZ_v=fHdenm2csyAqtUGGu+vteh6=yQ@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E1154581E82F@WSMSG3153V.srv.dir.telstra.com> <CAHBU6iuqosV91W6CJyow_eaKdCNm_VOairJysuLS8mrWV+HM9g@mail.gmail.com> <ABB2BA00-6A21-4710-A1F5-49D4FB469E8F@vpnc.org> <CAK3OfOig8y5KpYZ86KrMPxrJOYC_hLBew_nmyneHCC2mXX+tag@mail.gmail.com> <537BB89E.2040305@cisco.com>
To: IETF JSON WG <json@ietf.org>
X-Mailer: Apple Mail (2.1878.2)
Archived-At: http://mailarchive.ietf.org/arch/msg/json/zLy6vW_mTB_CAkUpXQNm2Mx_SMU
Subject: Re: [Json] I-JSON Tpic #2: Top-Level
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, 21 May 2014 06:16:38 -0000

Restricting I-JSON to top-level objects only, would immediately make JCard (RFC 7095) and JCal (draft-ietf-jcardcal-jcal-10.txt, in RFC-EDITOR state) non-I-JSON.

Since these are significant IETF efforts, that would make me unhappy.

(I don’t have an opinion yet whether I-JSON should restrict itself to RFC 4627 JSON, i.e. objects and arrays, or should embrace the ECMA-404/RFC 7159 extension.  Both sides have quite good arguments for them.)

Grüße, Carsten

v2.30.2 | Report a Bug | By Email | System Status