IETF Logo Mail Archive

[rfc-i] inline elements

Peter Saint-Andre <stpeter@stpeter.im> Tue, 15 March 2022 14:27 UTC

Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74DB63A0B1E; Tue, 15 Mar 2022 07:27:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.461
X-Spam-Level:
X-Spam-Status: No, score=-2.461 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.248, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=stpeter.im header.b=G7opSy7W; dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=messagingengine.com header.b=n+32U7/C
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 MUudtxK0J9VW; Tue, 15 Mar 2022 07:27:04 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B5E0E3A0B5B; Tue, 15 Mar 2022 07:27:04 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 0D8D3F0FDD; Tue, 15 Mar 2022 07:27:04 -0700 (PDT)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 9A6A8F5CF8 for <rfc-interest@rfc-editor.org>; Tue, 15 Mar 2022 07:27:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=stpeter.im header.b=G7opSy7W; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=n+32U7/C
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cN9LBh9fMjZX for <rfc-interest@rfc-editor.org>; Tue, 15 Mar 2022 07:26:57 -0700 (PDT)
Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) by rfc-editor.org (Postfix) with ESMTPS id DB182AE8B for <rfc-interest@rfc-editor.org>; Tue, 15 Mar 2022 07:26:57 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id 9FE4D3201DFB; Tue, 15 Mar 2022 10:26:56 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Tue, 15 Mar 2022 10:26:56 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=stpeter.im; h=cc :content-transfer-encoding:content-type:date:date:from:from :in-reply-to:message-id:mime-version:reply-to:sender:subject :subject:to:to; s=fm2; bh=0knv++XhE1n8O2KlANNdp+aAEf67bn1U9guZ8b Iq4o0=; b=G7opSy7W5jrcKtid2pwU9U1bW6eIlT3i/++jl6zQ43ii4Sn+vcIY6g wFKV+GjksudmjtcGv/SlMbW+HjJOtEV1z8nWgqHDUKR+Io33GAL9FsCykqSjvs+1 1aR/gsenlQ1+3jcFY0eAlwA86nRddYI9u4NPbyiMos+1W5w5Z/CKWufj48vFdOeB 3XTMgCq0x2qVynjSYdFFG8CCSA7E7sWvoaoXKHQEWNbylgvM/vBE7pXleaQeDANO qnP6zhZqcUVkJqKK+/XgFGsny1XwnYtl0ZT0qTcZWRUSf+Y2KcF+6EY8VOseB6SO +xT5aAhwveasCPCjBqjOqfVoMfQdK27w==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:date:from:from:in-reply-to:message-id:mime-version :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=0knv++XhE1n8O2KlA NNdp+aAEf67bn1U9guZ8bIq4o0=; b=n+32U7/CiEWdIYbmgJXs9vmytZe7rhVfu bqwyqdnG++tH2LTzOa6CjR2QFlFs8IkbCxiCqiR/CP9ynysAFIP+rXKKViiSjN1E vypntGNE1F3DOzQ0+fWf951BxNKN5F574Cgn0geZTzv0O24lgs57gNbCo/sIQ0X8 22mT/qLLlRY12F4tzkkY9AzsU1PyeuMT0r79qKCeHlnXLo4ekN4sq+HFWt8ReHhH 4oEQW4yRCg0tAKyUyNrkKrYCd56qScPgxyirDNNgsqzKhw03RgZCJ4V+ZEU6fOTC 6d2leSJBtJJWzgE+P5ZSmDlb0Gl2CHqLvk13uQKUOdiM5/1Wqszdw==
X-ME-Sender: <xms:L6IwYk-vatR3tBHKsNOP1VGlq2AjL7bb5XcsKpjZbw-iygnqYWQi7w> <xme:L6IwYsu6t7Ho4B0aZTuCnyMs_NrOinkDe2x0qMnGxLdELKAZB6mw9_QYW0dNV4ny3 ghDH9cV553TWmuQbg>
X-ME-Received: <xmr:L6IwYqBCkfEuCbOZgwV0Ailsg2Vs9qokBnAYjn8t0r4YzRTTi2p5CT-SGwdWc3yj8qxgL11Q_G-Q1toHAYBSEl7JNILvBXjpRviLkWw>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrudeftddgieefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfvffhufgtgfesthejredttdefjeenucfhrhhomheprfgvthgvrhcu ufgrihhnthdqtehnughrvgcuoehsthhpvghtvghrsehsthhpvghtvghrrdhimheqnecugg ftrfgrthhtvghrnhepudfghfejledufeevhedvtdehleekheevleduieeigfdvtdfgffeu ieffkedvhfeunecuffhomhgrihhnpehgihhthhhusgdrtghomhenucevlhhushhtvghruf hiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehsthhpvghtvghrsehsthhpvght vghrrdhimh
X-ME-Proxy: <xmx:L6IwYkeKGM11ArtL_uWLwYVm_GacHtbgIRhQfs_C7Y1yk8aii425wg> <xmx:L6IwYpNuZqeXtpGYfndZx07bKI72gotSlRE6V4AwGOuTSzPOG9YqFg> <xmx:L6IwYunCXzgvsuZwrzZGx2m9Q8UsRWBPoq_JF_hgK0XvZAdkTV0niw> <xmx:MKIwYrUTiIXJIxbKKI2jB9wrFTFhHMG-KOmf4Y5Zb2N1saUhSt-bSg>
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 15 Mar 2022 10:26:55 -0400 (EDT)
Message-ID: <b6084aae-d20a-cb8e-dbb9-a6691a4f8223@stpeter.im>
Date: Tue, 15 Mar 2022 08:26:50 -0600
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.7.0
Content-Language: en-US
To: RFC Interest <rfc-interest@rfc-editor.org>
From: Peter Saint-Andre <stpeter@stpeter.im>
Subject: [rfc-i] inline elements
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

Last year I promised [1] to look into some consistency issues in the v3 
XML vocabulary (with reference to RFC 7991 and draft-iab-rfc7991bis). 
I've finally found time to do so and will divide my report into several 
threads.

For the first thread, there's the relatively simple matter of the 
"inline elements" that are used within textual elements such as <li> or 
<t> alongside running text. As far as I can see, these inline elements 
are [2] as follows:

<bcp14>
<contact> (new in 7991bis, see [3])
<cref>
<em>
<eref>
<iref>
<relref>
<strong>
<sub>
<sup>
<tt>
<u> (new in 7991bis, I can't find a good pointer for it but it's 
documented in xml2rfc and will be in the next version of 7991bis)
<xref>

Also as far as I can see, all of these inline elements can be included 
as children of the following elements (with no recursion, e.g., it's not 
allowed to include <sub> directly within <sub>):

<annotation>
<blockquote>
<cref> (see below)
<dd>
<dt>
<em>
<li>
<name>
<refcontent> (see below)
<strong>
<sub> (see below)
<sup> (see below)
<t>
<td>
<th>

There are a few anomalies:

- <cref> does not allow <bcp14> or <iref> but this might not matter 
because <cref> is intended for comments only in work-in-progress documents

- <refcontent> does not allow <cref>, <eref>, <iref>, <relref>, or 
<xref> but I suppose this makes sense because there's already a 
reference involved

- <strong> (and perhaps other elements?) does not allow <u> [4]

- <sub> does not allow <sup> and <sup> does not allow <sub> but this 
will be fixed in 7991bis [5]

The descriptive text and the Relax NG schema in 7991bis might need to be 
modified to reflect the foregoing state of things, although John Levine 
has been working on 7991bis [6] so perhaps he's ahead of us.

Corrections are welcome.

Peter

[1] https://github.com/rfc-format/draft-iab-xml2rfc-v3-bis/issues/200

[2] The v2 vocabulary also defined <br>, <spanx>, and <vspace> but I 
believe those elements have been deprecated.

[3] https://github.com/rfc-format/draft-iab-xml2rfc-v3-bis/issues/185

[4] https://github.com/rfc-format/draft-iab-xml2rfc-v3-bis/issues/205

[5] https://github.com/rfc-format/draft-iab-xml2rfc-v3-bis/issues/193

[6] https://github.com/rfc-format/draft-iab-xml2rfc-v3-bis
_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest

v2.23.0 | Report a Bug | By Email