Re: [Json] sourcecode type="json"
John Levine <johnl@taugh.com> Wed, 27 October 2021 00:36 UTC
Return-Path: <johnl@iecc.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 67BEE3A1970 for <json@ietfa.amsl.com>; Tue, 26 Oct 2021 17:36:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.85
X-Spam-Level:
X-Spam-Status: No, score=-1.85 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=URXDVqTk; dkim=pass (2048-bit key) header.d=taugh.com header.b=yd0iRuVF
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 zSCQBMVqH2si for <json@ietfa.amsl.com>; Tue, 26 Oct 2021 17:36:12 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 2167A3A0908 for <json@ietf.org>; Tue, 26 Oct 2021 17:36:11 -0700 (PDT)
Received: (qmail 32007 invoked from network); 27 Oct 2021 00:36:08 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=7d02.61789ef8.k2110; bh=nqkpUKGOzkRsufiz3mTOy3i+kPBAK8YCQCKdHNwnXFs=; b=URXDVqTkOnJuQ2pG3ZvJydrxX6hZck0l7rpBdt7mGshVNynq5sYFZJbUnCQmIlmxe2CUBfOY9w4ByCZpubKx+suoEit8RLBI/CTiQoalFHoEQULNLs2/FpsyZioY4k9P1yPLDJHvT2/1DbDTIqnL2nYyjhI6unjyuPTtAmi94TrZ0PpJAOSSq7CDZTiXUTdUfs8hBot5oLXIfVbHdNEpKRUVuah6Si5wDXfFG7nURk5v0LapKowxCLfkVACYv/p2rJJ90aVJM4onrkNdrHoMM/uPsJ5uN5BVFGTNaUb4ugLegI+KuX4JRqk5x7N58B/W50BNw/kJyeO8J9vAByT/HA==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=7d02.61789ef8.k2110; bh=nqkpUKGOzkRsufiz3mTOy3i+kPBAK8YCQCKdHNwnXFs=; b=yd0iRuVFFbl8sg5gRSWT+8kkcAIwcW/C0++Ya40lQdIrDD7SookZVuewYyGYpWgnXpG0kL3EoHOZD7pqJUaPpkQ/z5i6HgcEdB5eaSUSLDpkBnQe/N0mZoP9E/JrZcIq+PGoH5QcmhKUDt85C98CtIq0IObrVQ9P3t0sFOksPoEJsQvAZSOgG3nneM6GcAxKbMYJtxSKFmr14W4sWBES+BuyCu46Kucmi8EvP7kRT77fJ+1NXgXevYkqj83l9CJtlW2edxDQhAnJ6E1faa9NWIV74l4jS2ykOS3aARVMYw4ZoTQeY1p+az9izXL2Hb/JO0Mq+PC0dGXcV8g5FeqQ3A==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 27 Oct 2021 00:36:07 -0000
Received: by ary.qy (Postfix, from userid 501) id 5C4472E60559; Tue, 26 Oct 2021 20:36:05 -0400 (EDT)
Date: Tue, 26 Oct 2021 20:36:05 -0400
Message-Id: <20211027003607.5C4472E60559@ary.qy>
From: John Levine <johnl@taugh.com>
To: rfc-interest@rfc-editor.org, json@ietf.org
Cc: mnot@mnot.net
In-Reply-To: <58E80F54-FABD-4AF3-8885-B70E070360F2@mnot.net>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/OQBZuan7ySTF5j4qgHVp7kPVJ_Q>
Subject: Re: [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: Wed, 27 Oct 2021 00:36:18 -0000
It appears that Mark Nottingham <mnot@mnot.net> said: >For http, we use 'http-message', which is defined to be either a full *or* partial message. Remember, this is not a media type... Right. We have lots of sourcecode which is a chunk of a program, not a full program. If it's a chunk of JSON, call it JSON. R's, John >> 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?
- [Json] sourcecode type="json" Carsten Bormann
- Re: [Json] sourcecode type="json" Pete Cordell
- Re: [Json] sourcecode type="json" Mark Nottingham
- Re: [Json] sourcecode type="json" John Levine
- Re: [Json] [rfc-i] sourcecode type="json" Carsten Bormann
- Re: [Json] [rfc-i] sourcecode type="json" John Levine