Re: [Rfc-markdown] [rfc-i] [Tools-discuss] Tool to convert TXT to RFCXML

Jay Daley <exec-director@ietf.org> Mon, 17 July 2023 09:35 UTC

Return-Path: <jay@staff.ietf.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 BDC8DC152561 for <rfc-markdown@ietfa.amsl.com>; Mon, 17 Jul 2023 02:35:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level:
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ietf-org.20221208.gappssmtp.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wyxxuGzudIZ5 for <rfc-markdown@ietfa.amsl.com>; Mon, 17 Jul 2023 02:35:37 -0700 (PDT)
Received: from mail-wm1-x32b.google.com (mail-wm1-x32b.google.com [IPv6:2a00:1450:4864:20::32b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A2785C1522CB for <rfc-markdown@ietf.org>; Mon, 17 Jul 2023 02:35:37 -0700 (PDT)
Received: by mail-wm1-x32b.google.com with SMTP id 5b1f17b1804b1-3fbf1b82de7so25764045e9.1 for <rfc-markdown@ietf.org>; Mon, 17 Jul 2023 02:35:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ietf-org.20221208.gappssmtp.com; s=20221208; t=1689586536; x=1692178536; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:from:to:cc:subject:date:message-id:reply-to; bh=gAnUbgltZDCjdq1BeDWvnp7ueonNwlEwas+ORyb1vJA=; b=qn3O8DD+1ZaO8bkzhas/JBACGaarMAZy/O0UauNg/qrXh0FERr4I0cRBo0SoYBFlUk IIdMhSwGrazw0os9W6JFDbLsGGOKT+Bf7jln2ev7kAxbOYrG+UwxoYVsJBImpibx+wcL pZVNprSWtQryqkx8xY2Sotb/uSqQjZkD+M6bEA5+L3k88w7tG9K9hyRljW56OkG4DUnH bXQSukUqtcy6BczWRNEWvnG9ROQh1DUsHebPKxouwMT5uExqAmI1e+8jq/1o11++Ai+k Eg5ulUGiWshWyHsqRgeD3WOPPAxTBW50m7Zsqm5YV4XKz92EtKfDWvOsbAh8IFnZl5Ub ItbQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1689586536; x=1692178536; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=gAnUbgltZDCjdq1BeDWvnp7ueonNwlEwas+ORyb1vJA=; b=LFG2NgYlfhoHakRFv46iymJVhPv0Ti/GI4uUZCiy7kOYrpRZMy81XOJTnrRd+jkeDL UFmSifNH+7pny2/0dcejNzNjGFXyfrmo85vidZL0PN8y58k54m4L/wTIyn6d5sFcDyBh Gu4ynC4q4qCXhJqbTvuRQBHv1m6mwl5R2/Vw5kvDjQcc0T5ZU8iiEy+OKEfHsZ8lWGce 1VRKijnpSsFPYOkCaFE1aEGazxpK5T3fpP6uqMwRo3lKBSHnoohSQaG/YXRFeDv8uunD cqxu7Kk6xgg0WTikG7UL83y1nnk3QKBuDYi+GTxPihBVPKydA3vsUroLGcfP2Aq0nqDd t9OA==
X-Gm-Message-State: ABy/qLbesW56KyKHp739adMVkD8Otif2F0rjR9A6XT1o/Cu7gU6s5NGW PmsO/iOoZ9i/JSOFhlSvUMgZb8Lm
X-Google-Smtp-Source: APBJJlFfW/aNRvGUnRhPTKL8raaubgr0eoNY/16nrt01A7KIV+NxoaiskE2DTKwJuas5qnPi6OFrEg==
X-Received: by 2002:a05:600c:2153:b0:3f7:c92:57a0 with SMTP id v19-20020a05600c215300b003f70c9257a0mr7639799wml.14.1689586535939; Mon, 17 Jul 2023 02:35:35 -0700 (PDT)
Received: from smtpclient.apple (host-92-27-125-209.static.as13285.net. [92.27.125.209]) by smtp.gmail.com with ESMTPSA id y22-20020a7bcd96000000b003fa8dbb7b5dsm7589775wmj.25.2023.07.17.02.35.35 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 17 Jul 2023 02:35:35 -0700 (PDT)
From: Jay Daley <exec-director@ietf.org>
Message-Id: <E960579F-0750-471B-8729-8A59E89735D5@ietf.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_1E7C5184-56DF-43EE-9025-EFE730B62F71"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.600.7\))
Date: Mon, 17 Jul 2023 10:35:24 +0100
In-Reply-To: <d76f7ddf-46ae-4046-a1e0-9499da86e700@betaapp.fastmail.com>
Cc: Carsten Bormann <cabo@tzi.org>, "Julian F. Reschke" <julian.reschke@gmx.de>, rfc-markdown@ietf.org, RFC Interest <rfc-interest@rfc-editor.org>
To: Martin Thomson <mt@lowentropy.net>
References: <CABXxEz97ZDeHhtMeX6CwX842d=s9CXfUtG5DFWpxNKbtBcoW6Q@mail.gmail.com> <CAD2=Z86=DyfT0Fp23DqdCyz32Od4uhAhA48K=pst64eZ+CS8NA@mail.gmail.com> <CABXxEz-KC5Nayv=KMce9mDi_ngu9J8PY1-pAbMUBypxEX2Pw8Q@mail.gmail.com> <430B62BB-45BB-4ECF-812F-39E84926CFA7@tzi.org> <CABXxEz-_6MV0P9sc=GBJw+eReFpLZC2vDFFvo9katc1ECwpyRw@mail.gmail.com> <9f95474b-c049-2e5a-1cfd-f3e9ebf48e2d@gmx.de> <fe96fb1a-1c56-4416-b937-b0b66c38ae71@betaapp.fastmail.com> <66ef1749-f4b1-51af-8e08-06eb58a9005a@gmx.de> <869922F5-DA96-40DB-A749-32E801A1A632@tzi.org> <d76f7ddf-46ae-4046-a1e0-9499da86e700@betaapp.fastmail.com>
X-Mailer: Apple Mail (2.3731.600.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/WRViDyr8toTS8isrZTiiq45YJ7g>
Subject: Re: [Rfc-markdown] [rfc-i] [Tools-discuss] Tool to convert TXT to RFCXML
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.39
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, 17 Jul 2023 09:35:41 -0000


> On 17 Jul 2023, at 08:58, Martin Thomson <mt@lowentropy.net> wrote:
> 
> On Mon, Jul 17, 2023, at 16:47, Carsten Bormann wrote:
>> * add <nobr or similar to RFCXML, so we don’t have to play the 
>> character substitution games.
> 
> This.  The way HTML does it is with CSS directives[1].  There is a lot of control over this through CSS, though for annoying reasons wrapping is still not fully specified.
> 
> For our purposes, it seems like a simple <nobr>...</nobr> element would be fine.  (Which leads me to ponder a new kramdown extension whereby words could be automatically wrapped in various span-level elements to ensure consistent styling for keywords...)

A word of caution.  The authoring markup languages are being pulled in two different directions and if that is not well managed then I fear we will end up with an even more complex way of working than exists now.  Those two directions are - does the markup represent formatting or does the markup represent semantics.  As I understand it, the original consensus design goal was to prioritise the representation of semantics.  i.e. not to prevent the formatting, but to capture the semantics first and then add finer grained formatting to that,

If we approach this specific issue from the semantic perspective then that would better be served by adding a new element, such as <term> … </term> that is intended to represent a technical term used inline in any body text and which therefore must remain as an atomic whole. 

We could then add finer grained semantic control that also leads to different formatting with <term type="maths"> or <term type="console"> etc.

Direct formatting could be achieved by allowing it to appear inside <tt> <em> etc, (though <tt> in my view is a mistake because it so obviously has clear semantic usages)

To be clear, this is not a full proposal. It’s too verbose and it doesn’t consider the existing <dt> and how that relates if at all.

Jay

> 
> [1] https://developer.mozilla.org/en-US/docs/Web/CSS/white-space in particular.
> 
> _______________________________________________
> Rfc-markdown mailing list
> Rfc-markdown@ietf.org
> https://www.ietf.org/mailman/listinfo/rfc-markdown

-- 
Jay Daley
IETF Executive Director
exec-director@ietf.org