IETF Logo Mail Archive

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

henrik@levkowetz.com Mon, 01 October 2018 11:31 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 658A0130E5F for <xml2rfc-dev@ietfa.amsl.com>; Mon, 1 Oct 2018 04:31:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.889
X-Spam-Level:
X-Spam-Status: No, score=-1.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_MANY_HDRS_LCASE=0.01, 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 2FDGGTOYgCDu for <xml2rfc-dev@ietfa.amsl.com>; Mon, 1 Oct 2018 04:31:24 -0700 (PDT)
Received: from durif.tools.ietf.org (durif.tools.ietf.org [IPv6:2001:1900:3001:11::3d]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7378B130DEB for <xml2rfc-dev@ietf.org>; Mon, 1 Oct 2018 04:31:24 -0700 (PDT)
Received: from localhost ([::1]:40259 helo=durif.tools.ietf.org) by durif.tools.ietf.org with esmtp (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1g6wQ8-00057n-85 for xml2rfc-dev@ietf.org; Mon, 01 Oct 2018 04:31:24 -0700
to: xml2rfc-dev@ietf.org
from: henrik@levkowetz.com
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Message-Id: <E1g6wQ8-00057n-85@durif.tools.ietf.org>
Date: Mon, 01 Oct 2018 04:31:24 -0700
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: xml2rfc-dev@ietf.org
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on durif.tools.ietf.org); SAEximRunCond expanded to false
X-Clacks-Overhead: GNU Terry Pratchett
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/GKYZfHzIauvIv9jmxzHHf9WeX8E>
Subject: [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 11:31:27 -0000

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.
---

Regards,
	Henrik

-- 
This issue is tracked at:
   https://github.com/rfc-format/draft-iab-xml2rfc-v3-bis/issues/37

Discussion should take place on this list.

v2.23.0 | Report a Bug | By Email