IETF Logo Mail Archive

Re: [xml2rfc-dev] V3 breakage in formatting internet draft references

Carsten Bormann <cabo@tzi.org> Wed, 02 October 2019 10:10 UTC

Return-Path: <cabo@tzi.org>
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 4B23912006A for <xml2rfc-dev@ietfa.amsl.com>; Wed, 2 Oct 2019 03:10:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level:
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_NONE=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 8DdGdWGAZjqP for <xml2rfc-dev@ietfa.amsl.com>; Wed, 2 Oct 2019 03:10:48 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6CAF8120122 for <xml2rfc-dev@ietf.org>; Wed, 2 Oct 2019 03:10:48 -0700 (PDT)
Received: from [10.159.97.60] (ewa_guest_internet_sthlm_nat2.ericsson.net [192.176.1.97]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 46jsN656Rhz10D4; Wed, 2 Oct 2019 12:10:46 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <DD4A3091-9E2B-417A-AF3A-8A44AFBBE60E@rfc-editor.org>
Date: Wed, 02 Oct 2019 12:10:46 +0200
Cc: Julian Reschke <julian.reschke@gmx.de>, XML Developer List <xml2rfc-dev@ietf.org>
X-Mao-Original-Outgoing-Id: 591703844.120478-14655f876a36f1b890eda0adbbb46264
Content-Transfer-Encoding: quoted-printable
Message-Id: <DC201108-B26F-4700-923D-924CEBBC0260@tzi.org>
References: <7e8bb742-1939-b48c-e7f7-03f3bec6bd63@gmx.de> <6F5868A8-56F3-4E26-B297-2CE0BD765397@rfc-editor.org> <b750c06e-caab-40e9-617d-57e0f79ff585@gmx.de> <DD4A3091-9E2B-417A-AF3A-8A44AFBBE60E@rfc-editor.org>
To: Heather Flanagan <rse@rfc-editor.org>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/pRDHRdPjyvd-zsmsL08ysAMWz_Q>
Subject: Re: [xml2rfc-dev] V3 breakage in formatting internet draft references
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, 02 Oct 2019 10:10:51 -0000

On Oct 1, 2019, at 23:19, Heather Flanagan <rse@rfc-editor.org> wrote:
> 
> “Second initial if provided” is a really ugly example, but I can add it if you think it’s critical.

How does that work?

I have a second initial that I’m not using.  If I started doing that, there would be a hodgepodge of citations, and people would start copying that initial over to citations that don’t have it and delete it from citations that do.

Heck, I’m happy when people don’t use Dave Borman’s last name for citing my documents (*), so I don’t know why we have to facilitate even more inconsistency between citation authors.

(There may be a purpose on earth for an explicit override that a citation author can invoke using some arduous ceremony if absolutely needed.  The normal case it should be not.)

Grüße, Carsten

(*) e.g., in RFC 3374, 3409, 4376, 4628, 4896 (three times).  
Sheesh, I never grepped for that before, I didn’t even know the extent of the problem…

v2.23.0 | Report a Bug | By Email