Re: [xml2rfc-dev] [Ext] RFC 7991 issue #35: <li> can't contain a block quote

Paul Hoffman <paul.hoffman@icann.org> Wed, 03 October 2018 23:20 UTC

Return-Path: <paul.hoffman@icann.org>
X-Original-To: xml2rfc-dev@ietfa.amsl.com
Delivered-To: xml2rfc-dev@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1CFB12F295 for <xml2rfc-dev@ietfa.amsl.com>; Wed, 3 Oct 2018 16:20:57 -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_PASS=-0.001, 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 93b2Rpm15qom for <xml2rfc-dev@ietfa.amsl.com>; Wed, 3 Oct 2018 16:20:56 -0700 (PDT)
Received: from out.west.pexch112.icann.org (out.west.pexch112.icann.org [64.78.40.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EEE72126F72 for <xml2rfc-dev@ietf.org>; Wed, 3 Oct 2018 16:20:55 -0700 (PDT)
Received: from PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) by PMBX112-W1-CA-2.pexch112.icann.org (64.78.40.23) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Wed, 3 Oct 2018 16:20:53 -0700
Received: from PMBX112-W1-CA-1.pexch112.icann.org ([64.78.40.21]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([64.78.40.21]) with mapi id 15.00.1367.000; Wed, 3 Oct 2018 16:20:53 -0700
From: Paul Hoffman <paul.hoffman@icann.org>
To: XML Developer List <xml2rfc-dev@ietf.org>
Thread-Topic: [Ext] [xml2rfc-dev] RFC 7991 issue #35: <li> can't contain a block quote
Thread-Index: AQHUW287fiNrVnOdUEmIW02STMsMvKUOne+A
Date: Wed, 3 Oct 2018 23:20:53 +0000
Message-ID: <EBA82C17-A4D1-4CE8-B2B2-796B6EB90223@icann.org>
References: <39D3AA2F-E6C0-4648-9764-9ADE7644477E@icann.org>
In-Reply-To: <39D3AA2F-E6C0-4648-9764-9ADE7644477E@icann.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.0.32.234]
Content-Type: multipart/signed; boundary="Apple-Mail=_6196B9AE-BD87-4643-A795-7F3E3E62CB2D"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/MqvA4ItlwgYuF7gjb9FVuiXSoNk>
Subject: Re: [xml2rfc-dev] [Ext] RFC 7991 issue #35: <li> can't contain a block quote
X-BeenThere: xml2rfc-dev@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." <xml2rfc-dev.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc-dev/>
List-Post: <mailto:xml2rfc-dev@ietf.org>
List-Help: <mailto:xml2rfc-dev-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Oct 2018 23:20:58 -0000

> The <li> element https://tools.ietf.org/html/rfc7991#section-2.29 can contain quite a bit of block elements, except <blockquote> (among others I think). Why?
> 
> In v2 xml ones usually works around this by mimicking the layout by abusing another element. Seems strange to do this here as well.

If I remember correctly, the idea was that list items are already indented, and indenting blockquotes in a list item might cause weird output. In retrospect, that doesn't seem like a great argument.

Does anyone still want to prohibit blockquotes in <li>?

--Paul Hoffman