Re: [Rfc-markdown] bcp14, was: [xml2rfc-dev] New xml2rfc release: v2.25.0

Dave Lawrence <tale@dd.org> Mon, 26 August 2019 23:06 UTC

Return-Path: <tale@dd.org>
X-Original-To: rfc-markdown@ietfa.amsl.com
Delivered-To: rfc-markdown@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31DC9120F02; Mon, 26 Aug 2019 16:06:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-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 ixC_BT29JFbg; Mon, 26 Aug 2019 16:06:25 -0700 (PDT)
Received: from gro.dd.org (host2.dlawren-3-gw.cust.sover.net [207.136.201.30]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C86BC120EE0; Mon, 26 Aug 2019 16:06:25 -0700 (PDT)
Received: by gro.dd.org (Postfix, from userid 102) id 230AC10D626; Mon, 26 Aug 2019 19:06:25 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <23908.26097.125524.792528@gro.dd.org>
Date: Mon, 26 Aug 2019 19:06:25 -0400
From: Dave Lawrence <tale@dd.org>
To: xml2rfc-dev@ietf.org, xml2rfc@ietf.org, rfc-markdown@ietf.org
In-Reply-To: <07f24586-9540-5170-e11c-9fca3c858b73@gmx.de>
References: <E1i2EMD-0002SA-UW@durif.tools.ietf.org> <22880345-a324-8dfd-a08c-e8ec89aeb9b5@gmx.de> <20190826144520.GA19037@miek.nl> <40d507f2-ed78-e09f-ae96-c64333a91547@levkowetz.com> <07f24586-9540-5170-e11c-9fca3c858b73@gmx.de>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/jNOwjx7ysiCfQZmCrfULJBH1wt8>
Subject: Re: [Rfc-markdown] bcp14, was: [xml2rfc-dev] New xml2rfc release: v2.25.0
X-BeenThere: rfc-markdown@ietf.org
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." <rfc-markdown.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-markdown/>
List-Post: <mailto:rfc-markdown@ietf.org>
List-Help: <mailto:rfc-markdown-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Aug 2019 23:06:27 -0000

Julian Reschke writes:
> If the sole reason for this change is to avoid breaking up MUST_NOT (and
> friends), why not hard-wire that into the renderers (for HTML, I believe
> it could be done with CSS...)?

And I readily admit I might have missed a memo, but if that is the
sole reason then how did we arrive at the conclusion that they needed
to be inseparable?