IETF Logo Mail Archive

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

Henrik Levkowetz <henrik@levkowetz.com> Tue, 30 October 2018 09:28 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 97A4B12F1A6 for <xml2rfc-dev@ietfa.amsl.com>; Tue, 30 Oct 2018 02:28:29 -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 3SLW46oxiKih for <xml2rfc-dev@ietfa.amsl.com>; Tue, 30 Oct 2018 02:28:28 -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 1890E12D4E9 for <xml2rfc-dev@ietf.org>; Tue, 30 Oct 2018 02:28:28 -0700 (PDT)
Received: from h-37-140.a357.priv.bahnhof.se ([94.254.37.140]:59843 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 1gHQK3-0002GS-0m; Tue, 30 Oct 2018 02:28:27 -0700
To: "HANSEN, TONY L" <tony@att.com>, "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> <2ab7b797-4a01-5327-10fb-5ae13587944f@nostrum.com> <a9cbe9b1-1ee4-b60b-bb88-d07d11afa6a3@gmx.de> <20181004192423.xexbgomdqs56pkok@miek.nl> <5694D337-A88C-4F3E-AE2D-8EA34C3A5A93@icann.org> <20181004193939.szec4ng47kp7lapv@miek.nl> <38897ac0-44a7-6b03-4e7e-e19a115fc53d@gmx.de> <b4b4ef3c-b510-9962-e3d9-21b856662bea@levkowetz.com> <410BB67F-2C5A-4B9E-AF78-04D94991A082@att.com>
From: Henrik Levkowetz <henrik@levkowetz.com>
Message-ID: <cd671664-b515-17db-152a-529b011442ec@levkowetz.com>
Date: Tue, 30 Oct 2018 10:28:19 +0100
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: <410BB67F-2C5A-4B9E-AF78-04D94991A082@att.com>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="CeuU4GijFd1vpb0KVbfQx3eeSvQh1dE7J"
X-SA-Exim-Connect-IP: 94.254.37.140
X-SA-Exim-Rcpt-To: xml2rfc-dev@ietf.org, tony@att.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/T9csBxZzlFGv8mTSra3G0IBwU0Q>
Subject: Re: [xml2rfc-dev] [Ext] Re: 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: Tue, 30 Oct 2018 09:28:30 -0000

On 2018-10-29 02:05, HANSEN, TONY L wrote:
> My druthers would have been to allow it anywhere.

I agree.  Although my primary point was consistency, I've had to deal
with long document titles that would have benefited from having <br>
available.

	Henrik

	

> 	Tony
> 
> On 10/4/18, 5:55 PM, "xml2rfc-dev on behalf of Henrik Levkowetz" <xml2rfc-dev-bounces@ietf.org on behalf of henrik@levkowetz.com> wrote:
> 
>     Hi Julian,
>     
>     On 2018-10-04 23:33, Julian Reschke wrote:
>     > On 2018-10-04 21:39, Miek Gieben wrote:
>     >> [ Quoting <paul.hoffman@icann.org> in "Re: [Ext] Re: [xml2rfc-dev] RFC 
>     >> 799..." ]
>     >>> One of the design goals for v3 was to get rid of markup that had no 
>     >>> semantic meaning to the documents. We mostly succeeded at that, but 
>     >>> clearly failed to clean up some of it (such as by allowing <br> in 
>     >>> table cells). I still think this is a good goal, and if we want to be 
>     >>> consistent, we should just rid of <br>.
>     >> 
>     >> If that's technically possible: +1 for removing <br> entirely
>     > 
>     > Misleading.
>     > 
>     > HTML can focus on semantic markup, because it has a sister technology to 
>     > deal with presentation (CSS). We don't have that, so we need to consider 
>     > common cases where a default presentation just isn't good enough.
>     > 
>     > I'm very surprised that people have no problem adding an attribute for 
>     > hanging list presentation but then at the same time object to enforced 
>     > line breaks in table cells.
>     
>     For me, it's not that.  It is adding <br> for that case, and not for
>     others where it would be just as useful.  It's the inconsistency.
>     
>     
>     Best regards,
>     
>     	Henrik
>     
>     
>     
> 
> _______________________________________________
> xml2rfc-dev mailing list
> xml2rfc-dev@ietf.org
> https://www.ietf.org/mailman/listinfo/xml2rfc-dev
>

v2.23.0 | Report a Bug | By Email