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

Henrik Levkowetz <henrik@levkowetz.com> Mon, 01 October 2018 12:38 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 BADC7130E61 for <xml2rfc-dev@ietfa.amsl.com>; Mon, 1 Oct 2018 05:38:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 9h_B_4zAEYm0 for <xml2rfc-dev@ietfa.amsl.com>; Mon, 1 Oct 2018 05:38:01 -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 74249130E60 for <xml2rfc-dev@ietf.org>; Mon, 1 Oct 2018 05:38:01 -0700 (PDT)
Received: from h-37-140.a357.priv.bahnhof.se ([94.254.37.140]:61713 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 1g6xSa-0006nb-GO; Mon, 01 Oct 2018 05:38:00 -0700
To: Julian Reschke <julian.reschke@gmx.de>, xml2rfc-dev@ietf.org
References: <E1g6wQ8-00057n-85@durif.tools.ietf.org> <70ee4cff-7533-13e0-d71a-ffecf2dc56f0@gmx.de>
From: Henrik Levkowetz <henrik@levkowetz.com>
Message-ID: <24828f94-dbbd-4c18-8d85-333487bda367@levkowetz.com>
Date: Mon, 01 Oct 2018 14:37:52 +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: <70ee4cff-7533-13e0-d71a-ffecf2dc56f0@gmx.de>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="8RrRxSLcfdigoqmm4spDJBXrkSjJp3sWb"
X-SA-Exim-Connect-IP: 94.254.37.140
X-SA-Exim-Rcpt-To: xml2rfc-dev@ietf.org, julian.reschke@gmx.de
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/W3HCeisOsOF__lNXx--fOkZODEY>
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: Mon, 01 Oct 2018 12:38:04 -0000

Hi Julian,

On 2018-10-01 14:07, Julian Reschke wrote:
> On 10/1/2018 1:31 PM, henrik@levkowetz.com wrote:
>> This captures an issue noted during implementation, also described in
>> https://tools.ietf.org/html/draft-levkowetz-xml2rfc-v3-implementation#section-3.1.2
>> 
>> Specification: https://tools.ietf.org/html/rfc7991#section-2.12
>> 
>> ---
>> In Section 2.12, <br>
>> 
>>     A number of elements permits a mixed content model (see Section "Mixed
>>     Content Model"): <li>, <blockquote>, <dd>, <td>, and <th>.  However,
>>     when using the simpler of the two content schemas, two of them (<td> and
>>     <th>) permit inline line breaks through the use of <br> elements; the
>>     others do not.  This seems terribly arbitrary.
>> 
>>     Recommendation:  Remove the <br> element completely.  Alternatively,
>>                      permit it to be used all places that 'text' and non-
>>                      block elements may be used (that is, in inline
>>                      context).
>> 
>>     Implementation:  The current version of xml2rfc renders <br> as a
>>                      newline in all inline contexts.
>> ---
> 
> As far as I recall, we ended up with the limited use of <br> because 
> forcing a line break inside a table cell sometimes really is needed, 
> while otherwise it's not. I agree consistency is nice, but this may be a 
> case where the current approach is the right one.

Experience with the use of the v3 specification is of course very limited
at present, but my awareness of the issue was triggered by attempts to use
<br> by Miek, when he started adapting his pandoc2rfc tool to use the v3
vocabulary.

I would say that even if <br> in running text would rarely be needed, the
confusion Miek ran into is unnecessary, and limiting <br> to use within
table cells, as opposed to removing it altogether or permitting it inline
everywhere is more complex for both authors and formatters to keep track
of and handle.

Hence my proposal.


Best regards,

	Henrik