Re: [xml2rfc] [Tools-discuss] [Rfc-markdown] New xml2rfc release: v3.16.0

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 20 January 2023 02:15 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3E5DC14F74A; Thu, 19 Jan 2023 18:15:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.099
X-Spam-Level:
X-Spam-Status: No, score=-7.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2NBqNCnP0_8B; Thu, 19 Jan 2023 18:14:59 -0800 (PST)
Received: from mail-pl1-x62a.google.com (mail-pl1-x62a.google.com [IPv6:2607:f8b0:4864:20::62a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 04161C14F737; Thu, 19 Jan 2023 18:14:58 -0800 (PST)
Received: by mail-pl1-x62a.google.com with SMTP id d3so4087527plr.10; Thu, 19 Jan 2023 18:14:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=4K9kmvmPNNJ2HsttWLy6+a4QfZ5TvQV0f9DVvyYaQas=; b=KmBBBOz1UEDoO+hyMzyQ8VifrPg9od6ICzLi7bgnZFFkTBgJ7UvbAAdW2/cTMN4yzQ fbwkikh1Grp1z4zJPENExoiHU0F12Pq0U5BRskPFkDJUfforgs06ZTjo1NJkyRlPxzee ymRCh5nxe4Nt+c6cy9jRXm5lXSsQCIYbuT2nKxgRfBgMcvrNk3S2dFN8XGSgFECj1D7G uwqjYn+kp+YxsCgUWi3kwC0SDi9sy7vpzgkAPqjhx25FGhOK3p2ACy8/MFrnr6T2vn26 Kvx65YSz3gVHz4tBaijpyAZ99Pa7fb7H6vqBxWRwI4I7dAWCe4AC04ABlqy3zIB/NXIi sMdw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=4K9kmvmPNNJ2HsttWLy6+a4QfZ5TvQV0f9DVvyYaQas=; b=4N0VH7hlO3y5pwNKhalJMwE1DT6VIW5AWdGSdgr5Z42VMHuz7zUjDclt93PQjuR0K/ DU/tsbg0EdoLbfineupqAYir9YucAc7/KNUG9Vb53Rspn7YF4Ex7ul2RpfDRJyZ0R3lT NK9o48FuJ0tSJTZaxaH8IEyEVg0JNLvNtTIsD1o1mVC6ed+o3+A+3cyZFQI3wWjaBSe7 y7uzpGSErmXNpDBp+33enUxo4glTqPYGhBhuI5Elkkh4TwRxvBp252A8R4boAwbwg34X EuZGxGYkTs105uJ+UR3Pl59lYv1W/hvPXtDPp4KbcyW9tn97K5TJthxo5W46aNyRNXk2 ZMLA==
X-Gm-Message-State: AFqh2kpKUTsJN9E6xymMmOuyviQ+N4Ed+gcIyOVbPhthd6rRe49EPl3D Jt+7hHZ3TzwM8mKPwH7mGkB3A3KGxfMWBw==
X-Google-Smtp-Source: AMrXdXuAtGMpuBAQhYw0eSXzPO7HzUgwSYBWW8CoBYdcLNCUJAqEhs5XQ1B4t5pYQvRU/4rMNSJ0Ww==
X-Received: by 2002:a17:902:c702:b0:194:8133:765c with SMTP id p2-20020a170902c70200b001948133765cmr10935801plp.50.1674180897869; Thu, 19 Jan 2023 18:14:57 -0800 (PST)
Received: from ?IPV6:2406:e003:10c2:2501:6969:5efe:7979:3937? ([2406:e003:10c2:2501:6969:5efe:7979:3937]) by smtp.gmail.com with ESMTPSA id q14-20020a17090311ce00b00189c536c72asm25829498plh.148.2023.01.19.18.14.55 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 19 Jan 2023 18:14:57 -0800 (PST)
Message-ID: <9b65e230-3da1-3752-3da2-b54f4f15fadd@gmail.com>
Date: Fri, 20 Jan 2023 15:14:53 +1300
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0
Content-Language: en-US
To: Marc Petit-Huguenin <marc@petit-huguenin.org>, Carsten Bormann <cabo@tzi.org>
Cc: "xml2rfc@ietf.org" <xml2rfc@ietf.org>, tools-discuss <tools-discuss@ietf.org>
References: <CAD2=Z87EMetcpv66YY_b2+X1-yFy4cTpKMjPoJL=cH99c7P_Uw@mail.gmail.com> <9d719176-a4eb-7cce-e706-10325700531c@petit-huguenin.org> <F1A5624B-16D0-4463-AC5F-B0A03F3B94B6@ietf.org> <8f5a497e-4135-7c0c-46cb-c3fe4791e9f3@petit-huguenin.org> <3B53040D-9B5F-4410-9029-459729ADFDF8@ietf.org> <7d532a76-c750-8cb6-fc86-f6242da2bc77@petit-huguenin.org> <27182BDD-899E-4238-9DF8-7AE3E0F0C18F@akamai.com> <11a20f42-4fe6-8d8d-1d76-54049d0bdb68@petit-huguenin.org> <6179D431-EC33-49B9-A793-805E926C1050@akamai.com> <6d55cf67-1ce2-8094-dda4-ab877ac2a1d7@petit-huguenin.org> <FD030B37-6910-4E8D-8C03-2CF14B4A2CA9@tzi.org> <4af15ba4-3286-890d-57eb-2f907854a184@petit-huguenin.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <4af15ba4-3286-890d-57eb-2f907854a184@petit-huguenin.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/bM0EyGSui8gdbDnGICf7xoZm-W4>
Subject: Re: [xml2rfc] [Tools-discuss] [Rfc-markdown] New xml2rfc release: v3.16.0
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: XML2RFC discussion list <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jan 2023 02:15:00 -0000

On 20-Jan-23 10:19, Marc Petit-Huguenin wrote:
> On 1/19/23 13:01, Carsten Bormann wrote:
>> On 2023-01-19, at 21:46, Marc Petit-Huguenin <marc@petit-huguenin.org> wrote:
>>>
>>> Because what I find to be problematic is allowing Unicode everywhere.
>>
>> We already allow Unicode everywhere (all that ASCII is Unicode, too).
>>
>> It’s only that some of the Unicode characters are shunned in certain contexts (and these aren’t even exactly the non-ASCII characters).
>>
>> This discussion would be easier to take serious if we could at least get the terminology right.
>>
> 
> You are right.  Replace that by "Because what I find to be problematic is allowing the whole of Unicode everywhere."

As we would also find allowing the whole of SVG anywhere within artwork. But in both cases, the problem is not, in my opinion, one that can be solved by a ruleset. Our experience clearly shows that these are editorial and therefore human questions. If an RFC author wants to mention a café or an example of اردو in running text, a grammar cannot decide whether that is appropriate. Similarly for using a particular unusual format in SVG.

Thinking that we could decide such things robotically was a mistake, IMO.

Of course the decision of principle belongs in the RSWG, but I think our tools need to be pragmatic rather than doctrinaire.

     Brian