Re: ORCID - unique identifiers for contributors

Melinda Shore <melinda.shore@gmail.com> Tue, 17 September 2013 18:19 UTC

Return-Path: <melinda.shore@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 B79D211E854D for <ietf@ietfa.amsl.com>; Tue, 17 Sep 2013 11:19:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
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 HB8T9SKd3x+S for <ietf@ietfa.amsl.com>; Tue, 17 Sep 2013 11:19:19 -0700 (PDT)
Received: from mail-pd0-x22c.google.com (mail-pd0-x22c.google.com [IPv6:2607:f8b0:400e:c02::22c]) by ietfa.amsl.com (Postfix) with ESMTP id B40FF11E855C for <ietf@ietf.org>; Tue, 17 Sep 2013 11:19:16 -0700 (PDT)
Received: by mail-pd0-f172.google.com with SMTP id z10so5948483pdj.31 for <ietf@ietf.org>; Tue, 17 Sep 2013 11:19:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=pCMgVzTpRJBIXsOXe4FhGV4Ar37j++hNud4qFGDWCwc=; b=Lt+yUeu39T+K14duTerTlQYd1rKEmACO5NeVHPGW0NPfrWkI3zHehIXkgb/ypfeN0c T/6bzIktkbuii13YPD8sVnnH5BF3XERHbFqd6Rq5j+Oy0tSDlieaYYM2aF4x3TaXT4KK IGZar5oSOGkG7jyQoRln2wwDg6lEe6eg9mZuH5U6/ODueXSbgmHALLdnlMDw2ZbMRh7T Bmy910gYJelAUv070eNlZFOVYTCxGkXGicn+4yyXGdmvEm0FfWeNBDPFoY2HsKuwEu8T 6X9DGVew3BAhrOw5ts1pcrUfsD5VCTj4QqNL5CMHhJRFD1voL58Hk7D23ht5z4kwHCSF 4w8w==
X-Received: by 10.67.30.100 with SMTP id kd4mr38863318pad.24.1379441956382; Tue, 17 Sep 2013 11:19:16 -0700 (PDT)
Received: from spandex.local (66-230-85-52-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.85.52]) by mx.google.com with ESMTPSA id wp8sm39797430pbc.26.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 17 Sep 2013 11:19:15 -0700 (PDT)
Message-ID: <52389D20.1080008@gmail.com>
Date: Tue, 17 Sep 2013 10:19:12 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: ORCID - unique identifiers for contributors
References: <20130916203141.86927.qmail@joyce.lan> <C65F64A8-2D7B-47AF-BAAC-DE4DE57586B7@checkpoint.com> <523791FB.2070807@gmail.com> <CABiXOEm+D4oE7NePHmR5gviOJURqkSAhDhGb=s1o1ayJZAc7kQ@mail.gmail.com> <523845F5.9050902@gmail.com> <CABiXOEmhe5p8jMW2W=9qnhUZ_ORhwKCgA1_-dxK_NtGNy7g1zA@mail.gmail.com> <5238517F.8060705@joelhalpern.com> <6014.1379431237@sandelman.ca> <A3B67B91B80804CC611555AD@JcK-HP8200.jck.com> <A6729341-EF60-40A3-830E-2138A6A60AEE@shinkuro.com> <7406B04A-903D-4765-9FC1-4880F68DD9FF@lurchi.franken.de> <CAPv4CP-2h_=GnO7JQPPhFc=TFn5kinmWaurZUn4B0G69vhWE7g@mail.gmail.com> <E664BD6A-EADF-4FAF-A2A6-F0429595989C@lurchi.franken.de>
In-Reply-To: <E664BD6A-EADF-4FAF-A2A6-F0429595989C@lurchi.franken.de>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
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: Tue, 17 Sep 2013 18:19:19 -0000

On 9/17/13 9:55 AM, Michael Tuexen wrote:
> ... and that is my point. One level of indirection might be useful here.
> I would prefer to update only one mapping and not go through a list
> of RFCs and change the mapping for each document.

I really think that you all are completely over-engineering
this.  But that's what I think.  What I *know* is that you're
looking at this from the perspective of IETF contributors.
Librarians have a problem, too, and the ORCID stuff primarily
addresses that problem, not ours.

There's been a long history of difficulty in name usage on
documents and that's confounded librarians, who for some
reason (<- sarcasm) feel the need to be able to group works by the same
author.  This has been dealt with through authority control
mechanisms, where the cataloger tries to ascertain if
a given "Scott Smith" is the same person as one of the
many other Scott Smiths already in the catalog, and if not,
creates a new authority record.  Discrimination is encoded
in the authority records in the form of middle names/initials,
dates of birth and death, etc.  Again, this is something the
*cataloger* does, and it's actually rather difficult.  So,
in a cataloging record the contents of the author field are
normalized under authority control and the author name as it
appears on the title page is carried in the body of the
cataloging record, and not indexed.

There's a quite good discussion of this here:
http://kcoyle.blogspot.com/2007/09/name-authority-control-aka-name.html

What ORCID does is allow the author to help catalogers out
by providing a unifying identifier.  It's not intended to
be authenticative or provide identity information - it just
helps group documents (which is why I think it belongs in a
separate piece of metadata).  I don't think this is a huge
deal and i don't think it requires community consensus.  I
imagine most IETF authors, who for the most part are not
academics, will bother with it, and that's just fine.

Melinda