IETF Logo Mail Archive

Re: ORCID - unique identifiers for contributors

Andy Mabbett <andy@pigsonthewing.org.uk> Tue, 17 September 2013 11:57 UTC

Return-Path: <pigsotwing@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 1279411E83EF for <ietf@ietfa.amsl.com>; Tue, 17 Sep 2013 04:57:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.739
X-Spam-Level:
X-Spam-Status: No, score=-1.739 tagged_above=-999 required=5 tests=[AWL=0.239, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 Q1m+KIyvgvGg for <ietf@ietfa.amsl.com>; Tue, 17 Sep 2013 04:57:01 -0700 (PDT)
Received: from mail-ob0-x22d.google.com (mail-ob0-x22d.google.com [IPv6:2607:f8b0:4003:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id A503E11E8100 for <ietf@ietf.org>; Tue, 17 Sep 2013 04:56:46 -0700 (PDT)
Received: by mail-ob0-f173.google.com with SMTP id vb8so5226703obc.32 for <ietf@ietf.org>; Tue, 17 Sep 2013 04:56:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:content-type; bh=DAJPq6W2tg71bAVrW4OhVbZfH+iftR7yv1FTSnk64YI=; b=CiY3+dekFqHZvrv2Vb1sRdFbdbzeETeZuNPDQ4JQc6XsBm9VW25zqUCx2Qod6TfczZ B4D7ipfiHdqupMRmsucQXYjHGcG1iFz+ePwXEWL4fwWVDcWhTbgSGv1k+7uqf8UF7CGJ DGlAir3zZU3Mt5yCK04g8UA6Pe7J9Zb9oHxHaL5JW7x91F2gKKe14DGn9qXRWprr47kw KEVBR/86tz8LJeVM0+XI/yoMTpikYjX+UzAJV5RUHw98By+5cz+r1whlHKi3TGR46Pky dzg9o6g6hYB37jzDdj5VJ9ebySTqP7ZhYTMamPIcVDK1VIpWdSSQSBRVQvnlU8ztjEkt fW2w==
X-Received: by 10.60.102.237 with SMTP id fr13mr5749204oeb.20.1379419005946; Tue, 17 Sep 2013 04:56:45 -0700 (PDT)
MIME-Version: 1.0
Sender: pigsotwing@gmail.com
Received: by 10.182.45.6 with HTTP; Tue, 17 Sep 2013 04:56:04 -0700 (PDT)
In-Reply-To: <523791FB.2070807@gmail.com>
References: <20130916203141.86927.qmail@joyce.lan> <C65F64A8-2D7B-47AF-BAAC-DE4DE57586B7@checkpoint.com> <523791FB.2070807@gmail.com>
From: Andy Mabbett <andy@pigsonthewing.org.uk>
Date: Tue, 17 Sep 2013 12:56:04 +0100
X-Google-Sender-Auth: eVpN-j3dkY-uEdD2XdgYrv2p5kM
Message-ID: <CABiXOEm+D4oE7NePHmR5gviOJURqkSAhDhGb=s1o1ayJZAc7kQ@mail.gmail.com>
Subject: Re: ORCID - unique identifiers for contributors
To: ietf@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"
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 11:57:06 -0000

On 17 September 2013 00:19, Melinda Shore <melinda.shore@gmail.com> wrote:

>  I don't see any real downside to allowing
> people who have ORCIDs to put them in IETF documents.  I'm not
> sure there's a lot of demand for them (this is the first time
> it's come up, as far as I know) but I don't see a problem with
> plopping one more piece of information - one that has a unique
> function - into our docs.

Thank you. So how might we raise awareness of ORCID among RfC
contributors and and encourage its use by them?

Is there a "how to" guide or FAQ where it could be mentioned? How
might we get the IETF to agree to wording along the lines of "the IETF
encourages (or "recommends" or "requests") contributors to register
for an ORCID and to include it..."?

-- 
Andy Mabbett
@pigsonthewing
http://pigsonthewing.org.uk

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