Re: ORCID - unique identifiers for contributors

John C Klensin <john-ietf@jck.com> Mon, 16 September 2013 18:06 UTC

Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C5AE21F870F for <ietf@ietfa.amsl.com>; Mon, 16 Sep 2013 11:06:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.499
X-Spam-Level:
X-Spam-Status: No, score=-103.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id boD0uOuDpfMp for <ietf@ietfa.amsl.com>; Mon, 16 Sep 2013 11:06:23 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 0EF3021F8613 for <ietf@ietf.org>; Mon, 16 Sep 2013 11:06:22 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1VLdBk-0008kM-4J; Mon, 16 Sep 2013 14:06:20 -0400
Date: Mon, 16 Sep 2013 14:06:15 -0400
From: John C Klensin <john-ietf@jck.com>
To: Andy Mabbett <andy@pigsonthewing.org.uk>
Subject: Re: ORCID - unique identifiers for contributors
Message-ID: <14489380AE3C6658CF8BBE0A@JcK-HP8200.jck.com>
In-Reply-To: <CABiXOEnZADr5dkd2G6XG_qx-7L+gbnuWJxCvSqvxjMqRSUuWNw@mail.gmail.com>
References: <CABiXOE=cbpPigRbqCkZYzgKSN+yiG4HyNznF99WohLc_SByi2g@mail.gmail.com> <5237390E.5040102@bogus.com> <CABiXOEnZADr5dkd2G6XG_qx-7L+gbnuWJxCvSqvxjMqRSUuWNw@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: Heather Flanagan <rse@rfc-editor.org>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Sep 2013 18:06:40 -0000

--On Monday, September 16, 2013 18:34 +0100 Andy Mabbett
<andy@pigsonthewing.org.uk> wrote:

>> If the goal is to include contact info for the authors in the
>> document and in fact you can't be contacted using the info is
>> it contact info?
> 
> While I didn't say that the goal was to provide contact
> info[*], an individual can do so through their ORCID profile,
> which they manage and can update at any time.

The goal of the "author's address" section of the RFCs is
_precisely_ contact information.  See, e.g.,
draft-flanagan-style-02 and its predecessors.  

I can see some advantages in including ORCID or some similar
identifier along with the other contact information.  I've been
particularly concerned about a related issue in which we permit
non-ASCII author names and then have even more trouble keeping
track of equivalences than you "J. Smith" example implies and
for which such an identifier would help.   But, unless we were
to figure out how to require, not only that people have ORCIDs
but that they have and maintain contact information there (not
just "can do so"), I'd consider it useful supplemental
information, not a replacement for the contact information that
is now supposed to be present.

Treating an ORCID (or equivalent) as supplemental would also
avoid requiring the RSE to inquire about guarantees about the
permanence and availability of the relevant database.  It may be
fine; I'd just like to avoid having to go there.

best,
   john