IETF Logo Mail Archive

Re: ORCID - unique identifiers for contributors

Michael Richardson <mcr@sandelman.ca> Tue, 17 September 2013 15:21 UTC

Return-Path: <mcr@sandelman.ca>
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 62ECE11E845A for <ietf@ietfa.amsl.com>; Tue, 17 Sep 2013 08:21:03 -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=[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 AkdtslmAaw1A for <ietf@ietfa.amsl.com>; Tue, 17 Sep 2013 08:20:59 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3::184]) by ietfa.amsl.com (Postfix) with ESMTP id 7E12611E8474 for <ietf@ietf.org>; Tue, 17 Sep 2013 08:20:55 -0700 (PDT)
Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by tuna.sandelman.ca (Postfix) with ESMTP id 742BE20189 for <ietf@ietf.org>; Tue, 17 Sep 2013 12:29:33 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 57F5B63B18; Tue, 17 Sep 2013 11:20:37 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 48B4A636C7 for <ietf@ietf.org>; Tue, 17 Sep 2013 11:20:37 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: ietf@ietf.org
Subject: Re: ORCID - unique identifiers for contributors
In-Reply-To: <5238517F.8060705@joelhalpern.com>
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>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha1"; protocol="application/pgp-signature"
Date: Tue, 17 Sep 2013 11:20:37 -0400
Message-ID: <6014.1379431237@sandelman.ca>
Sender: mcr@sandelman.ca
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 15:21:03 -0000

I did not know about ORCID before this thread.
I think it is brilliant, and what I've read about the mandate of
orcid.org, and how it is managed, I am enthusiastic.

I agree with what Joel wrote:

Asking for ORCID support in the tool set and asking for IETF endorsement
are two very different things.

Having tool support for it is a necessary first step to permitting IETF
contributors to gain experience with it.   We need that experience before we
can talk about consensus.

So, permit ORCID, but not enforce.
An interesting second (or third) conversation might be about how I could
insert ORCIDs into the meta-data for already published documents.

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        | network architect  [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [

v2.40.4 | Report a Bug | By Email | System Status