IETF Logo Mail Archive

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

Robert Sparks <rjsparks@nostrum.com> Thu, 04 October 2018 17:19 UTC

Return-Path: <rjsparks@nostrum.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 88935130E94 for <xml2rfc-dev@ietfa.amsl.com>; Thu, 4 Oct 2018 10:19:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.879
X-Spam-Level:
X-Spam-Status: No, score=-1.879 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] 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 un2LpnocsTyq for <xml2rfc-dev@ietfa.amsl.com>; Thu, 4 Oct 2018 10:18:58 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 0CFBD130DD3 for <xml2rfc-dev@ietf.org>; Thu, 4 Oct 2018 10:18:57 -0700 (PDT)
Received: from unescapeable.routerlogin.net (mobile-166-137-217-005.mycingular.net [166.137.217.5]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id w94HIWGZ021985 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 4 Oct 2018 12:18:34 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host mobile-166-137-217-005.mycingular.net [166.137.217.5] claimed to be unescapeable.routerlogin.net
To: Paul Hoffman <paul.hoffman@icann.org>, Miek Gieben <miek@miek.nl>
Cc: "xml2rfc-dev@ietf.org" <xml2rfc-dev@ietf.org>
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>
From: Robert Sparks <rjsparks@nostrum.com>
Message-ID: <2ab7b797-4a01-5327-10fb-5ae13587944f@nostrum.com>
Date: Thu, 04 Oct 2018 12:18:27 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <B63F3A7C-AAB6-4281-BC5F-BC28E9693E43@icann.org>
Content-Type: multipart/alternative; boundary="------------4D98108156F624C2E3F3A26F"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/oQ_UIqDSN_1iPH7IRqc046J9jbU>
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:19:01 -0000

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.
>
> --Paul Hoffman
>
>
> _______________________________________________
> xml2rfc-dev mailing list
> xml2rfc-dev@ietf.org
> https://www.ietf.org/mailman/listinfo/xml2rfc-dev

v2.23.0 | Report a Bug | By Email