Re: [Rfc-markdown] [xml2rfc-dev] [xml2rfc] initials handling, was: New xml2rfc release: v2.22.3

Julian Reschke <julian.reschke@gmx.de> Mon, 06 May 2019 11:54 UTC

Return-Path: <julian.reschke@gmx.de>
X-Original-To: rfc-markdown@ietfa.amsl.com
Delivered-To: rfc-markdown@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7EA1C1201A1; Mon, 6 May 2019 04:54:11 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 4_SiEs3Yrafz; Mon, 6 May 2019 04:54:09 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (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 77815120193; Mon, 6 May 2019 04:54:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1557143645; bh=7r0SLqUvmYiUyu0+SpFHpe+cx61PF/ZVOMn3xoXueNQ=; h=X-UI-Sender-Class:Subject:From:To:Cc:References:Date:In-Reply-To; b=dZUcR3KgAtKsZchlbZOG4dLh00N2Jvasy4Xe5p837RjBMtsAbZRC7JM0o691L/9g0 Sr7HjLOJ6zjy4ubdmcYDbB0FX7HciuW/CdMSrRMJOdscXHW/pMGEutXvsUAA7TRIin PKFTBahtybvHlqOXrcoaWkSWHpVCnEhtxQGEyN/M=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.1.34] ([217.91.35.233]) by mail.gmx.com (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1N0FxV-1gUZh42zKR-00xHTk; Mon, 06 May 2019 13:54:05 +0200
From: Julian Reschke <julian.reschke@gmx.de>
To: Heather Flanagan <rse@rfc-editor.org>
Cc: "rfc-markdown@ietf.org" <rfc-markdown@ietf.org>, "xml2rfc@ietf.org" <xml2rfc@ietf.org>, "xml2rfc-dev@ietf.org" <xml2rfc-dev@ietf.org>
References: <E1hDSIW-0008DY-Hl@durif.tools.ietf.org> <c8d8c9e9-88dd-8c49-c1d4-e0438c56a03c@gmx.de> <f41d8ba2-7078-0ffa-3e41-6f8bc1d0f766@levkowetz.com> <dfcbd237-bbff-867d-b704-cb874c4b2ed3@gmx.de> <b760846d-5183-ad8a-dd42-62a7800bdbf6@levkowetz.com> <561D7097-7155-4DDD-8C5D-FA65663B5105@att.com> <280b0cf8-a7d0-0334-42fe-a9cd6e7966d7@gmx.de> <1DC0E053-509F-4531-9EAF-1A287FFA4ECD@att.com> <8cedc522-614c-039c-e550-8f5494ab040f@gmx.de> <308E0D17-7B84-4782-B17D-EE06EE80E6BE@rfc-editor.org> <3A0F4CD6-451F-44E2-9DA4-28235C638588@rfc-editor.org> <77365280-3339-499c-db0e-626808ff31dd@gmx.de> <2370a17d-b0e4-455e-8d9e-3d8ea13f79b6@Spark> <7663a236-9a4e-f8c3-dede-b52171dc63c9@gmx.de>
Message-ID: <0d4455dd-01f8-cec4-7a0f-b372e197e90b@gmx.de>
Date: Mon, 6 May 2019 13:54:06 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <7663a236-9a4e-f8c3-dede-b52171dc63c9@gmx.de>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:+b7LghVqYNxvpEttVvJG+HT+bkcEvfeV4wAAecOcsaxbBbkX4ds 3F8tbffkY0kOY0ud7xQcxAAXv2clhzT+4vaKculAlq8gjFgCHxItUw2IyWYVtGRHg/HqTzz iCmhlT3Uz4iHNfqJUQYer5iBKGMaSPg0/VJKt2hNbHY2rVR9c5DJX4dwqGXVmMY+JCW8Z6i Dde6wfEsFOlNvUu+y3y2g==
X-UI-Out-Filterresults: notjunk:1;V03:K0:Q58l1u/mAsw=:dv8pFuBZg3t3wy128FDFZp 5FEKRHpBpgzv5j7kvuUzQDyRXjA+6CfpazuuCpT2RLKQElbkAB8xAnbl7XByL/iFQ/7rFW6kN pqsfv+KIPPvy0GH6iXOUNmhx7VyydOJ/0hvETjhkV8fBce80Pei8SJE6rvfsfTJRe0mHW2t1D 7IwMsMTF3Tf2Ji0+MqvAI9cPsCOF7a1s5ywC4sPjnU/wdOFfwFIK16DwlvM1aaet/VcHUlvZz cBNeOIBvGNpdRUiYCMscCgYHGn2B2djDi5z10rMMzQEvx30w/76BqCgPOL4pY3n00Q4rIRNv2 Pgqrhl7BGeXmW+OmFWijzw1W2hLIOhes3neA2B+yIMZhnLzP/o9pZ0kyEwivQHnxEi6cJBEko mggVve1WK1KjBzmsLsBSbaJV+HRyHe0sjKSvkKg6veTnhgvCy4yfl5G5+vqgYOXDYtCU50mI9 Omeyd1wW+M1RMYmuvKB+ubCT458sWqRFRyDFqpgZdsomZ41KKflSx7ms1s9zFQ1797hbsi7X3 saf/p1AObKFrjP6jdhQRpGn+McTuomUSPhIVkbfyWEe0nipKx8n6VIirv/UIiK2R7E4sXEYqW XhvNBoIDgi64+cOw9JFpnSNpamLr8ECKHHB5vf/JJhePW2JbmDL2XbxaPIel9mZvyfFWo6R5j qsVZ0BArOm+Vvc4BCao6ecSKRb3ygGaIbbfQi9uH0dbn232qmMyToXNuUOEgrCjBR7iPJs3pf /sbv4eX8fuQZMIXUbCFRBCcwJaii8cT2mV1YUoXnKh3eBwmMbyaiS8a+cfWmPXpeSavA2mKEr lXM2EK7IQaazAA92qdyT3duUu29t5nZHxlK/EByDBdzAJcn1q//dhusx+vcyF4Zr5VT3uIdse lWnTjNH+j8zAqvrkstGqZ9YFhAJV6y6Gr7NyWf8YHsh7SQc7A45JfK8EAX3/9G8sz84+eBzji 8y27VELJjJQ==
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/r5s3ugdUu38KUZVQQvGTGF4veMA>
Subject: Re: [Rfc-markdown] [xml2rfc-dev] [xml2rfc] initials handling, was: New xml2rfc release: v2.22.3
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "rfc-markdown is a discussion list for people writing I-Ds and RFCs in Markdown and the authors of the tools used for that." <rfc-markdown.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-markdown/>
List-Post: <mailto:rfc-markdown@ietf.org>
List-Help: <mailto:rfc-markdown-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 May 2019 11:54:21 -0000

On 22.04.2019 20:31, Julian Reschke wrote:
> On 22.04.2019 16:35, Heather Flanagan wrote:
>> On Apr 21, 2019, 10:23 PM -0700, Julian Reschke <julian.reschke@gmx.de>de>,
>> wrote:
>>> On 11.04.2019 17:06, Heather Flanagan wrote:
>>>> ...
>>>> And coming back to this:
>>>>
>>>> A longstanding principle for referencing RFCs is to make the reference
>>>> match what is on the front page of the RFC itself, over what
>>>> information
>>>> is in any other location. This is something we should be clearer about
>>>> in the Style Guide, but it is a practice we’ve enforced for quite a
>>>> long
>>>> time.
>>>
>>> If you're not planning a revision anytime soon, you may want to document
>>> this in detail at <https://www.rfc-editor.org/styleguide/part2/> or file
>>> an erratum.
>>
>> I agree - I’ll work with the RPC on updating the web portion of the
>> style guide.
>>
>>>
>>>> Changing the tool to match this longstanding practice is not ideal, but
>>>> it is expedient given that the proper way to handle this is an
>>>> extensive
>>>> data cleanup of the citation library. I’ve asked the RPC to prioritize
>>>> getting documents published and format implementation over this kind of
>>>> data cleanup for now.
>>>> ...
>>>
>>> I still don't get this. Is there a well-defined algorithm to decide the
>>> detailed format? I guess so, otherwise it could not be placed into the
>>> formatter. In this case, please publish it. And if there is one, just
>>> get the <reference> files updated accordingly. (And yes, I volunteer, if
>>> the algorithm is clear).
>>>
>>>
>>
>> Ah, volunteering! I love that! Let me talk to Sandy and Alice to see how
>> best to move this forward.
>> ...
>
> Can we start with a precise problem statement? How exactly is the rule
> for initials for author names different in these ancient RFCs?

Hi there once again.

It would be awesome if there was a problem statement for what caused
Henrik to make the change below:

>    * Added special initials handling for RFCs 1272 and below, to apply the
>      single initials handling enforced at that time.

Could somebody please explain what the actual change in handling *is*?
The style guide says in
<https://tools.ietf.org/html/rfc7322#section-4.8.6.2>:

>    For one author or editor:
>
>       [RFCXXXX] Last name, First initial., Ed. (if applicable),
>                 "RFC Title", Sub-series number (if applicable),
>                 RFC number, Date of publication,
>                 <http://www.rfc-editor.org/info/rfc#>.

...so just using the first initial is currently the rule as well.

What *is* the change?

Best regards, Julian