IETF Logo Mail Archive

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

Charlie Perkins <charles.perkins@earthlink.net> Thu, 11 April 2019 15:03 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 ACA8312037E for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Thu, 11 Apr 2019 08:03:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.998
X-Spam-Level:
X-Spam-Status: No, score=-4.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=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 (2048-bit key) reason="fail (message has been altered)" header.d=earthlink.net; domainkeys=fail (2048-bit key) reason="fail (message has been altered)" header.from=charles.perkins@earthlink.net header.d=earthlink.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 bxhJ7LiHvkgZ for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Thu, 11 Apr 2019 08:03:44 -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 DA87B120378 for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Thu, 11 Apr 2019 08:03:43 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 6F532B81F73; Thu, 11 Apr 2019 08:03:38 -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 51BB8B81F59; Tue, 9 Apr 2019 10:30:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=earthlink.net; domainkeys=pass (2048-bit key) header.from=charles.perkins@earthlink.net header.d=earthlink.net
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 R8MGzJyaal1K; Tue, 9 Apr 2019 10:30:14 -0700 (PDT)
Received: from elasmtp-mealy.atl.sa.earthlink.net (elasmtp-mealy.atl.sa.earthlink.net [209.86.89.69]) by rfc-editor.org (Postfix) with ESMTPS id 653EEB81F58; Tue, 9 Apr 2019 10:30:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=earthlink.net; s=dk12062016; t=1554831018; bh=FwIDddIif4q2jG28JQIr3EJaLQXJfgB1mAQu wgj+loo=; h=Received:Subject:References:To:Cc:From: X-Forwarded-Message-Id:Message-ID:Date:User-Agent:MIME-Version: In-Reply-To:Content-Type:Content-Language:X-ELNK-Trace: X-Originating-IP; b=XGt4Std33mXPopc2gfnVss+e5IBxt4KnamzXdSSWkPKbku 3hL0HGclwhaJD7IZblZH//haMLw06dK9kRbTAlK7S90CBl4CDczlltKyXUu91TF6Jro Pvued8SKupd7lcKVKBta5AZYB5UFrGZsNSIa9Avq+gaC/LhGgERE4VF4NCrI3u04Q2s eFwYEf6DWeTkq9Ydo3G9tsIjcR6/dGjCqBudpudwjrHI8fj73esNJVDUjJdTzUAHTid g/X7f/W1AahfR7MN67u7wunfwbAMR3MKa6u2ozYf54SK41Ayf2ORLkZa5h32TZI2eoo 7ApxIXbYJN2BHHQoBDSMjvxFHGiw==
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk12062016; d=earthlink.net; b=Dz+Zo5rUoBpVwkO2Ss/EZnpijQOyK1v1O8V+wZznLuuYTCyGf/2qq/88Wws1QmKfEgXACTmrHPXvWBDDOapQvLd+7an42RA+asNEMASMeZ9r7dH1HSnDKPiLoHBfZFV+YToLIJmndVvk5ksLdrYOTT2DyrZd+0mf18UfgPxqcQHeniHWJ0WIhT0CusspPjkdJk0Zl23aAOp069sYqB+1lUtfHpZdoZH2ph0RIMnIUemc4cBw7C/P26bCSLW2tnLx4aThzj8K//LKcScuLmv7C9XMdNmCEhnd6VnuwnHAlRpL1ILU8gGNf5o8DKD9MAmLFK4yaCxQYOjgctaCkYsB/w==; h=Received:Subject:References:To:Cc:From:X-Forwarded-Message-Id:Message-ID:Date:User-Agent:MIME-Version:In-Reply-To:Content-Type:Content-Language:X-ELNK-Trace:X-Originating-IP;
Received: from [99.51.72.196] (helo=[192.168.1.82]) by elasmtp-mealy.atl.sa.earthlink.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4) (envelope-from <charles.perkins@earthlink.net>) id 1hDuZb-0006Pv-QL; Tue, 09 Apr 2019 13:30:15 -0400
References: <baa28eec-5e09-d691-125f-988f0c04e8cd@gmx.de>
To: Heather Flanagan <rse@rfc-editor.org>
From: Charlie Perkins <charles.perkins@earthlink.net>
X-Forwarded-Message-Id: <baa28eec-5e09-d691-125f-988f0c04e8cd@gmx.de>
Message-ID: <bdcc7321-a53f-4d7c-71eb-0662db5950f0@earthlink.net>
Date: Tue, 09 Apr 2019 10:30:13 -0700
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: <baa28eec-5e09-d691-125f-988f0c04e8cd@gmx.de>
Content-Language: en-US
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956846b590522b13c95bcbee175caebfcd30db970789b969503350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.51.72.196
X-Mailman-Approved-At: Thu, 11 Apr 2019 08:03:37 -0700
Subject: [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
Content-Type: multipart/mixed; boundary="===============3165840934623540492=="
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

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.
>
> PS. How to I get a URI to be shown in the citation?  One way that does
> not work is to use
> <uri>https://mentor.ieee.org/802.11/dcn/15/11-15-1261-03-0arc-multicast-performance-optimization-features-overview-for-ietf-nov-2015.ppt</uri>

<https://greenbytes.de/tech/webdav/rfc7749.html#element.reference.attribute.target>

Best regards, Julian

_______________________________________________
xml2rfc mailing list
xml2rfc@ietf.org
https://www.ietf.org/mailman/listinfo/xml2rfc

_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest

v2.23.0 | Report a Bug | By Email