Re: [xml2rfc-dev] --table-borders

Julian Reschke <julian.reschke@gmx.de> Thu, 27 January 2022 06:40 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 AB9593A135A for <xml2rfc-dev@ietfa.amsl.com>; Wed, 26 Jan 2022 22:40:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.612
X-Spam-Level:
X-Spam-Status: No, score=-2.612 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.714, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gmx.net
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 eIHssBiyw-kL for <xml2rfc-dev@ietfa.amsl.com>; Wed, 26 Jan 2022 22:40:20 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 14E563A135D for <xml2rfc-dev@ietf.org>; Wed, 26 Jan 2022 22:40:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1643265615; bh=RCCmC/VP5mgU7zMHStaELb6tFRIlF5sQ/4Zw9jERbYs=; h=X-UI-Sender-Class:Date:Subject:To:References:From:In-Reply-To; b=D/lBe6q1QMvhv9Rt4GqN9LGM8NYRx+Ikd10oYYxG+4p+MnanMzw2WoqsfKHxbIObf Jm/qJ2GwoxMvXX7ZwCuVXoIZAgZkxcAuXfNgk13rwlRaBGzfobVJnu6EZRRsPFI/PQ N0hTZQGeVzEiZxOdAdOmtuJ3PVWSLS3+zBU7x1ao=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.178.20] ([91.61.54.37]) by mail.gmx.net (mrgmx105 [212.227.17.168]) with ESMTPSA (Nemesis) id 1MtOKc-1mP7Q126iU-00usXA for <xml2rfc-dev@ietf.org>; Thu, 27 Jan 2022 07:40:15 +0100
Message-ID: <7f87902c-a5bf-43fa-5ab6-f76d92619d8f@gmx.de>
Date: Thu, 27 Jan 2022 07:40:14 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0
To: xml2rfc-dev@ietf.org
References: <Ye/CSVZZnKrN+T2K@miek.nl> <cf002966-48ee-06b3-cc60-e52a865743b3@staff.ietf.org> <33F0F5FB-5CBC-4D6D-BFB7-18AC9798C720@ietf.org> <997C8D93-EF22-42D3-A0A4-9C04EDAEF464@tzi.org> <725DB532-FB23-41C1-9AC4-10D2C020CAA4@ietf.org>
From: Julian Reschke <julian.reschke@gmx.de>
In-Reply-To: <725DB532-FB23-41C1-9AC4-10D2C020CAA4@ietf.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:/feO0iTgEUWsv3zjNvyuPIreDKet3mbKdLGyeExLBl3Kon0FOrq tcjmKXCmhM34e406izLztP3/LCP53C3dyTyKLh8zhnB0gnKTPe+hyx17MB/pls8l5YJn9Ny xepakt1Apxtf433XLrCBPq7YBkN7VNZ0sWa8u+0surtxCfe+k7AETp3o9YcO8hmCFOsCX2F 32hP0OFqst9SEadem/FgQ==
X-UI-Out-Filterresults: notjunk:1;V03:K0:COPLqbwuWeI=:EsNXK7M78eh5UwuYrLFAaA rcjZk36znswukN88N8SvCQxQfFlIoTy5MfbEKB6pTnkNsnWtTU7H3k4d0YeF1eExlrbwxoyma Qc2Y8j54AdI53hZoPDQECM11yhNZCYnNPvQRy7kIrLXEUfjY6ipuOanNu8WL8d+2+aw2u5oBA UIrjbM917EDYSymI2If0uHKL1oSyHCQAzsxsPj4qSnLeS8fIm57pk7gFnmCZbp5X9YlrD5b4a ByxLru6PsXOd1vKZlEabEoHJBpIVT+yFY2CkPcm1FM5b0XM/jOgACGfKMbsqxFF0jXAOeTVhi xJEM/yU9Y744wHl+alZuaplVlH/q9XiDc2RfFmTJhuqgPes+LUa7nJqMc8xOiNR78uHOrgORG D66pbyNsAeGpG3CL8F4vXRKq1ZOiuYDTntAVyTpoZKZmserKnhzI7hxtXbFSZrivtY2XDDKzJ xIYWs/JUKY4MKJ1xO1Qo8q7lBE+Vpp6Qq/JgIQtuJKbrkPffsXuVlGzHsYLOho/H/j5szkJAA lN1Tgu88LDPtjDDIEd6losUI2QB/ksJE/HTfgDAHX47DI+ypTQknA+xLrugeBJY9whgfoJHyq /pN0Z3Iaog5ghe+Uj6AqAXsy/q0p2cnDxYZUZbzVy59B94lzVD6z/3e087pL/F0vzTp0mMd/s oHZ8y5yy18ieq93kJ4Xh52M1C49yrhHCr81eVG3ilP9mdMvraStFIh0byLsDZCFuhpZBsrdTX zTZsbfrHomWBe8k23PABTs2DSS145JTwOME/mOskN4e38I2Czn1AieyKBmkv4n6sM/SAymLQU jDlDtZ2KKV6Zlj0shtlH2sw/5SPCAqtEtlpPVUOx74+JmuUJyALcdesZQRfe5k/w6qisiGUbC mxgmPYpg3fA7M81QoG2/x7fmR2i2wh+LuY466BDaw6dLLRYVCHoAR0HZ7GPIiZyF3q8bd7/Qv 3Su4F6QHyorPgcdalL9ZNdV4H4kZTse9EFgDs+gz+eqzAxGkcnP6ETcwBGSCh9zqjaawRhSYT IGH5keN5vCqDHViWhrgABLAPoFgiV1YIpJLZ5BwCZtT8gvW+g3yGIixLdp/h9uuA4G9i7dqTB qP4Z3orwINAiec=
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/o1_Fm3DFxhMJntE4bodeZQD2v7c>
Subject: Re: [xml2rfc-dev] --table-borders
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: Thu, 27 Jan 2022 06:40:25 -0000

Am 26.01.2022 um 23:52 schrieb Jay Daley:
> ...
>> That was an anti-goal of the 779* design work, which intended to have the xml capture the semantics of the document, and not provide layout instructions. If we do as you suggest, that's a big shift in requirements on the vocabulary, and pushes for much more frequent vocabulary version changes does it not?
>
> We have features such as the newline attribute in the <dl> element that appear to be layout only and Carsten has listed some others below.

That is true, but we really tried to minimize the number of knobs.

*If* we want to provide some control over table styling, a single binary
switch won't be that helpful. Note that we had many more in V2.

>> There will also be (and have been) arguments about including _anything_ in the vocabulary that would influence the behavior of only one of the renderers.
>
> We already have that with the type="svg" attribute of the <artwork> element, which is arguably has a much bigger impact than a table border.

I don't think this falls into the same category.

>> On 27/01/2022, at 11:41 AM, Carsten Bormann <cabo@tzi.org> wrote:
>>
>> On 26. Jan 2022, at 22:38, Jay Daley <exec-director@ietf.org> wrote:
>>>
>>> Personally speaking, I agree with Miek that all formatting should be controlled within the document and not externally in the tool.
>>
>> +1.
>>
>>> So yes, it should go and if the functionality is needed then it should be a new language feature.

At least we shouldn't get us into a situation where there's extra
metadata needed to create the RFC TXT versions (thus all of these should
be the same).

>...
>>
>> The fact that, without Henrik, we have grammar ossification, means that we probably can’t fix anything before we get a v3.1.
>
> We have the XML and Style Guide Change Management Team https://mailarchive.ietf.org/arch/browse/xml-sg-cmt/
 > ...

It would be awesome if the visibility of this would be greater. I really
would like to be able to at least *subscribe* to this mailing list so
that I see what's currently discussed.

Just in this month I see a re-opening of an issue (<postal>) which was
supposed to be closed with consensus many months ago, and a discussion
about referenceGroup titles that's related to a vocabulary ticket I
opened over five years ago.

Best regards, Julian