IETF Logo Mail Archive

Re: [rfc-i] Unicode names in RFCs and xml2rfc

Julian Reschke <julian.reschke@gmx.de> Fri, 06 December 2019 15:50 UTC

Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36BF2120020 for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Fri, 6 Dec 2019 07:50:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.499
X-Spam-Level:
X-Spam-Status: No, score=-4.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (body has been altered)" 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 psmBEIb0UryN for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Fri, 6 Dec 2019 07:50:23 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7847A120823 for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Fri, 6 Dec 2019 07:50:23 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 7C61CF4071A; Fri, 6 Dec 2019 07:50:18 -0800 (PST)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 5E999F4071A for <rfc-interest@rfc-editor.org>; Fri, 6 Dec 2019 07:50:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gmx.net
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ft_0d2oGvKCx for <rfc-interest@rfc-editor.org>; Fri, 6 Dec 2019 07:50:16 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) by rfc-editor.org (Postfix) with ESMTPS id E0C85F40712 for <rfc-interest@rfc-editor.org>; Fri, 6 Dec 2019 07:50:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1575647397; bh=hB0LzKdga7fb3o4CPlYR1aIAvsoLxXmjzM3vMpu7tX8=; h=X-UI-Sender-Class:Subject:To:Cc:References:From:Date:In-Reply-To; b=OrEVURrMBSPQ+M5h9dVrmO22gKGZocmmZVsVuhNeNLE+7nXBu9oPBw3VBul6PPe6T O7aXOOIQTcvHT27LVJSBV56NgxcsXBsWd6zkWImnfreMkKHZe8hT0kkZAyKafO8UP6 1tSaGsB2La+PP4I2OuP3hMmiRjIDIMSHu5Y3F+VA=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.178.124] ([93.203.239.90]) by mail.gmx.com (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1MV67o-1iDJHW3Rji-00S6ht; Fri, 06 Dec 2019 16:49:56 +0100
To: Henrik Levkowetz <henrik@levkowetz.com>, Carsten Bormann <cabo@tzi.org>
References: <76d730cb-9fe1-4572-acbe-8db5bc0bd598@www.fastmail.com> <8813e75d-f541-94ea-6c6a-14b624ae1850@levkowetz.com> <82ef4920-f193-49d6-9105-cd51cd834c30@www.fastmail.com> <6718ee2f-d081-156e-224e-da4a1ceb5300@levkowetz.com> <E6C61494-1808-4B32-BA5E-F67898441503@tzi.org> <1c2a3559-e436-483b-30ac-addc250d4c3d@levkowetz.com>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <91def230-cc37-177e-9a08-344685c1ed0c@gmx.de>
Date: Fri, 06 Dec 2019 16:49:55 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <1c2a3559-e436-483b-30ac-addc250d4c3d@levkowetz.com>
Content-Language: en-US
X-Provags-ID: V03:K1:F9Dp7qOYJ0Jsg23FmgFO3dwgwQELXmns8vSJcIvFaNfUBdrpzO8 YtqwIR/A8KXU0s60QKaS88ETqscYkLcR/W0GHA+Blmb7CBWKKBjXviMLdBNcdlysO87SJbi F37dm3LfAX8tiyADG1XfauH0+tVx4978NLR27xBb9UpDqCBfPlaws4KRATHYoNV68ZUOe2h QC19Zrk4gfbGy5ZgF3HnQ==
X-UI-Out-Filterresults: notjunk:1;V03:K0:cCklUiZksIc=:P2YWPx3jIThnT7hasJFz5/ O3qKMiO5NpE6OxZz6MihNo6xIZ5ySo6Tb9bPviw+i5xvXY4kfHlIRqCN4yu3cuKmQm7zXN/tB 9Z5+hH09teThhdjb3kvByJKOVKd7hpfaSM8eCf+ug/UOnbLSuZ9mW4SlOgMDePBOg3OO7Ld7x AEKr/5I3heEXzSy65EhuqjSitCXhuyQyZ5zG35ubeYq+I5oTgvGnvKe9Ha90nB7c/igiLz8Rp qlqwWrg4rU3Z3+vU2Rte58TgHe7I79orhPiCoru4LeVzkeJMePTTVpkGv8JCYmbMu/JTG3mTP V2CHjVtzjDOqB8N6zd2RYt3HXZEGgGoE2dYt4qVufJ0BvO+1051N7rZt3RKAKSJKzGP3B8v3s e3kbS/aziGzkTL9QdLCA+/LmH8KD9J8DprfQgNpOM11DZ/+YfkSGkduR9Qxt5nepojzuaO2R/ ESE15FV8gQehNAYZR2unJhAPx2RNpbhODxkc3AA3g96Kxqapos3xlJxxgl+WWqWq8zoDb9OPk HxWzddAgbpKLJG5pHnzcdUsTXDWUZBwIOO8k5lKaI0T8uwUXIemVhi1qmkwamHIkHcdcjKEMM C3l76hfHqAg5MRx0UWE/dj2FyNaXiZipEiRF8GHkyuCTNC/zBhOi2TLT7+J+fup6ze4q9aPn7 ku8XD6UNhbGM+pNTiQeDhVXshVXLhB0x8awzX3AFRw8Kcysgk7xiiYTvgPGkB3ovvWdEzPbCU W2YfNjtwGww06BG1M8IKGcP59biVtVTyG+54dLuPHGGNgLrQlG0OAajGGTs3H08Uq0onguDkX 73Ipj61/ZQSTn6BX98LY+I0kXdEdfVMAzOdrLJs5xUNQ6eC5rVLmv9q42fOBUeVa6Gf/s+1jP GpvOlbF0rZmb9O8nh5H6yHJRXHiT/UyiDNoSlMAloJxQe4d1PHYn5MrkgdPOzUdY1hNAm4Rug 56xA/DUf9uy6952Oi91k5Wa9qDIG1Ghz8zfkherxd6a5vcsIbPSlh5leOOj2WltUMOBBH1H0a ApBjYkC9ObIgNDmMm3H5oMGKRourLEsz7xjXwCe4rGZB8CTnNIk3kFAlVnWQD+gHdGQDuBGGl 97G2jrQuSA6Le4ale37JgTcr95PcM0LYGXOwYPUtycwqpwE/OmqKBdaiqsvxzJPEn+is3TTOx pRG316SpWxOhgzfxk9xdiDADodm/EvQwQlJWL/qo2vRwl/yZUY/ajJvwC0LFdUWXVy53HYuy8 5m/ieIMLqzQ4/mMxFwhpFb1XiSSVRArMKJ+6VI4rWQXt55eUMPvnCCsAgsW0=
Subject: Re: [rfc-i] Unicode names in RFCs and xml2rfc
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Cc: rfc-interest@rfc-editor.org
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

On 04.12.2019 12:03, Henrik Levkowetz wrote:
> Hi Carsten,
>
> On 2019-12-04 12:00, Carsten Bormann wrote:
>> Hi Henrik,
>>
>> On Dec 4, 2019, at 11:34, Henrik Levkowetz <henrik@levkowetz.com> wrote:
>>>
>>> A <contributor> entry
>>
>> Where can I read up on this?
>> Already checked RFC 7991 and draft-levkowetz-xml2rfc-v3-implementation-notes.
>
> This is a proposal I'm making now, which has grown out of previous
> discussions around the subjects.  It's gradually come together in my
> mind as a reasonable approach to what is clearly an issue experienced
> by document authors.

OK, I see <https://trac.tools.ietf.org/tools/xml2rfc/trac/changeset/3490>.

1) I agree and like the addition of <contact> as block-level element.
This solves the "how to style the contributors section" question we've
ignored for years.

2) Adding "<contact>" as phrase-level element: IMHO not a good idea.

2a) ...because allowing elements to appear both in block context and
flow context is asking for trouble. For instance: what if the <contact>
element inside <t> contains actual postal information?

2b) As I said before, there are more reasons to use non-ASCII than names
of contacts. For instance, what if I want to refer to the title of a
book? I know that this isn't currently mentioned in RFC 7997, but I
think wiring this into the grammar is the wrong approach.

Best regards, Julian
_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest

v2.23.0 | Report a Bug | By Email