Re: [rfc-i] Fwd: Re: [xml2rfc] Change in the results of using the "author" tag

Martin J. Dürst <duerst@it.aoyama.ac.jp> Fri, 12 April 2019 08:51 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 F1E351201C9 for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Fri, 12 Apr 2019 01:51:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.02
X-Spam-Level:
X-Spam-Status: No, score=-4.02 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, FROM_EXCESS_BASE64=0.979, HEADER_FROM_DIFFERENT_DOMAINS=0.001, 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=itaoyama.onmicrosoft.com
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 aCl6iI9jHkfU for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Fri, 12 Apr 2019 01:51:05 -0700 (PDT)
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 E784A120096 for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Fri, 12 Apr 2019 01:51:05 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 40981B82810; Fri, 12 Apr 2019 01:51:00 -0700 (PDT)
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 8A50AB82810; Fri, 12 Apr 2019 01:50:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=itaoyama.onmicrosoft.com
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 lwUNsjB2Eolf; Fri, 12 Apr 2019 01:50:56 -0700 (PDT)
Received: from JPN01-OS2-obe.outbound.protection.outlook.com (mail-eopbgr1410092.outbound.protection.outlook.com [40.107.141.92]) by rfc-editor.org (Postfix) with ESMTPS id 50EDFB8280E; Fri, 12 Apr 2019 01:50:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=itaoyama.onmicrosoft.com; s=selector1-it-aoyama-ac-jp; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=6n+Hgu3dC2r6JiBXrGXo0lCrkATtz8O4C61xJPdA4og=; b=gUxFEsQnT/fteP3XUztnhZMYJTmZWM3Rix8m1HTSjpujW/sQ1ZzoCVG5bxi6ApVz1eal+xdWIPP+g4ywhLSAKGnVhMZv3tkDBeGF2gqS1j9omHyI5fSps+4ZvJCQ4gwdvG1zYcqm1YshVtPh477fKDODbv4+kjYdD49IytfQ1Ps=
Received: from TYAPR01MB5149.jpnprd01.prod.outlook.com (20.179.187.18) by TYAPR01MB2509.jpnprd01.prod.outlook.com (20.177.103.12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1771.16; Fri, 12 Apr 2019 08:50:59 +0000
Received: from TYAPR01MB5149.jpnprd01.prod.outlook.com ([fe80::b4c8:597f:753c:6fba]) by TYAPR01MB5149.jpnprd01.prod.outlook.com ([fe80::b4c8:597f:753c:6fba%3]) with mapi id 15.20.1771.019; Fri, 12 Apr 2019 08:50:59 +0000
From: "Martin J. Dürst" <duerst@it.aoyama.ac.jp>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Charlie Perkins <charles.perkins@earthlink.net>, Heather Flanagan <rse@rfc-editor.org>
Thread-Topic: [rfc-i] Fwd: Re: [xml2rfc] Change in the results of using the "author" tag
Thread-Index: AQHU8HfEIaGO7XNJVkuKXsW6WiV/7KY3vxIAgAB5sAA=
Date: Fri, 12 Apr 2019 08:50:59 +0000
Message-ID: <1d48bb83-cbd3-4111-aae1-cf5b5516dd9b@it.aoyama.ac.jp>
References: <baa28eec-5e09-d691-125f-988f0c04e8cd@gmx.de> <bdcc7321-a53f-4d7c-71eb-0662db5950f0@earthlink.net> <c23b9acd-2954-2b5e-0c30-ab717b53e1db@gmail.com>
In-Reply-To: <c23b9acd-2954-2b5e-0c30-ab717b53e1db@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-clientproxiedby: TYAPR01CA0163.jpnprd01.prod.outlook.com (2603:1096:404:7e::31) To TYAPR01MB5149.jpnprd01.prod.outlook.com (2603:1096:404:12e::18)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=duerst@it.aoyama.ac.jp;
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [133.2.210.64]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: c22af53a-00fd-4e41-9089-08d6bf23fbc6
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(7021145)(8989299)(4534185)(7022145)(4603075)(4627221)(201702281549075)(8990200)(7048125)(7024125)(7025125)(7027125)(7023125)(5600139)(711020)(4605104)(2017052603328)(7193020); SRVR:TYAPR01MB2509;
x-ms-traffictypediagnostic: TYAPR01MB2509:
x-ms-exchange-purlcount: 3
x-microsoft-antispam-prvs: <TYAPR01MB2509F19BA7421CD6E650F451CA280@TYAPR01MB2509.jpnprd01.prod.outlook.com>
x-forefront-prvs: 0005B05917
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(346002)(376002)(396003)(39840400004)(136003)(366004)(199004)(189003)(110136005)(85202003)(786003)(105586002)(446003)(316002)(71190400001)(71200400001)(106356001)(31686004)(53936002)(99286004)(8676002)(74482002)(31696002)(85182001)(68736007)(52116002)(2906002)(54906003)(86362001)(81166006)(508600001)(81156014)(8936002)(3846002)(6116002)(11346002)(186003)(66066001)(305945005)(7736002)(6486002)(6436002)(97736004)(102836004)(26005)(5660300002)(229853002)(6306002)(6512007)(6506007)(386003)(53546011)(6246003)(4326008)(966005)(14444005)(256004)(486006)(76176011)(14454004)(476003)(25786009)(2616005); DIR:OUT; SFP:1102; SCL:1; SRVR:TYAPR01MB2509; H:TYAPR01MB5149.jpnprd01.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:0; MX:1;
received-spf: None (protection.outlook.com: it.aoyama.ac.jp does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: jE2tz3xFA7UsP3aEm5+ewHMOt4GIHjmPEq+6+pNIkuzBYx/TtOm8Xcix0FjpJjw8afyjcEGUnzgqdqspfzy5hBafnhoBALKaAmMTpAc4Yjnp2X9cMwHNVQxTAsDpQWV0ZZ8E6jK34cwexM2E+iTmzdwAk2XNjf2VTTzM8cCedjE3+L+SLNWbTLy4/CgWL08JaY9U/CqtuIZxIjyTmWSSjUJPZGHO74d/uNKb+jf/bgj9Mc3BgyCX3MiIetvfT4eNJN9vvg2lQ3v5Z02e6O7gkhCj1iRPRrfiLBEBqRjwWvXpVnsyKkFICQahcuSCOB1Fm9V+EHNTQ65XOTPjSJCbma1MXtv/On+6WCWIHqNFgOE4nQsnjcFKrka/0m4BMT4nnwSzius2zq7RjVyt5nv0u77mcOW386CTYUxbHlJu1ZI=
Content-ID: <35AD7EC7F500C544817D8E00C43690A3@jpnprd01.prod.outlook.com>
MIME-Version: 1.0
X-OriginatorOrg: it.aoyama.ac.jp
X-MS-Exchange-CrossTenant-Network-Message-Id: c22af53a-00fd-4e41-9089-08d6bf23fbc6
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Apr 2019 08:50:59.1520 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: e02030e7-4d45-463e-a968-0290e738c18e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: TYAPR01MB2509
Subject: Re: [rfc-i] Fwd: Re: [xml2rfc] Change in the results of using the "author" tag
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: Julian Reschke <julian.reschke@gmx.de>, "rfc-interest@rfc-editor.org" <rfc-interest@rfc-editor.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

Hello Brian,

On 2019/04/12 10:35, Brian E Carpenter wrote:
> Hi Charlie,
> 
> Sad to say I think you are wrong. Every journal I've ever submitted
> to has its own required style for citations,

Agree; I already said so much in another mail just recently.

> and I'd say that overall
> styles that require or permit given names rather than initials are unusual.
> So the RFC Series is using a fairly standard practice.

This is true too, but it puts people with names such as "Francisca Yu" 
or "John Smith", and Chinese, Koreans, and Danes in general, at a 
disadvantage.

Regards,   Martin.

> For the IEEE's own style, see
> https://ieee-dataport.org/sites/default/files/analysis/27/IEEE%20Citation%20Guidelines.pdf
> 
> This page is quite informative:
> https://pitt.libguides.com/citationhelp
> 
> Or this, for the ACM style:
> http://www.citethisforme.com/guides/association-for-computing-machinery
> 
> Regards
>     Brian Carpenter
> 
> On 10-Apr-19 05:30, Charlie Perkins wrote:
>> Hello Heather and all,
>>
>> I was redirected to ask you instead of xml2rfc...
>>
>> Basically, I think it is wrong to enforce RFC Style Guide limitations when showing the authorship of external documents.  So, for instance, if an external publication shows that the author is "Francisca Yu", I don't think we should require the initialized version in the citation of an IETF document.
>>
>> Regards,
>> Charlie P.
>>
>> PS. No offense to Ms. Yu.
>>
>> PPS. Can someone tell me how to cite a stable URL?
>>
>>
>>
>> -------- Forwarded Message --------
>> Subject: 	Re: [xml2rfc] Change in the results of using the "author" tag
>> Date: 	Tue, 9 Apr 2019 19:10:37 +0200
>> From: 	Julian Reschke <julian.reschke@gmx.de>
>> To: 	Charlie Perkins <charles.perkins@earthlink.net>
>> CC: 	xml2rfc@ietf.org
>>
>>
>>
>> On 09.04.2019 18:43, Charlie Perkins wrote:
>>> Hello Julian,
>>>
>>> I followed your suggestion.  Now it shows that the author is "D. Stanley".
>>>
>>> The actual document shows that the author is "Dorothy Stanley".
>>>
>>> Regardless of what the IETF says about handling names for RFCs, I think
>>> that external citations should reflect the authorship as indicated in
>>> the external publication.
>>
>> Well, that contradicts the RFC Style Guide.
>>
>>> I also tried simply deleting 'initials="D" surname="Stanley"' from the
>>> citation.  xml2rfc imposes the requirement anyway.
>>>
>>> Can we please have it to respect the actual authorship as shown in the
>>> publications which we cite?
>>
>> That's a discussion you need to lead with the RFC Editor, not the tools
>> implementers.
>>
>>> Regards,
>>> Charlie P.
_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest