IETF Logo Mail Archive

[Json] sourcecode type="json"

Carsten Bormann <cabo@tzi.org> Tue, 26 October 2021 19:26 UTC

Return-Path: <cabo@tzi.org>
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 2692F3A1764; Tue, 26 Oct 2021 12:26:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 lvJL7Cqu0HxI; Tue, 26 Oct 2021 12:26:41 -0700 (PDT)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::15]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B6E83A1761; Tue, 26 Oct 2021 12:26:41 -0700 (PDT)
Received: from [192.168.217.118] (p5089a10c.dip0.t-ipconnect.de [80.137.161.12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4Hf1yy17Ghz2xHl; Tue, 26 Oct 2021 21:26:34 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
Date: Tue, 26 Oct 2021 21:26:33 +0200
Cc: asdf@ietf.org
X-Mao-Original-Outgoing-Id: 656969193.780653-b7321c559521a863ad9799de32e36238
Content-Transfer-Encoding: quoted-printable
Message-Id: <13AB383A-D467-400F-B48D-A0EC6B6D82AA@tzi.org>
To: json@ietf.org, rfc-interest <rfc-interest@rfc-editor.org>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/UQu7zJaGvs0OBvcHA9Zzuu5UG2U>
Subject: [Json] sourcecode type="json"
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 26 Oct 2021 19:26:46 -0000

https://www.ietf.org/archive/id/draft-ietf-asdf-sdf-08.html

includes a number of JSON examples, or at least it claims so.

We created 15 examples that are marked »<sourcecode type=“json”>«.  Of these, 3 are JSON, and 12 are a single member (or two) without surrounding braces, meant to be put into larger JSON objects.

E.g.:
https://www.ietf.org/archive/id/draft-ietf-asdf-sdf-08.html#section-3.2-6

These braces can of course be added, but they are really noise distracting from the content that is in these members (and the objects formed this way may be valid JSON, but they usually aren’t valid SDF).

Should we introduce a new sourcecode type “json-members”?
Or should we bite the bullet and add the noise to get real JSON texts?

Grüße, Carsten

v2.23.0 | Report a Bug | By Email