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

Heather Flanagan <rse@rfc-editor.org> Mon, 22 April 2019 14:35 UTC

Return-Path: <rse@rfc-editor.org>
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 C945C1200A2; Mon, 22 Apr 2019 07:35:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 g7mKLvYTfo7D; Mon, 22 Apr 2019 07:35:30 -0700 (PDT)
Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C7CB812001B; Mon, 22 Apr 2019 07:35:30 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 357151C1E51; Mon, 22 Apr 2019 07:35:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NFZSMC5d_uVf; Mon, 22 Apr 2019 07:35:12 -0700 (PDT)
Received: from [10.198.42.38] (c-71-231-216-10.hsd1.wa.comcast.net [71.231.216.10]) by c8a.amsl.com (Postfix) with ESMTPSA id D61491C1C11; Mon, 22 Apr 2019 07:35:11 -0700 (PDT)
Date: Mon, 22 Apr 2019 07:35:23 -0700
From: Heather Flanagan <rse@rfc-editor.org>
To: Julian Reschke <julian.reschke@gmx.de>
Cc: "=?utf-8?Q?rfc-markdown=40ietf.org?=" <rfc-markdown@ietf.org>, "=?utf-8?Q?xml2rfc=40ietf.org?=" <xml2rfc@ietf.org>, "=?utf-8?Q?xml2rfc-dev=40ietf.org?=" <xml2rfc-dev@ietf.org>
Message-ID: <2370a17d-b0e4-455e-8d9e-3d8ea13f79b6@Spark>
In-Reply-To: <77365280-3339-499c-db0e-626808ff31dd@gmx.de>
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>
X-Readdle-Message-ID: 2370a17d-b0e4-455e-8d9e-3d8ea13f79b6@Spark
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="5cbdd130_c55abdf_3366"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/uiyNjtnwmoiWMsu44AuV0bof_48>
Subject: Re: [Rfc-markdown] [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, 22 Apr 2019 14:35:33 -0000

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.

-Heather