Re: [Rfc-markdown] 1.3.34: map most codeblock classes to <sourcecode> instead of <artwork>

Carsten Bormann <> Fri, 19 February 2021 08:46 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id E84233A0D4E for <>; Fri, 19 Feb 2021 00:46:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id wNy9MT4dRKPu for <>; Fri, 19 Feb 2021 00:46:02 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 13BF83A0D39 for <>; Fri, 19 Feb 2021 00:46:01 -0800 (PST)
Received: from [] ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPSA id 4DhlXm1m9fzyRB; Fri, 19 Feb 2021 09:46:00 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.\))
From: Carsten Bormann <>
In-Reply-To: <>
Date: Fri, 19 Feb 2021 09:45:59 +0100
X-Mao-Original-Outgoing-Id: 635417159.340462-e110aa66ee1b1dc926279df6f341d670
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <> <>
To: Julian Reschke <>
X-Mailer: Apple Mail (2.3608.
Archived-At: <>
Subject: Re: [Rfc-markdown] 1.3.34: map most codeblock classes to <sourcecode> instead of <artwork>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "rfc-markdown is a discussion list for people writing I-Ds and RFCs in Markdown and the authors of the tools used for that." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 19 Feb 2021 08:46:06 -0000

> FWIW, I'm not sure what the use case for not left-aligning source code is?

I had one just yesterday…

(In a normal publication I’d use color.)

> Slightly related to this: it seems we need to come up with
> recommendations about what is artwork and what is sourcecode. For
> instance, in the HTTP specs, is a HTTP message example (or a header
> field example) artwork or sourcecode?

I’d say:
Q: Is it meant for machine consumption?
No?  Artwork.


PEM, CBOR-diag, JSON data items that can be parsed: source code.
ABNF, CDDL, YANG: source code (but see example above)
Pseudocode, C, Python: source code

Math: artwork
Illustrative excerpts of code for human consumption: artwork
Call-flows (example in RFC 7991), HTTP interactions: artwork
UML stuff, MSCs, flow charts, GANTT charts: artwork

(Deliberately) Bad code (counterexamples): Hmm.

Grüße, Carsten