Re: [xml2rfc-dev] [Ext] Re: [xml2rfc] [Rfc-markdown] <br> is back, was: New xml2rfc release: v2.32.0

Paul Hoffman <paul.hoffman@icann.org> Tue, 08 October 2019 16:55 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 33D2312004C for <xml2rfc-dev@ietfa.amsl.com>; Tue, 8 Oct 2019 09:55:20 -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 Zk6bCF0v13-J for <xml2rfc-dev@ietfa.amsl.com>; Tue, 8 Oct 2019 09:55:18 -0700 (PDT)
Received: from ppa4.dc.icann.org (ppa4.dc.icann.org [192.0.46.77]) (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 86C6F120018 for <xml2rfc-dev@ietf.org>; Tue, 8 Oct 2019 09:55:18 -0700 (PDT)
Received: from PFE112-CA-1.pexch112.icann.org (out.west.pexch112.icann.org [64.78.40.7]) by ppa4.dc.icann.org (8.16.0.27/8.16.0.27) with ESMTPS id x98GtC9i026240 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Tue, 8 Oct 2019 16:55:12 GMT
Received: from PMBX112-W1-CA-2.pexch112.icann.org (64.78.40.23) by PMBX112-W1-CA-2.pexch112.icann.org (64.78.40.23) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 8 Oct 2019 09:55:10 -0700
Received: from PMBX112-W1-CA-2.pexch112.icann.org ([64.78.40.23]) by PMBX112-W1-CA-2.PEXCH112.ICANN.ORG ([64.78.40.23]) with mapi id 15.00.1473.005; Tue, 8 Oct 2019 09:55:10 -0700
From: Paul Hoffman <paul.hoffman@icann.org>
To: "xml2rfc-dev@ietf.org" <xml2rfc-dev@ietf.org>, Sandy Ginoza <sginoza@amsl.com>
Thread-Topic: [Ext] Re: [xml2rfc-dev] [xml2rfc] [Rfc-markdown] <br> is back, was: New xml2rfc release: v2.32.0
Thread-Index: AQHVffPqpzOR1LM9ZEqc3RrMiISZXadRa84A
Date: Tue, 08 Oct 2019 16:55:10 +0000
Message-ID: <5f467e5a-200f-e7fd-94d6-8b04d863c7e2@icann.org>
References: <E1iGMu9-00055y-Ui@durif.tools.ietf.org> <8304e61d-c550-91ea-9e23-eef2cd31240b@gmx.de> <A3513970-EEB0-4DBD-9E6F-A87EBFAF886D@att.com> <de4feaff-8f71-cd38-545c-2d848749251b@levkowetz.com> <f00a671a-6fe4-f5ae-2582-0b78ffa1c256@gmx.de> <1f18382c-d830-b887-f5d3-3f376ae4fdd7@gmx.de> <B15F7AF0-F5A0-401A-9F6E-F7E0E466B6A7@amsl.com> <f4f1b7ba-127a-fbfa-531b-eeff03814281@gmx.de> <71bc8d39-d06c-d900-cc8e-04a48218d75f@gmail.com> <0905DADC-E9D5-47A7-B610-F8A62686D2BD@att.com> <07DBAE10-D1FA-45C4-B7A2-321B265CA302@amsl.com> <c88388ff-84ae-c5f5-e093-e9aee77da3d6@levkowetz.com>
In-Reply-To: <c88388ff-84ae-c5f5-e093-e9aee77da3d6@levkowetz.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Thunderbird/68.1.1
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.0.32.234]
x-source-routing-agent: Processed
Content-Type: text/plain; charset="utf-8"
Content-ID: <785B9F4EF412024D90B259B42BAB571C@pexch112.icann.org>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-10-08_06:, , signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/7VDKKTA4oqW-da-CQ5n_IUCpI3A>
Subject: Re: [xml2rfc-dev] [Ext] Re: [xml2rfc] [Rfc-markdown] <br> is back, was: New xml2rfc release: v2.32.0
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: Tue, 08 Oct 2019 16:55:20 -0000

On 10/8/19 9:17 AM, Henrik Levkowetz wrote:
>>> Sandy, does the RPC feel that the ability to add a line break is needed?
>>
>> Yes, the RPC would appreciate being able to use <br>.
> 
> 
> Ok, I then propose that we permit <br> in body text, including lists and
> tables, and in document and section titles.  More specifically, I propose to
> permit <br> as a child element of these elements:
> 
>     blockquote
>     dd
>     dt
>     em
>     li
>     name
>     strong
>     t
>     td
>     th
>     title
>     tt
> 
> (Should <sub> and <sup> be in that list?  If we compare with the places where
> for instance <bcp14> is permitted, the answer would be 'yes'; but I'm not
> sure it's the right thing to do.)

This seems to go well beyond what the RPC asked for and significantly muddies the semantics of the v3 format.

The concern of the folks who contributed to the v3 design is that <br> everywhere would have authors thinking that they could put in line breaks for emphasis, or for making the output look "right" without any semantic meaning. In the original HTML semantics, <br> is a block-level break, not a character formatting break.

Given that, I would propose to instead allow <br/> in the following:

blockquote
dd
li
name
t
td
th

(I strongly dislike having <br/> in <name>, but we allow other formatting there, so this should be allowed as well.)

Sandy: Would that suit the needs of the RPC?

--Paul Hoffman