Re: ORCID - unique identifiers for bibliographers

"John Levine" <johnl@taugh.com> Mon, 16 September 2013 19:25 UTC

Return-Path: <johnl@iecc.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 C801111E831D for <ietf@ietfa.amsl.com>; Mon, 16 Sep 2013 12:25:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.468
X-Spam-Level:
X-Spam-Status: No, score=-101.468 tagged_above=-999 required=5 tests=[AWL=-1.469, BAYES_50=0.001, 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 NP+lc7eaVYWy for <ietf@ietfa.amsl.com>; Mon, 16 Sep 2013 12:25:27 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id E6F4911E8319 for <ietf@ietf.org>; Mon, 16 Sep 2013 12:25:18 -0700 (PDT)
Received: (qmail 98464 invoked from network); 16 Sep 2013 19:25:17 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 16 Sep 2013 19:25:17 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=52375b1d.xn--30v786c.k1309; i=johnl@user.iecc.com; bh=Ix0ffpFLc1HdyCbp9vAEIVKJuMVSe7mXrmsF+cSav/Y=; b=XNWnRB8VjUT6O7bUuu8y7QLItm2j0a5hBY/dtzQpxn0V3S7vQ4ECNLHDTy9OryZ1S9c1w/WDzixXCJGLz7/2rWTewD2B1C0b01n6xQEnuJXx5ALdboUrcaRLJ3aNwoYdwGx2IlQFRyDE/a5VbWIE9l3shFe4rqwbLU1Lsv6qGabJ9u+WFWJD/DGc2eb17sy236x9BlJbhWWcO/Tlr+GWunvMjELfvvQD+Pdhn7HqlZkD7302T9q5CpQ5TFa/kats
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=52375b1d.xn--30v786c.k1309; olt=johnl@user.iecc.com; bh=Ix0ffpFLc1HdyCbp9vAEIVKJuMVSe7mXrmsF+cSav/Y=; b=T2ebIMjuPc9r4v+YhBRpovu7ftvrBJw4gJ+wpmkwTt2CuQlPax6YCB2VhCcCeEUBsCWb5JvitF9poLOwvs/n7Yv0pZrk69byM7KTmVdBkzL2PIVyPup+V4Svh1slmItAzyyNOSMF2hCB5CCJK/FU/oOesBcRA3ah6jcPKMPXdVmz19oYQbUwCgSwDvzgop0V7Su6nqEIHcx9ctKtksm9y26bdX9uwUflymlTPYQgEOpIgocTU/CscMrUvn5aDl3p
Date: Mon, 16 Sep 2013 19:24:54 -0000
Message-ID: <20130916192454.86555.qmail@joyce.lan>
From: John Levine <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: ORCID - unique identifiers for bibliographers
In-Reply-To: <CABiXOEnZADr5dkd2G6XG_qx-7L+gbnuWJxCvSqvxjMqRSUuWNw@mail.gmail.com>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
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 19:25:32 -0000

>* The purpose of ORCID is to /uniquely/ identify individuals, both to
>differentiate between people with similar names, and to unify works
>where the author uses variant or changed names

If you think that's a good idea, I don't see any reason to forbid
people from including an ORCID along with the real contact info, but I
would be extremely unhappy if the IETF were to mandate it or anything
like it.

My name turns out to be fairly common.  Over the years, I have been
confused with a comp sci professor in Edinburgh, a psychology
professor in Pittsburgh, another comp sci researcher in Georgia, a
psychiatrist in Cambridge MA, a composer in Cambridge UK, a car buyer
in Phoenix, and some random guy in Brooklyn, all of whom happen to be
named John Levine.  Tough.  Not my problem.

I also think that it's time for people to get over the "someone might
spam me so I'm going to hide" nonsense.  The point of putting contact
info in an RFC is so that people can contact you, and the most
ubiquitous contact identifiers we have remain e-mail addresses.  I
still use the same e-mail address I've had since 1993 (the one in the
signature below), and my garden variety spam filters are quite able to
keep it usable.  If I can do it, so can you.

Regards,
John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. http://jl.ly