Internet Engineering Task Force K. Hazelton, Ed.
Internet-Draft MACE-Dir
Intended status: Informational October 5, 2015
Expires: April 7, 2016

Trial Version of a MACE-Dir Attribute for ORCID Researcher Identifiers


[ORCID] is an organization that provides persistent digital identifiers for individual researchers as an aid to linking them with their scholarly work products. This document provides an experimental attribute definition intended for use in trials aimed at assessing the practicality and potential value of including ORCID identifiers in attribute assertions.

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

This Internet-Draft will expire on April 7, 2016.

Copyright Notice

Copyright (c) 2015 IETF Trust and the persons identified as the document authors. All rights reserved.

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents ( in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.

Table of Contents

1. Introduction

There are scenarios in which relying parties would like to know researcher identifiers like ORCID for users accessing their services. If the relying party opts to accept ORCID values from external sources, there is a benefit to agreeing on a standard representation of an ORCID identifier. ORCID values might be included in a SAML attribute assertion provided by an Identity Provider to a Relying Party on behalf of a user. The eduPersonOrcid attribute specification in this document is based on the style of attribute specification associated with the [EDUPERSON] work of MACE-Dir. If an IdP includes this attribute in their local directory copy of the eduPerson object class as another optional attribute on person entries, experimental use of this attribute in SAML exchanges can be supported.

2. Requirements Language

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119].

3. Specification

3.1. eduPersonOrcid Attribute

An eduPersonOrcid attribute carries values of the ORCID-assigned researcher identifiers for the associated entry

Application utility class: standard; # of values: multi
Permissible values (if controlled)
Values MUST be valid ORCID identifiers in the ORCID-preferred URL representation (see Example given below)
Each value represents an ORCID identifier registered with as belonging to the entry
Example applications for which this attribute would be useful
NIH/NLM SciENcv self-service web application
Example (LDIF Fragment)
pres, eq

4. Acknowledgements

This document was produced by the MACE-Dir working group. People who made particular contributions to the work include David Bantz, Jim Basney, Scott Cantor, Marlena Erdos, Tom Golson, Mark Jones, Craig Jurney, David Langenberg, Jim Leous, Steve Olshansky, Benn Oshrin, Michael Pelikan, Chris Phillips, Mark Scheible and Bill Weems of MACE-Dir; Geoff Bilder, Laure Haak, Laura Paglione of ORCID and Don Preuss of NIH/NLM.

5. IANA Considerations

This memo includes no request to IANA.

6. Security Considerations

ORCID identifiers are meant to uniquely identify the researcher to whom they are registered, so they are personally identifying information by design. The privacy implications of releasing this attribute need to be understood by the user, the asserting party and the relying party. Appropriate policies need to be defined and followed by all parties.

7. References

7.1. Normative References

[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997.

7.2. Informative References

[EDUPERSON] MACE-Dir, "eduPerson Spcecification", 2013.
[ORCID] ORCID, "ORCID Home Page", 2014.

Author's Address

Keith Hazelton (editor) MACE-Dir 1210 W Dayton St. Madison, Wisconsin 53706 US Phone: +1 608 262 0771 EMail: