IETF Logo Mail Archive

Re: ORCID - unique identifiers for contributors

Dave Cridland <dave@cridland.net> Mon, 16 September 2013 14:49 UTC

Return-Path: <dave@cridland.net>
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 201B411E8124 for <ietf@ietfa.amsl.com>; Mon, 16 Sep 2013 07:49:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 1ZbQ5hGOs-28 for <ietf@ietfa.amsl.com>; Mon, 16 Sep 2013 07:49:51 -0700 (PDT)
Received: from mail-oa0-x231.google.com (mail-oa0-x231.google.com [IPv6:2607:f8b0:4003:c02::231]) by ietfa.amsl.com (Postfix) with ESMTP id 9ACEB11E8114 for <ietf@ietf.org>; Mon, 16 Sep 2013 07:49:51 -0700 (PDT)
Received: by mail-oa0-f49.google.com with SMTP id l17so86423oag.22 for <ietf@ietf.org>; Mon, 16 Sep 2013 07:49:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=dn4n8B8Aw6RjJJw7rSPmjMSMTtWn0RuO4VTOC01JQl4=; b=PfGgjctay5oJSh3Aft703d1+TuAU77l4rRWHuaJzQw/cYx5viz/jXSGNrI/KcMCVbM XnnqfE92uJ38cEwGhtpbLBWUsnXPDBxZ/9kb+AoYVkyoARSYhennqOq/aLJEG92B+qto l3K8zepAD2gCc2bZtsD+Nq41uRpgKZyhCiaks=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=dn4n8B8Aw6RjJJw7rSPmjMSMTtWn0RuO4VTOC01JQl4=; b=YAIb4O2m3kTEJnZjEhMXUJpAR2TWL/I72ZAEcGHTIoXyp2zwFf9KPnoRibGdrMqn2F UMZywoCPbsaUrT1VvaLrYtfWW5ot8MU9FzwH9BCPNTT3RO2P/ZhsDZI6daw3BST0kM62 5Bba+7bGXDJYq9hWi5U7izkLmKikYNAgIOSVuTar84Z8W1QvBKb7b53KES7/E1jBHAOW 3vwUo3lzfcmVbI5Usw7GZHba7Dzx19qgOd48BcWd81jNh0qu9wwDGAWetH5FhMaRFAcJ aUjcyMtBrYop9UZP+iVYiijj+umMVCnuIzQ1lDzwblk0REOgn1AleGqeDToePhh+IED/ OqrQ==
X-Gm-Message-State: ALoCoQlcoc80tEp/k3obUZW1IwqrGrCQQ+EqJiyw/meymhn9+xwPzliuptuEcMsJ6kbyTyIY615I
MIME-Version: 1.0
X-Received: by 10.182.181.34 with SMTP id dt2mr227100obc.30.1379342990074; Mon, 16 Sep 2013 07:49:50 -0700 (PDT)
Received: by 10.60.121.97 with HTTP; Mon, 16 Sep 2013 07:49:50 -0700 (PDT)
In-Reply-To: <CABiXOE=cbpPigRbqCkZYzgKSN+yiG4HyNznF99WohLc_SByi2g@mail.gmail.com>
References: <CABiXOE=cbpPigRbqCkZYzgKSN+yiG4HyNznF99WohLc_SByi2g@mail.gmail.com>
Date: Mon, 16 Sep 2013 15:49:50 +0100
Message-ID: <CAKHUCzyhGBL-pZBm4KexOkmEQNcEAh84WvC9uMcrHi_HYjYFQQ@mail.gmail.com>
Subject: Re: ORCID - unique identifiers for contributors
From: Dave Cridland <dave@cridland.net>
To: Andy Mabbett <andy@pigsonthewing.org.uk>
Content-Type: multipart/alternative; boundary="089e0122aa24f2784504e6815023"
Cc: "ietf@ietf.org Discussion" <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 14:49:52 -0000

On Mon, Sep 16, 2013 at 3:39 PM, Andy Mabbett <andy@pigsonthewing.org.uk>wrote:

> This problem is addressed by "Open Research Contributor Identifiers"
> (ORCID; <http://orcid.org>),  UIDs (and URIs) for scientific and other
> academic authors. Mine is below.
>

There are actually IETF participants who share a name - all poor comments
and suggestions are actually that other Dave Cridland of course - but it's
not clear that this is a problem requiring a centralised registration which
isn't even centralised under the auspices of either the IETF or ISoc.

That's not to say you can't put any particular URI against your name in an
RFC, mind, but I'd be rather hesitant to leap at mandating a registration
procedure for authors.

Dave.

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