Re: ORCID - unique identifiers for contributors

Andy Mabbett <andy@pigsonthewing.org.uk> Wed, 18 September 2013 12:42 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 B91C211E8272 for <ietf@ietfa.amsl.com>; Wed, 18 Sep 2013 05:42:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.811
X-Spam-Level:
X-Spam-Status: No, score=-1.811 tagged_above=-999 required=5 tests=[AWL=0.167, 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 ECHNUZmdf0JJ for <ietf@ietfa.amsl.com>; Wed, 18 Sep 2013 05:42:41 -0700 (PDT)
Received: from mail-ob0-x233.google.com (mail-ob0-x233.google.com [IPv6:2607:f8b0:4003:c01::233]) by ietfa.amsl.com (Postfix) with ESMTP id 3B20611E8264 for <ietf@ietf.org>; Wed, 18 Sep 2013 05:42:41 -0700 (PDT)
Received: by mail-ob0-f179.google.com with SMTP id wn1so7170179obc.38 for <ietf@ietf.org>; Wed, 18 Sep 2013 05:42:40 -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=eVaEwzofmq2fQ4v4kJebmrWZdXXYXXSZjvDxpob0yzU=; b=cfd3kNPJ/ZSEUuNJwBUCdxvvNrBu7f1bxr/ZWyBK9N6KUMrNgSmrI7cj5TOj68PEFP OvI+vGiy3ySaj4ODIVlvrXi1D8xvRkAz8SGMR8pJfzRFpUS0O4StLT8Vx2e56Pl4nOo9 NTwXIhhOHc12XU8o9koO1QXdUSLoVa/VkF1zAmeZMUrjKu/FffOEnYV+ITePLbVsZU7T t3TM5JBvYTZ09kqXGvfZPAUhgldAeNOPBxvtzKz3whOAQagYdmXkKMcHhBTmbulowYCV 9KZ7k1uulBEEmRisVlqPL092VmkTJefU6YmSNd/tQoCFewwiLYloPsjssCiNOiz7P8/5 zVDA==
X-Received: by 10.182.81.41 with SMTP id w9mr10206324obx.18.1379508160672; Wed, 18 Sep 2013 05:42:40 -0700 (PDT)
MIME-Version: 1.0
Sender: pigsotwing@gmail.com
Received: by 10.182.45.6 with HTTP; Wed, 18 Sep 2013 05:41:36 -0700 (PDT)
In-Reply-To: <5238B12C.9020103@isdg.net>
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> <5238B12C.9020103@isdg.net>
From: Andy Mabbett <andy@pigsonthewing.org.uk>
Date: Wed, 18 Sep 2013 13:41:36 +0100
X-Google-Sender-Auth: 60wBHdvG0GnSiBxWmlCjq_mPV2o
Message-ID: <CABiXOEm84ric-tNmDvVYch8iD=Bp+g7Ekg1Mn=BR1F+3BjRtgA@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: Wed, 18 Sep 2013 12:42:41 -0000

On 17 September 2013 20:44, Hector Santos <hsantos@isdg.net> wrote:

> The idea is great.  By why use ORCID?  Why not Facebook? linked-in? etc. So
> many issues when its 3rd party.

Facebook, LinkedIn (and other such services) are commercial, and
proprietary. Their data is not available under a CC0 licence and their
software is not open source. ORCID's - as I've already pointed out -
are.

> While ORCID does offer an API (another
> conflict issue when API changes),

Again, the software and data is open.

> I think the IETF should offer its own
> registry database of contributors.

Why reinvent the wheel?  Even if done, that would not preclude the use of ORCID.

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