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

Julian Reschke <julian.reschke@gmx.de> Mon, 01 October 2018 12:08 UTC

Return-Path: <julian.reschke@gmx.de>
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 5B441120072 for <xml2rfc-dev@ietfa.amsl.com>; Mon, 1 Oct 2018 05:08:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 EYfu4jwkyt8q for <xml2rfc-dev@ietfa.amsl.com>; Mon, 1 Oct 2018 05:08:09 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 960A7130DF0 for <xml2rfc-dev@ietf.org>; Mon, 1 Oct 2018 05:08:08 -0700 (PDT)
Received: from [192.168.1.34] ([217.91.35.233]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0LejNC-1fNThF3X5S-00qQ36; Mon, 01 Oct 2018 14:07:55 +0200
Received: from [192.168.1.34] ([217.91.35.233]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0LejNC-1fNThF3X5S-00qQ36; Mon, 01 Oct 2018 14:07:55 +0200
To: henrik@levkowetz.com, xml2rfc-dev@ietf.org
References: <E1g6wQ8-00057n-85@durif.tools.ietf.org>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <70ee4cff-7533-13e0-d71a-ffecf2dc56f0@gmx.de>
Date: Mon, 01 Oct 2018 14:07:55 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.0
MIME-Version: 1.0
In-Reply-To: <E1g6wQ8-00057n-85@durif.tools.ietf.org>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K1:zDn2kERUji/nbdCqJKg6JQ2MkBcRk5R9M6vD5tfBCKWDSMUp6Af 90cpBxBb1qzbJunq84hpCqlr1APlnpZhJ8PBGGmQwbV/LAHfrBkUVwBE57CJV7l+j45NvN4 HcU0H3p/ZjF0IxC9LRXVjSleUr+XQKD304cDOpieR4Dsctd2wwTXbm21OFrsRkkYznTGj4F 30yQiSE6BEvHhbqQXXK+A==
X-UI-Out-Filterresults: notjunk:1;V01:K0:8bGThWbypq8=:nsdux5n7A+xPd4DyhJVfMF bX81DY+R6I7GaDIZ69V/tB9yDm+FF0tU76l5394sBO+yctbnQX/YP3uy043nin6Sh4P53hbMN esFkwguQqx94AMMKDCB7F4gl0vHVroV1Gbw788LqjI9LU21o0Pa5EmJomZ6Vgp0cnU5+GL81C enzi9YMqPeXjThJ8HrhuBukOF4tWtHRUq4qPc8f+BnldXfhFG8hC7LYM0KCe7R/G7HZ6+YlXq rd3eMf83IKnAi6x/8fdWC9VoOWJ1F1FRKlp5ZtaV4eoxvJtplq9AVjwq4WeI2+dg6WRO5mBOF DzW4X9d5Fr9G6D+pavlX7mJohXI6CP9s7dt/BCLNbxgMeZ14y+L7jsMeX9f+qEmY+O+SL2Asn AaE4CPp1NhRJuNkhip4cWDbyYvO8X+4FEK4c6T9bcvpjj/rcp2zuPipImol4/C59JNLg6Io5f 3RDawKTRCzhdKxkHHWSTtW6ERZz3JfZ0XEthoiaE+YOrIvCcbV1mWZ7EHwv4Y2YuDc4zvK+jZ 2gBCXV7HJ0zq7oN0Ea1omiO9W4kpR03AjGnGptpQmY0MzinuElBA+NtIf8SSwIMwS43iKa6d/ 3sxFh9revdxB80edrPLchttZ7B669WoEqOqjd0rSSbAH9kMjENcNr9wISRQDc5JRrI5uzSv6T zQfStm9hJtMNGjfYemsuQbZwoU9jJ3CEjN96D7dR0HlycCy3lcS2nGha79hWPDDA7fg0mX+T8 NUgazKbieByo4VWjrVIbNu+Da1vTcdwqoo0Innb9R6GKIEA4zfOHODWgCDDgqSBYQr8KxeMj2 x+CAx4+NRZYGk8cpZEVca1BB2KoRWf3Fz+bUL0vp8pyGQBg5uE=
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/3JIho6JwqZwl6hCgTKP3IL3Fu0U>
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:08:12 -0000

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.

Best regards, Julian