Re: ORCID - unique identifiers for bibliographers

Phillip Hallam-Baker <hallam@gmail.com> Mon, 16 September 2013 19:41 UTC

Return-Path: <hallam@gmail.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 3E42A21F88FB for <ietf@ietfa.amsl.com>; Mon, 16 Sep 2013 12:41:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.526
X-Spam-Level:
X-Spam-Status: No, score=-2.526 tagged_above=-999 required=5 tests=[AWL=0.073, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
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 z61YnV3wjm-u for <ietf@ietfa.amsl.com>; Mon, 16 Sep 2013 12:41:19 -0700 (PDT)
Received: from mail-lb0-x22f.google.com (mail-lb0-x22f.google.com [IPv6:2a00:1450:4010:c04::22f]) by ietfa.amsl.com (Postfix) with ESMTP id A6E2D11E8321 for <ietf@ietf.org>; Mon, 16 Sep 2013 12:41:18 -0700 (PDT)
Received: by mail-lb0-f175.google.com with SMTP id y6so4568774lbh.34 for <ietf@ietf.org>; Mon, 16 Sep 2013 12:41:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=qkU8N3ceSt4UuahlliYiCaqS4SPayv+7ygX0eM1ZTDc=; b=nYtQOKO9O02NkNSffX7Dy9pXZXuISlnHSKKOAmjXtagAGXuiMA4Tl4gCXC8mxxdc2d KIN0cs9XjWpr+QNmoYpBoB8JrL9UprJ8rgaASvtPlzfBEsMyliN8R+kg5t6VlH95D/0K kyu9ib4o1eBKZy2hF1b38eotY23+78v5G0uqpTsd+4T0yFhGqbZEWL/kx9zr+qRbn1E6 PBlI/sFcW5knWBFmuHMU6Qk/X7nSNYeZzK/G2WjRTPHrnR+vV0fanGnBgyoRYq8/ZpSk a0eNfCI5DtO5RwmdcmaAtKvcOvfBMGkAFoZPV2NVysLrHdaGafZHdXsWuSChIAtfM66S HVtg==
MIME-Version: 1.0
X-Received: by 10.112.89.100 with SMTP id bn4mr26464947lbb.16.1379360477519; Mon, 16 Sep 2013 12:41:17 -0700 (PDT)
Received: by 10.112.148.165 with HTTP; Mon, 16 Sep 2013 12:41:17 -0700 (PDT)
In-Reply-To: <20130916192454.86555.qmail@joyce.lan>
References: <CABiXOEnZADr5dkd2G6XG_qx-7L+gbnuWJxCvSqvxjMqRSUuWNw@mail.gmail.com> <20130916192454.86555.qmail@joyce.lan>
Date: Mon, 16 Sep 2013 15:41:17 -0400
Message-ID: <CAMm+Lwi3+CKd79t0=zwNbcc5bART527iuSHLuYx4bHjavTsb7g@mail.gmail.com>
Subject: Re: ORCID - unique identifiers for bibliographers
From: Phillip Hallam-Baker <hallam@gmail.com>
To: John Levine <johnl@taugh.com>
Content-Type: multipart/alternative; boundary="001a11c379ec47a60f04e6856367"
Cc: IETF Discussion Mailing List <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 19:41:20 -0000

On Mon, Sep 16, 2013 at 3:24 PM, John Levine <johnl@taugh.com> wrote:

> >* 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.
>

+1

I discovered the ambiguity problem 30 years ago and began using the full
version of my family name to ensure uniqueness.

Since this has turned out to be ambiguous, I have decided to instead use a
SHA-256 hash of my DNA sequence:

9f00a4-9d1379-002a03-007184-905f6f-796534-06f9da-304b11-0f88d7-92192e-98b2




-- 
Website: http://hallambaker.com/