Re: [xml2rfc-dev] RFC 7991 issue #31: Schema Issue, RFC 7991, In Section 2.54, <table>

Jim Schaad <ietf@augustcellars.com> Sat, 06 October 2018 19:27 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 87F30130E02 for <xml2rfc-dev@ietfa.amsl.com>; Sat, 6 Oct 2018 12:27:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 EbLP5BWLAjmW for <xml2rfc-dev@ietfa.amsl.com>; Sat, 6 Oct 2018 12:27:08 -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 E0C37130DEE for <xml2rfc-dev@ietf.org>; Sat, 6 Oct 2018 12:27:07 -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; Sat, 6 Oct 2018 12:22:14 -0700
From: Jim Schaad <ietf@augustcellars.com>
To: 'Henrik Levkowetz' <henrik@levkowetz.com>, 'XML Developer List' <xml2rfc-dev@ietf.org>
References: <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> <f36e6a80-99ad-fd1a-f872-9b8fc83fb763@levkowetz.com> <050c01d45d97$714e51b0$53eaf510$@augustcellars.com> <efc18e10-416f-91ae-bff5-f7ecf2721df4@levkowetz.com>
In-Reply-To: <efc18e10-416f-91ae-bff5-f7ecf2721df4@levkowetz.com>
Date: Sat, 06 Oct 2018 12:26:47 -0700
Message-ID: <052b01d45daa$87e71980$97b54c80$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQKlc/I8qUpx6H6sTpIQv3vHmEIb5gGMQXb8AverSrcCvXax5QHGvedgAOtPwScCpgcF3ADkS5KAAqj1aRQB/yc3qAHvHWwdAnFKOwwCPeYpeKKqSxbQ
Content-Language: en-us
X-Originating-IP: [192.168.0.11]
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/MUDrMUn2Ds6Ggxr5p3IrawCiVzc>
Subject: Re: [xml2rfc-dev] RFC 7991 issue #31: Schema Issue, RFC 7991, In Section 2.54, <table>
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: Sat, 06 Oct 2018 19:27:10 -0000


> -----Original Message-----
> From: Henrik Levkowetz <henrik@levkowetz.com>
> Sent: Saturday, October 6, 2018 10:39 AM
> To: Jim Schaad <ietf@augustcellars.com>; 'XML Developer List' <xml2rfc-
> dev@ietf.org>
> Subject: Re: [xml2rfc-dev] RFC 7991 issue #31: Schema Issue, RFC 7991, In
> Section 2.54, <table>
> 
> On 2018-10-06 19:10, Jim Schaad wrote:
> >
> >> -----Original Message-----
> >> From: xml2rfc-dev <xml2rfc-dev-bounces@ietf.org> On Behalf Of Henrik
> >> Levkowetz
> >> Sent: Saturday, October 6, 2018 9:33 AM
> >> To: XML Developer List <xml2rfc-dev@ietf.org>
> >> Subject: [xml2rfc-dev] RFC 7991 issue #31: Schema Issue, RFC 7991, In
> >> Section 2.54, <table>
> >>
> >> Bringing this issue to the list.  The issue was raised by Miek:
> >> https://github.com/rfc-format/draft-iab-xml2rfc-v3-bis/issues/31
> >>
> >> This issue starts out by stating one problem, namely that <table> has
> >> no provisions for having a caption.  The discussion subsequently
> >> sorts this out, pointing to the use of the <name> element for a table
> >> in order to provide the caption.
> >>
> >> In order to make this clearer, Section 2.54 probably should mention
> >> the usage of <name> to provide a caption, and section 2.32 should
> >> include 'table' in the initial list of places it can be used (not
> >> only texttable).  Section 1.3.3, bullet 7 could also mention the use of <name>
> to provide a caption.
> >>
> >> The discussion subsequently mentions the discrepancy between table
> >> and figure permitting <name>, while <artwork> doesn't.  To clarify
> >> this, it might be good to point out in Section 2.5. <artwork> that
> >> there is no separate numbering space for artwork; in order to caption
> >> and number a piece of artwork it has to be wrapped in a <figure> so that it
> can get a Figure number.
> >>
> >> Finally the discussion moves on to the alignment of table captions.
> >>
> >> There are 2 issues here:
> >>
> >>  - one schema issue, which is whether to permit left/center/right
> >>    alignment of tables.  It is permitted for artwork, and was permitted
> >>    for texttable, but it not permitted for <table>.
> >
> > This is going to violate the least surprise rule. Since v2 centers
> > tables by default, I think that should be the case in v3 as well.
> 
> I fully agree.  Not making it so is a mistake from my side.  Will fix in the next
> release.
> 
> > The
> > question then becomes what are the advantages/disadvantages of
> > allowing for left and right aligned tables.
> 
> Right.  (And also the issue of permitting it in the past, but not now.)
> 
> >>  - The alignment of the table caption.  This is not covered in the
> >>    specification, but xml2rfc 2.10.2 centers the caption, while the
> >>    table (lacking any alignment specification) is left-aligned.  For
> >>    narrow tables, this mis-alignment of caption and table does not look
> >>    good.  The next release of xml2rfc will center the caption under the
> >>    table, before placing the combined table and caption.
> >
> > What is the rule you have for doing the alignment of figure captions?
> > I think that the same rules should apply to both figures and tables.
> 
> Till now, both have been centered.  That can be changed.
> 

No, I would not change this.  I would keep the centering for the caption.  The next interesting question the caption is wider than the table should it be wrapped to the table width or run on past the edge of the table.  I don't think that I have a preference

Jim


> >
> >>
> >> To sum up:  I think there are some improvements that could be made to
> >> the document text, to clarify the use of <name> to provide <table>
> >> captions.  There is one unresolved schema issue (align keyword for
> >> <table>) and one layout issue which will be fixed in the next xml2rfc release.
> >
> > +1 on adding the align to the table, but the default needs to be
> > center. If we allow it for figures then it should also be allowed for
> > tables.
> 
> Makes sense to me.
> 
> 	Henrik