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

Henrik Levkowetz <henrik@levkowetz.com> Sat, 06 October 2018 16:33 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 AFA47130E00 for <xml2rfc-dev@ietfa.amsl.com>; Sat, 6 Oct 2018 09:33:01 -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 dSi9zEBzwOCz for <xml2rfc-dev@ietfa.amsl.com>; Sat, 6 Oct 2018 09:32:59 -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 C1A4F130DDA for <xml2rfc-dev@ietf.org>; Sat, 6 Oct 2018 09:32:59 -0700 (PDT)
Received: from h-37-140.a357.priv.bahnhof.se ([94.254.37.140]:50086 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 1g8pVi-0000OK-0g; Sat, 06 Oct 2018 09:32:58 -0700
From: Henrik Levkowetz <henrik@levkowetz.com>
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>
To: XML Developer List <xml2rfc-dev@ietf.org>
Message-ID: <f36e6a80-99ad-fd1a-f872-9b8fc83fb763@levkowetz.com>
Date: Sat, 06 Oct 2018 18:32:50 +0200
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: <38897ac0-44a7-6b03-4e7e-e19a115fc53d@gmx.de>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="KB6pgq41nl70NFF4L99I612IpC2O3CLJL"
X-SA-Exim-Connect-IP: 94.254.37.140
X-SA-Exim-Rcpt-To: miek@miek.nl, xml2rfc-dev@ietf.org
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/XjmEYSeXCseUD3KAtNCOLLBmEdk>
Subject: [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 16:33:02 -0000

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

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

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.


Best regards,

	Henrik