Re: [xml2rfc-dev] RFC 7991 issue #37: Schema Issue, RFC 7991, In Section 2.12, <br>

Henrik Levkowetz <henrik@levkowetz.com> Thu, 04 October 2018 17:57 UTC

Return-Path: <henrik@levkowetz.com>
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 6C667130EB3 for <xml2rfc-dev@ietfa.amsl.com>; Thu, 4 Oct 2018 10:57:02 -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] 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 gH0eSdtl1B_K for <xml2rfc-dev@ietfa.amsl.com>; Thu, 4 Oct 2018 10:57:00 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2EF20130ED7 for <xml2rfc-dev@ietf.org>; Thu, 4 Oct 2018 10:57:00 -0700 (PDT)
Received: from h-37-140.a357.priv.bahnhof.se ([94.254.37.140]:56082 helo=tannat.localdomain) by zinfandel.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1g87ru-0007kk-Jt; Thu, 04 Oct 2018 10:56:59 -0700
To: Robert Sparks <rjsparks@nostrum.com>, Paul Hoffman <paul.hoffman@icann.org>, Miek Gieben <miek@miek.nl>
References: <E1g6wQ8-00057n-85@durif.tools.ietf.org> <70ee4cff-7533-13e0-d71a-ffecf2dc56f0@gmx.de> <24828f94-dbbd-4c18-8d85-333487bda367@levkowetz.com> <3ac63652-2df2-03c7-eee6-bad2cbd326d8@levkowetz.com> <B63F3A7C-AAB6-4281-BC5F-BC28E9693E43@icann.org> <2ab7b797-4a01-5327-10fb-5ae13587944f@nostrum.com>
Cc: "xml2rfc-dev@ietf.org" <xml2rfc-dev@ietf.org>
From: Henrik Levkowetz <henrik@levkowetz.com>
Message-ID: <c9dc6869-148c-cdcc-06a4-94aeb2d6df57@levkowetz.com>
Date: Thu, 04 Oct 2018 19:56:48 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <2ab7b797-4a01-5327-10fb-5ae13587944f@nostrum.com>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="JAHaatxXU6CUwA70aM9IgLncaw8jucxHA"
X-SA-Exim-Connect-IP: 94.254.37.140
X-SA-Exim-Rcpt-To: xml2rfc-dev@ietf.org, miek@miek.nl, paul.hoffman@icann.org, rjsparks@nostrum.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on zinfandel.tools.ietf.org)
X-Clacks-Overhead: GNU Terry Pratchett
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/8d0Tl90Ksw3unHRl3avMvu01ID0>
Subject: Re: [xml2rfc-dev] RFC 7991 issue #37: Schema Issue, RFC 7991, In Section 2.12, <br>
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: Thu, 04 Oct 2018 17:57:09 -0000

On 2018-10-04 19:18, Robert Sparks wrote:
> I didn't see a response to this.
> 
> If we decide that preserving the "only in tables" idea, this avoids the 
> argument about causing authors unnecessary confusion.
> 
> If it's clearly a bad idea, please capture why on the list for later.
> 
> RjS
> 
> 
> On 10/2/18 12:56 PM, Paul Hoffman wrote:
>> I just thought of something different that might deal with Miek's
>> issue: change the name of the element to <tbr>. That will prevent
>> people who "know" what <br> "means" from expecting it to work
>> because <br> doesn't exist.
>> 
>> If, later, we want to add <br> for running text (with lots of
>> description of what it will and will not do to displayed RFCs), we
>> can do so then.


So, Miek's original issue, as communicated to me, as I understood it,
found reasonable, and tried to capture in #37, was that <br> was generally
unavailable, but the functionality existed specifically within table cells.

Miek has also raised a related issue, #41, about not having so many special
cases in the schema.

Finally, <br> is a known tool for authors acquainted with HTML, if they
have a situation where default layout doesn't do the right thing.

So renaming <br> to <tbr> will deal with the expectation of <br> being
generally useful, since it's not called <br> any more.  It will probably
leave some authors without remedy for the case of controlling table
column title breaks, as they won't think to look for <tbr> if <br> doesn't
work.

The renaming will not do anything for issue #41, and it will also do nothing
to address the need for a straightforward capability like <br> in other
contexts.

So I don't see this a clean solution, and the parts it solves also introduces
new drawbacks.

I tried to capture what I felt was the essence of the problem in my proposed
resolution, of either permitting <br> widely, or removing it.  I still don't
care much either way, but <tbr> seems to provide neither the cleanness of
removing <br> it completely, or permitting it more generally.


	Henrik