RE: ORCID - unique identifiers for contributors

"Pat Thaler" <pthaler@broadcom.com> Tue, 17 September 2013 17:24 UTC

Return-Path: <pthaler@broadcom.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 57BF311E82A8 for <ietf@ietfa.amsl.com>; Tue, 17 Sep 2013 10:24:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 yr4PZaUzoEa8 for <ietf@ietfa.amsl.com>; Tue, 17 Sep 2013 10:24:18 -0700 (PDT)
Received: from mms3.broadcom.com (mms3.broadcom.com [216.31.210.19]) by ietfa.amsl.com (Postfix) with ESMTP id 4E7E711E82C5 for <ietf@ietf.org>; Tue, 17 Sep 2013 10:24:18 -0700 (PDT)
Received: from [10.9.208.55] by mms3.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.5)); Tue, 17 Sep 2013 10:13:32 -0700
X-Server-Uuid: B86B6450-0931-4310-942E-F00ED04CA7AF
Received: from SJEXCHCAS07.corp.ad.broadcom.com (10.16.203.16) by IRVEXCHCAS07.corp.ad.broadcom.com (10.9.208.55) with Microsoft SMTP Server (TLS) id 14.1.438.0; Tue, 17 Sep 2013 10:22:43 -0700
Received: from SJEXCHMB09.corp.ad.broadcom.com ( [fe80::3da7:665e:cc78:181f]) by SJEXCHCAS07.corp.ad.broadcom.com ( [::1]) with mapi id 14.01.0438.000; Tue, 17 Sep 2013 10:22:43 -0700
From: Pat Thaler <pthaler@broadcom.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>, Andy Mabbett <andy@pigsonthewing.org.uk>
Subject: RE: ORCID - unique identifiers for contributors
Thread-Topic: ORCID - unique identifiers for contributors
Thread-Index: AQHOsuq8XtChe2oIG0G6Gq7VfssM55nJP9qAgAAHKYCAAAiAAIAAJluAgADTagCAAAMigIAABXwAgAAIRoD//9SoYA==
Date: Tue, 17 Sep 2013 17:22:42 +0000
Message-ID: <EB9B93801780FD4CA165E0FBCB3C3E672AEF2334@SJEXCHMB09.corp.ad.broadcom.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>
In-Reply-To: <5238517F.8060705@joelhalpern.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.16.203.100]
MIME-Version: 1.0
X-WSS-ID: 7E2652302L885585386-10-01
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Cc: "ietf@ietf.org" <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: Tue, 17 Sep 2013 17:24:24 -0000

Given this comment in John Levin's post: " PS: Now that I think about it, you can already put in a personal URL
in rfc2xml, so if someone wants to use an ORCID URL, they can do so
right now." it seems like there isn't any need to change the schema.

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Joel M. Halpern
Sent: Tuesday, September 17, 2013 5:57 AM
To: Andy Mabbett
Cc: ietf@ietf.org
Subject: Re: ORCID - unique identifiers for contributors

Heather Flanagan can be most easily reached at
rfc-editor@rfc-editor.org, the specified email address for reaching the 
rfc-editor.
Note however that you need to be clear as to what you are asking her. 
If you are asking that she arrange for the tools to include provision 
for using ORCHIDs, that is a reasonable request.  SUch a request would 
presumably be prioritized along with the other tooling improvement that 
are under consideration.

On the other hand, if youa re asking that the IETF endorse or encourage 
such uses, there are two problems.  First, the RFC Editor does not speak 
for the IETF.  You need to actually get a determination of IETF rough 
consensus on the ietf email list.  That consensus would need to be based 
on a more specific question than "do we want to allow ORCHIDs", and then 
would be judged on that question by the IETF chair.

Yours,
Joel M. Halpern

On 9/17/13 8:26 AM, Andy Mabbett wrote:
> On 17 September 2013 13:07, Melinda Shore <melinda.shore@gmail.com> wrote:
>> I'm not sure much needs to be done other than talking with Heather
>> Flanagan (the RFC Editor), getting her sign-off, and then getting
>> it into the xml2rfc schema and noting its existence.
>
> Thank you. Is Heather on this list?
>
>> I hope that what's going on here is *not* that there's been
>> little uptake and you're trying to promote its use.
>
> On the contrary; the uptake from both individuals, and organisations
> incorporating ORCID into their publishing workflows - is impressive,
> as you can see form reading the ORCID website & blog.
>