Re: [xml2rfc-dev] RFC 7991 issue #40: Schema Issue, RFC 7991, New Section 2.54.2

Julian Reschke <julian.reschke@gmx.de> Mon, 01 October 2018 12:11 UTC

Return-Path: <julian.reschke@gmx.de>
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 38AC5130DCE for <xml2rfc-dev@ietfa.amsl.com>; Mon, 1 Oct 2018 05:11:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 QXPhNiGH3XWM for <xml2rfc-dev@ietfa.amsl.com>; Mon, 1 Oct 2018 05:11:16 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (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 8CBFE120072 for <xml2rfc-dev@ietf.org>; Mon, 1 Oct 2018 05:11:15 -0700 (PDT)
Received: from [192.168.1.34] ([217.91.35.233]) by mail.gmx.com (mrgmx103 [212.227.17.168]) with ESMTPSA (Nemesis) id 0LsD9n-1fjntS1SdL-013u8N; Mon, 01 Oct 2018 14:11:01 +0200
Received: from [192.168.1.34] ([217.91.35.233]) by mail.gmx.com (mrgmx103 [212.227.17.168]) with ESMTPSA (Nemesis) id 0LsD9n-1fjntS1SdL-013u8N; Mon, 01 Oct 2018 14:11:01 +0200
To: henrik@levkowetz.com, xml2rfc-dev@ietf.org
References: <E1g6wVR-0006Oi-4Z@durif.tools.ietf.org>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <58b7afb2-53a4-8ee0-ba99-6d4a90c561af@gmx.de>
Date: Mon, 01 Oct 2018 14:11:01 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.0
MIME-Version: 1.0
In-Reply-To: <E1g6wVR-0006Oi-4Z@durif.tools.ietf.org>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K1:711HdokXwTU8EWmvyWuJ+4OCRW4lF/WA35i98sbp7CPcT2CWWYE go+0WJppgEncOcqYAt0+yMuIs0l+B6205B0xd3gqsYspQW0r8bzqYA1utAgPGf1We48CJcL RuMnLQ+IJJ1NLZHuRqU6UZxp29D6Cp4u1gPUgalUGNFVwCgUJZ6WyxXmhoaopNZqtg+8/mh hQ3i9DBccjCAm91bJtWJg==
X-UI-Out-Filterresults: notjunk:1;V01:K0:rq0qv+2F/4I=:v5R923Fxb4XcEfDrQBBGeG GkZYCrWDjsXtWxQd6rEeKblEv4qlqXTCBQBllDlJseTy8Rdr4QSMdZf299mN3M31l+UTkXoB8 ERqB8yqeTFlPoKOZYr+VkI8KpBJUidCFdYMpWaH5Fp73gyjCFqAzFimrgOOGJAqkQgzs8DEhz /h0uL9btT4ONd0StdCmeO+IqDpuHyPqV5RJzRIoizRn1mVvb+fqffzUD973H5HVCB7zAxrHJg GlvePE5mt1LabSivpD1V4i+ckmIAsROdljwIlrs6tvOTbZS/21cut0CPMF2hQ8K3twkkhpGEi 063kdowfoPQ98nSktqtta/SPS6Yg8F/2vMQp069+4qdP04P3GtF17gD3yf+mPbwJAMoqO9gSe e4o2Lw+XkvwbwnFJ+1Jvb0/a0FB6tBiOLRtUNYST+yGmygNe7tJ54eDr51g29PiOAhd9kj+Pb th8pDAHLiX3Bg6vfJ+aZm3DOp7+j4CkUt7UmpoKOEGi9qqo+4iz6PLH6n+4gr99spV45HsD7i 1qjhjKh6K8yacQbmEhalquiWBFQGGuuAcDsDy2+Q7QjzkWoHXko9HXQs6kX0L474B+IO6YXYD zxS84KTtQhm7Ll+W1vldLPgQp7hNV6RuNKb2lK8bfaJSEfkKtNW81gfzqVtfJ7U+QkgrJkDF/ BVWmdG227AmkEaVqZqNd2hsk8uE/D5gBsubijZwfLjICuk8GVvLVz1KOHO696IE4yyz/l+/mK OqmakfZt4njwzKo6UPuKHNmeFe98UB2CZStM0OGz89CG1tZNw+F+zOpQgfvcYc265aUP6MbOT Htzmb22r4Q8qjQnDVbLrgpHgFwHOsOfoJb6h0FE/6hiMiSkMSc=
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/agUW_TujXH_a8-au25sd5fUf1Zw>
Subject: Re: [xml2rfc-dev] RFC 7991 issue #40: Schema Issue, RFC 7991, New Section 2.54.2
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: Mon, 01 Oct 2018 12:11:19 -0000

On 10/1/2018 1:36 PM, henrik@levkowetz.com wrote:
> This captures an issue noted during implementation, also described in
> https://tools.ietf.org/html/draft-levkowetz-xml2rfc-v3-implementation#section-3.1.5
> 
> ---
> New Section 2.54.2
> 
>     The version 3 schema deprecates the previously available 'align'
>     attribute for the tables, and the V2 to V3 converter will remove this
>     attributes if used.  This makes a previous feature that was appreciated
>     by some authors unavailable.  In the text formatter, the effect is
>     simply to make all tables left-aligned, which may not be the most
>     readable and polished output, but for the HTML formatter it also
>     potentially removes the option of letting text flow around smaller
>     tables in a controlled way.
> 
>     Recommendation:  Make the 'align' attribute for tables available again.
> 
>     Implementation:  Implemented but inactive in the current version of
>                      xml2rfc.  The current text formatter code already has
>                      support for the 'align' attribute for these elements;
>                      but since the schema does not permit the attribute for
>                      <table>, the code is never invoked.
> ---
> ...

+1, but duplicates #9.

Best regards, Julian