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

Julian Reschke <julian.reschke@gmx.de> Wed, 02 October 2019 03:45 UTC

Return-Path: <julian.reschke@gmx.de>
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 76D6C120288 for <xml2rfc-dev@ietfa.amsl.com>; Tue, 1 Oct 2019 20:45:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=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 (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 DJqJP5WP3HTp for <xml2rfc-dev@ietfa.amsl.com>; Tue, 1 Oct 2019 20:45:41 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (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 74CB5120096 for <xml2rfc-dev@ietf.org>; Tue, 1 Oct 2019 20:45:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1569987934; bh=J9phVugKt005m5fXjfTWftwO7qnTu15Zi/tbwtcOK00=; h=X-UI-Sender-Class:Subject:To:Cc:References:From:Date:In-Reply-To; b=WcheZbmQ7q/ZTW+FGiSNoav8WHtkVyqEei1MYC7T/k5Xxi4r3KdYdF0E0xXzt6frE gYHr7GlF89mc+pJtTEBZXAOxDWKdGlIORzbgEOyoDAnm3cNFjMnGEtnwpAsu0XAQUa /29wob/p9Lz96zG0Rv4yo936aNur0vC0whoDWTvU=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.178.124] ([84.171.159.18]) by mail.gmx.com (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1MHGCo-1iJvQs2DKq-00DKFe; Wed, 02 Oct 2019 05:45:34 +0200
To: Heather Flanagan <rse@rfc-editor.org>
Cc: XML Developer List <xml2rfc-dev@ietf.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>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <db200ee8-e042-cdc1-2058-5afcc4d4cd57@gmx.de>
Date: Wed, 02 Oct 2019 05:45:32 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <DD4A3091-9E2B-417A-AF3A-8A44AFBBE60E@rfc-editor.org>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:ZqVOieNIIKixIy5+hiaqmu3rSHET9lIAMYb7At9nBgZNBNN6WXd M21ENlYYFUAprwiuFAAdP40tnbI0eA5Q2qb8/6wn1vPchkcrS0VYCnOh4tOaEcnUMLl4y3c 3yPqi78pH1y/pykw4MThX+JQNvVtUW70qM5SMoi1Q0pVZiBKK8Y4mdetxMeYpCpf7xzrF0m c3V2IJbDbKIGEc4Hu6dDw==
X-UI-Out-Filterresults: notjunk:1;V03:K0:RWuf/IB7W08=:WaFYKMfsVXEvTnNoKv1Iys VKwOQ9hs2P6Pbl0ShYPtestbvQb7asS/1qTq/0s8uXjpQ1UzJ0bseYJUb6fDxgGQEAIVOJ/Qs l4p/UVhlMgOhlB0c89bM7C6MzuQ8T5jgSBBvrTOvcSu8+IunTEhp2RcPDS3ZOXN0VCECVBYGh b1eddgHtbKb9Q8vbPIEVN9S4Lv9tUdQ3uvBXeAmJ/DKVJUX6SnuUXydgZ2fJ7tKPPlKAesuIb +DoZli6WJcp5t2HatPPb+tSz+wzoTIrCW6SfBRTLLRnSpm10YMFwGQLmgFuQeefg0xlT+y5Mo kkWd4p42K4y6PTn6yiC4hWmD42dnJJqsC7MVQb8VJsXt8TK7zfXeijAn9FleaFFezoSBanHUB ercFDhwPnlOGt2PGiFvG4NWGmq2ZXKIeA6RMQJyGqlaHxZMlvPKwHPj5XX6tHd0kZ2pPZHra6 fNZzDgdfADPW3X4W7fdvW44g7VrcUHzbWU4AEtkuQxNFzZZS91toZkGpuS44enOwXx7WgLFRg RsAb6B8xAwmxWQ9B9DkHPei7VwElyoCug0MxFZLhzwq6NGyfF/OJygyQwObtW/wnaavUebM53 9ShG/GGVsvfyL9SEPQqMYTT8E3pa63xbhRQ9m4wCufiQBgcbYb8RLUQpb7n4NU5xseBf5bk0Q F2wrhP/RtPNZsQiJzT7UzazrKzENhkBuIQhfQW8yAAAWJuq6FD30lNvv1qppvy5oE0VUT8y0z s/shxGVU0RQZn/IQxnFhi+KgLbdbYJESywj2YM2GMsJ2oB3dV15VVPH//EsQnLYDZ2asy6/5L 1Z9Q4C9kmZ87quRbOx4NWHosGD57idY9e6QOL3obwxFeoNh7jf1giK5HDbwPr0ErGrtcBJE2d URgSvsIdzuHy3fTdoo6rI4rCbmbqlYOGy3kE37qQikrxiW8jlkVz9UWbbAT5m7L+59EJt/peY V7irkgfONe2DeuSc1iwBGZ7Ss8eYx+z4CA/6LRQNxaIuG3LYvh7hWB1IGg8rKNMt/I4WEqx4y bPnfAu3A5JMW1Pbxsb2mdhRUGps3a9JPIkT+fxIjeEfJ/JZX6lj0ynR0+y89qUeX5WOfAsNH/ 5eHMOuz9+0n7rQqbCEibuHMlfVBYnjq1ubVIIHJMsqeNM1E8zF1BMq9wPSdGvc61X1/2hB/Fm +UxkveoP65obaV5yXAd8yLDlExxK13gFd31bB4jlyxOUOqVWX2jMVhpk8Zx9eI6tXRRZxipSF YkzR95ZJcUeVoA4+koXY/LDN6dIfmzBpNhWfBgGJRtoSZn4iRlPvVZcFucvI=
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/TQ6oZpDhNfmq6MFV_aWUAsYpxtA>
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 03:45:44 -0000

On 01.10.2019 23:19, Heather Flanagan wrote:
> ...
>>> "<t>The author's name (initial followed by family name) appears on the
>>> first line of the heading.  Some variation, such as additional
>>> initials or capitalization of family name, is acceptable.  Once the
>>> author has selected how their name should appear, they should use
>>> that display consistently in all of their documents.</t>"
>>
>> That's about the front page, not for references.
>
> Iirc, we’ve always tried to be consistent between what’s on the front
> page and what’s in the references.
> ...

Well, but we are not consistent right now.

>> For the latter, the draft style guide says in
>> <https://tools.ietf.org/html/draft-flanagan-7322bis-03#section-4.8.6.4>:
>>
>>>   [SYMBOLIC-TAG]  Last name, First initial., Ed. (if applicable) and
>>>   First initial.  Last name, Ed. (if applicable), "I-D Title", Internet
>>>   Draft, draft-string-NN, Month Year.
>>
>> Note: "first initial”.
>
> “Second initial if provided” is a really ugly example, but I can add it
> if you think it’s critical.

That would still be inconsistent with the front page, no?

> ...
>>>> 4) A URI ontools.ietf.org <http://tools.ietf.org/>is inserted that
>>>> I'd prefer not to have here.
>>>
>>> Why not? I think having a URI makes a lot of sense.
>>
>> The style guide doesn't say so. The author didn't provide one. Why is
>> the tool inserting something automatically? Also, why totools.ietf.org
>> <http://tools.ietf.org/>?
>> Are you planning to put that into the style guide?
>
> Well, there are always things the authors don’t provide that are
> automatically added. And since we’ve been talking about making sure that
> internal links to specific sections are included (which perforce MUST go
> to tools references) the thought was to be consistent and have the
> reference point to the same place that the internal section pointers are
> going to send people. I think it would be confusing to have one set of
> links go one place, and another set of links to somewhere entirely
> different.

Well.

Right now the tools target is only inserted when none is specified, so
this is not in line what you're arguing for.

Also, for RFCs the target uses https://www.rfc-editor.org/info/rfcNNNN,
which also is not the URI used for the section links.

Best regards, Julian