IETF Logo Mail Archive

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

Robert Sparks <rjsparks@nostrum.com> Wed, 26 January 2022 21:55 UTC

Return-Path: <rjsparks@nostrum.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 2E72F3A2402; Wed, 26 Jan 2022 13:55:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.994
X-Spam-Level:
X-Spam-Status: No, score=-1.994 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, KHOP_HELO_FCRDNS=0.399, NICE_REPLY_A=-0.714, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.com
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 TOf5uZxAKwdJ; Wed, 26 Jan 2022 13:55:27 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 1A4B23A23FE; Wed, 26 Jan 2022 13:55:27 -0800 (PST)
Received: from [192.168.1.114] ([47.186.48.51]) (authenticated bits=0) by nostrum.com (8.17.1/8.16.1) with ESMTPSA id 20QLtNML072610 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Wed, 26 Jan 2022 15:55:24 -0600 (CST) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1643234124; bh=8IZhc2r4VfxzMys7PXADGkd1dyOYdkTEierACfppNT4=; h=Date:Subject:To:Cc:References:From:In-Reply-To; b=QowGcRUJN4+RZcOwdObG+PDvVQVW72SigdaDWWF2aYCNg/1OOQ+0zAneXJ5IW0ZJZ NjjkkAJkeCtte853Xt+MBoj4ghF4Kh4GdESIQxCWHPLOoLRwP40XTA9sTQ2ynvh7BJ +FAzkOxIIxQjs5NsjRFnjWocmoFUISLf6aPpKRlc=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.48.51] claimed to be [192.168.1.114]
Message-ID: <674b7b1f-5afd-f893-7573-1a4b93fc4ed8@nostrum.com>
Date: Wed, 26 Jan 2022 15:55:18 -0600
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.5.0
Content-Language: en-US
To: Jay Daley <exec-director@ietf.org>, Kesara Rathnayake <kesara@staff.ietf.org>
Cc: 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>
From: Robert Sparks <rjsparks@nostrum.com>
In-Reply-To: <33F0F5FB-5CBC-4D6D-BFB7-18AC9798C720@ietf.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/XMBQjyUso9tzklJbMHb_Yu4OQTs>
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: Wed, 26 Jan 2022 21:55:31 -0000

On 1/26/22 3:38 PM, Jay Daley wrote:
>
>> On 26/01/2022, at 5:48 PM, Kesara Rathnayake <kesara@staff.ietf.org> wrote:
>>
>>
>>
>> On 25/01/22 10:26 pm, Miek Gieben wrote:
>>> Hello,
>>> xml2rfc has gained a --table-borders flag, which changes how tables are rendered (in text,
>>> didn't check the html). There is another way of changing how a document looks and that is
>>> the indexInclude attribute in the <rfc> tag.
>>> I think/feel that any option that changes the look of the document should be included in
>>> the rfc tag? Or that we default to only one way of doing things. I.e. indexInclude only
>>> works when there are <iref>s so why not make it always true? This might involve more
>>> discussion for table borders...
>> --table-borders flag only has visible differences in text mode [1].
>> Shall we stick with one border style for text outputs and get rid of this flag?
> Personally speaking, I agree with Miek that all formatting should be controlled within the document and not externally in the tool.  So yes, it should go and if the functionality is needed then it should be a new language feature.
>
> Jay

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?

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.


>
>>   --Kesara
>>
>> [1] https://trac.ietf.org/trac/xml2rfc/browser/trunk/cli/tests/valid/manpage.txt#L4159
>>
>>> Regards,
>>> /Miek
>>> -- 
>>> Miek Gieben
>>> _______________________________________________
>>> xml2rfc-dev mailing list
>>> xml2rfc-dev@ietf.org
>>> https://www.ietf.org/mailman/listinfo/xml2rfc-dev
>> -- 
>> Kesara Rathnayake
>> Senior Software Development Engineer - IETF LLC
>> kesara@staff.ietf.org
>>
>> _______________________________________________
>> xml2rfc-dev mailing list
>> xml2rfc-dev@ietf.org
>> https://www.ietf.org/mailman/listinfo/xml2rfc-dev
>>

v2.23.0 | Report a Bug | By Email