Re: [xml2rfc-dev] RFC 7991 issue #37: Schema Issue, RFC 7991, In Section 2.12, <br>
Jim Schaad <ietf@augustcellars.com> Wed, 03 October 2018 03:12 UTC
Return-Path: <ietf@augustcellars.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 485AF13118E for <xml2rfc-dev@ietfa.amsl.com>; Tue, 2 Oct 2018 20:12:26 -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, RCVD_IN_DNSWL_NONE=-0.0001, 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 OM_fm5w8LiS3 for <xml2rfc-dev@ietfa.amsl.com>; Tue, 2 Oct 2018 20:12:24 -0700 (PDT)
Received: from mail2.augustcellars.com (augustcellars.com [50.45.239.150]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AD66F130FBD for <xml2rfc-dev@ietf.org>; Tue, 2 Oct 2018 20:12:23 -0700 (PDT)
Received: from Jude (192.168.0.11) by mail2.augustcellars.com (192.168.0.56) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Tue, 2 Oct 2018 20:07:43 -0700
From: Jim Schaad <ietf@augustcellars.com>
To: 'Paul Hoffman' <paul.hoffman@icann.org>, 'Miek Gieben' <miek@miek.nl>
CC: 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> <20181002180304.nsrwbvpcesb4ozrd@miek.nl> <2C672A24-F2F1-47C4-B183-EE078F920D50@icann.org>
In-Reply-To: <2C672A24-F2F1-47C4-B183-EE078F920D50@icann.org>
Date: Tue, 02 Oct 2018 20:12:16 -0700
Message-ID: <02bd01d45ac6$e53cf9b0$afb6ed10$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQJneuHnr/v7zss5vAhzJBHAbfZkOwKlc/I8AYxBdvwC96tKtwK9drHlAgM7L/oA5XHcjqOAGaZg
Content-Language: en-us
X-Originating-IP: [192.168.0.11]
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/p3gQvgq2wa8LgkzEDRsc3teXVQw>
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: Wed, 03 Oct 2018 03:12:26 -0000
> -----Original Message----- > From: xml2rfc-dev <xml2rfc-dev-bounces@ietf.org> On Behalf Of Paul > Hoffman > Sent: Tuesday, October 2, 2018 11:11 AM > To: Miek Gieben <miek@miek.nl> > Cc: xml2rfc-dev@ietf.org > Subject: Re: [xml2rfc-dev] RFC 7991 issue #37: Schema Issue, RFC 7991, In > Section 2.12, <br> > > On Oct 2, 2018, at 11:03 AM, Miek Gieben <miek@miek.nl> wrote: > > > > [ Quoting <paul.hoffman@icann.org> in "Re: [xml2rfc-dev] RFC 7991 issue > #3..." ] > >> 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. > > > > What's the problem for just allowing it ~everywhere (ala HTML); and go by > the motto: garbage in; garbage out? > > See previous answers. We don't want "garbage in", these are long-lived > documents. We want documents that are well-structured and well-searchable > and so on. > > > I wonder who can honestly say that they can write 7991 XML *without* > having the spec next to them. The main reason that I know of for doing a <br> is to break paragraphs in a list item. This is no longer necessary as you can now have more than one <t> as a child of an item which was not previously possible. I think this should be left as is. Well, I can honestly say that I can currently write about 90% of the v2 grammar without needing to consult a specification for it. I will admit that I do use a template as a starting point, but I would assume that would be normal case for writing v3 documents from scratch as well. There are probably some corner cases that might be done better, but that is going to be true no matter what I use to write documents in. I find it harder to remember all of the ways to use markdown than I ever did to write XML. Jim > > Most likely not. Nor could they do that with the current v2 format if they did > anything more than paragraphs and sections. > > --Paul Hoffman
- Re: [xml2rfc-dev] RFC 7991 issue #37: Schema Issu… Julian Reschke
- [xml2rfc-dev] RFC 7991 issue #37: Schema Issue, R… henrik
- Re: [xml2rfc-dev] RFC 7991 issue #37: Schema Issu… Henrik Levkowetz
- Re: [xml2rfc-dev] RFC 7991 issue #37: Schema Issu… Julian Reschke
- Re: [xml2rfc-dev] RFC 7991 issue #37: Schema Issu… Henrik Levkowetz
- Re: [xml2rfc-dev] RFC 7991 issue #37: Schema Issu… Paul Hoffman
- Re: [xml2rfc-dev] RFC 7991 issue #37: Schema Issu… Paul Hoffman
- Re: [xml2rfc-dev] RFC 7991 issue #37: Schema Issu… Miek Gieben
- Re: [xml2rfc-dev] RFC 7991 issue #37: Schema Issu… Paul Hoffman
- Re: [xml2rfc-dev] RFC 7991 issue #37: Schema Issu… Jim Schaad
- Re: [xml2rfc-dev] RFC 7991 issue #37: Schema Issu… Henrik Levkowetz
- Re: [xml2rfc-dev] RFC 7991 issue #37: Schema Issu… Henrik Levkowetz
- Re: [xml2rfc-dev] RFC 7991 issue #37: Schema Issu… Julian Reschke
- Re: [xml2rfc-dev] RFC 7991 issue #37: Schema Issu… Henrik Levkowetz
- Re: [xml2rfc-dev] RFC 7991 issue #37: Schema Issu… Julian Reschke
- Re: [xml2rfc-dev] RFC 7991 issue #37: Schema Issu… Henrik Levkowetz
- Re: [xml2rfc-dev] RFC 7991 issue #37: Schema Issu… Julian Reschke
- Re: [xml2rfc-dev] RFC 7991 issue #37: Schema Issu… Henrik Levkowetz
- Re: [xml2rfc-dev] RFC 7991 issue #37: Schema Issu… Julian Reschke
- Re: [xml2rfc-dev] RFC 7991 issue #37: Schema Issu… Henrik Levkowetz
- Re: [xml2rfc-dev] [Ext] Re: RFC 7991 issue #37: S… Paul Hoffman
- Re: [xml2rfc-dev] RFC 7991 issue #37: Schema Issu… Jim Schaad
- Re: [xml2rfc-dev] [Ext] Re: RFC 7991 issue #37: S… Henrik Levkowetz
- Re: [xml2rfc-dev] RFC 7991 issue #37: Schema Issu… Julian Reschke
- Re: [xml2rfc-dev] [Ext] Re: RFC 7991 issue #37: S… Julian Reschke
- Re: [xml2rfc-dev] RFC 7991 issue #37: Schema Issu… Henrik Levkowetz
- Re: [xml2rfc-dev] RFC 7991 issue #37: Schema Issu… Martin J. Dürst
- Re: [xml2rfc-dev] RFC 7991 issue #37: Schema Issu… Julian Reschke
- Re: [xml2rfc-dev] RFC 7991 issue #37: Schema Issu… Henrik Levkowetz
- Re: [xml2rfc-dev] RFC 7991 issue #37: Schema Issu… Julian Reschke
- Re: [xml2rfc-dev] RFC 7991 issue #37: Schema Issu… Henrik Levkowetz
- Re: [xml2rfc-dev] [Ext] RFC 7991 issue #37: Schem… Paul Hoffman
- Re: [xml2rfc-dev] [Ext] RFC 7991 issue #37: Schem… Henrik Levkowetz
- Re: [xml2rfc-dev] [Ext] RFC 7991 issue #37: Schem… Paul Hoffman
- Re: [xml2rfc-dev] [Ext] RFC 7991 issue #37: Schem… Julian Reschke
- Re: [xml2rfc-dev] [Ext] RFC 7991 issue #37: Schem… Henrik Levkowetz
- Re: [xml2rfc-dev] RFC 7991 issue #37: Schema Issu… Robert Sparks
- Re: [xml2rfc-dev] RFC 7991 issue #37: Schema Issu… Julian Reschke
- Re: [xml2rfc-dev] RFC 7991 issue #37: Schema Issu… Henrik Levkowetz
- Re: [xml2rfc-dev] RFC 7991 issue #37: Schema Issu… Miek Gieben
- Re: [xml2rfc-dev] [Ext] Re: RFC 7991 issue #37: S… Paul Hoffman
- Re: [xml2rfc-dev] [Ext] Re: RFC 7991 issue #37: S… Miek Gieben
- Re: [xml2rfc-dev] [Ext] Re: RFC 7991 issue #37: S… Julian Reschke
- Re: [xml2rfc-dev] [Ext] Re: RFC 7991 issue #37: S… Miek Gieben
- Re: [xml2rfc-dev] [Ext] Re: RFC 7991 issue #37: S… Henrik Levkowetz
- Re: [xml2rfc-dev] [Ext] Re: RFC 7991 issue #37: S… Julian Reschke
- Re: [xml2rfc-dev] RFC 7991 issue #37: Schema Issu… Heather Flanagan
- Re: [xml2rfc-dev] RFC 7991 issue #37: Schema Issu… Henrik Levkowetz
- Re: [xml2rfc-dev] RFC 7991 issue #37: Schema Issu… Heather Flanagan
- [xml2rfc-dev] RFC 7991 issue #31: Schema Issue, R… Henrik Levkowetz
- Re: [xml2rfc-dev] RFC 7991 issue #31: Schema Issu… Jim Schaad
- Re: [xml2rfc-dev] RFC 7991 issue #31: Schema Issu… Henrik Levkowetz
- Re: [xml2rfc-dev] RFC 7991 issue #31: Schema Issu… Carsten Bormann
- Re: [xml2rfc-dev] RFC 7991 issue #31: Schema Issu… Jim Schaad
- Re: [xml2rfc-dev] RFC 7991 issue #31: Schema Issu… Henrik Levkowetz
- Re: [xml2rfc-dev] RFC 7991 issue #31: Schema Issu… Heather Flanagan
- Re: [xml2rfc-dev] RFC 7991 issue #31: Schema Issu… Henrik Levkowetz
- Re: [xml2rfc-dev] RFC 7991 issue #31: Schema Issu… Jim Schaad
- Re: [xml2rfc-dev] RFC 7991 issue #31: Schema Issu… Henrik Levkowetz
- Re: [xml2rfc-dev] [Ext] RFC 7991 issue #31: Schem… Paul Hoffman
- Re: [xml2rfc-dev] [Ext] RFC 7991 issue #31: Schem… Jim Schaad
- Re: [xml2rfc-dev] [Ext] RFC 7991 issue #31: Schem… Henrik Levkowetz
- Re: [xml2rfc-dev] [Ext] RFC 7991 issue #31: Schem… Henrik Levkowetz
- Re: [xml2rfc-dev] [Ext] RFC 7991 issue #31: Schem… Jim Schaad
- Re: [xml2rfc-dev] [Ext] RFC 7991 issue #31: Schem… Heather Flanagan
- Re: [xml2rfc-dev] [Ext] Re: RFC 7991 issue #37: S… HANSEN, TONY L
- Re: [xml2rfc-dev] RFC 7991 issue #37: Schema Issu… HANSEN, TONY L
- Re: [xml2rfc-dev] RFC 7991 issue #37: Schema Issu… HANSEN, TONY L
- Re: [xml2rfc-dev] [Ext] Re: RFC 7991 issue #37: S… Henrik Levkowetz