[xml2rfc] Embedded lists in V3 syntax

"David R. Oran" <daveoran@orandom.net> Mon, 26 April 2021 18:31 UTC

Return-Path: <daveoran@orandom.net>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF61D3A2BFE for <xml2rfc@ietfa.amsl.com>; Mon, 26 Apr 2021 11:31:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.889
X-Spam-Level:
X-Spam-Status: No, score=-1.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_SPF_HELO_TEMPERROR=0.01, URIBL_BLOCKED=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 WsS8OBuenxEC for <xml2rfc@ietfa.amsl.com>; Mon, 26 Apr 2021 11:31:45 -0700 (PDT)
Received: from spark.crystalorb.net (spark.crystalorb.net [IPv6:2607:fca8:1530::c]) (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 7A9033A2BFB for <xml2rfc@ietf.org>; Mon, 26 Apr 2021 11:31:45 -0700 (PDT)
Received: from [192.168.15.102] ([IPv6:2601:184:407f:9004:fc7e:bbfc:6d27:9577]) (authenticated bits=0) by spark.crystalorb.net (8.14.4/8.14.4/Debian-4+deb7u1) with ESMTP id 13QIVfxx032047 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NO) for <xml2rfc@ietf.org>; Mon, 26 Apr 2021 11:31:43 -0700
From: "David R. Oran" <daveoran@orandom.net>
To: xml2rfc <xml2rfc@ietf.org>
Date: Mon, 26 Apr 2021 14:31:35 -0400
X-Mailer: MailMate (1.14r5757)
Message-ID: <B82E621C-0475-42BD-BFE7-C3717A2DDACC@orandom.net>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_488C88CA-BCD5-4554-8C0B-95180E424470_="
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/w44EilxCMhzmHHgoEFByP5s97X4>
Subject: [xml2rfc] Embedded lists in V3 syntax
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Apr 2021 18:31:51 -0000

I was trying to get an <ol> inside a <ul> and tried the obvious approach 
of just putting the <ol> after one of the <li>’s of the <ul>.

That caused xml2rfc to barf, so I went googling around, looked at the 
FAQ and RFC7991. This would seem a common-enough situation that one 
would think it covered in the documentation, but there was nothing in 
the FAQ about multi-level lists (even to say “don’t do it”).

Then I found 
https://greenbytes.de/tech/webdav/draft-hoffman-rfcexamples-latest.html#v3-basic 
and that had a list inside a list so I thought I had found a solution.

So I tried that and of course it didn’t work. On closer examination, 
the V3 source had a naked </t> without a matching <t>, so I thought - 
this can’t be right!

So, just to be sure, I extracted the xml source from the web page myself 
and tried to compile it. D’oh…it causes xml2rfc to barf.

So, I think we have a few issues/questions this raises:

1. How the heck do you embed one list inside another?
2. If this isn’t allowed, something in the FAQ ought to warn you off
3. If it is allowed, the FAQ should show you how with one or more 
examples
4. 
https://greenbytes.de/tech/webdav/draft-hoffman-rfcexamples-latest.html#v3-basic 
ought to get fixed or deprecated somehow.

DaveO