Introduction

This page describes registrations in the URN-space urn:schac:personalUniqueCode:nl.

These values are used to express specific types of identification numbers (as described below) for use with the following attribute:

• urn:mace:terena.org:attribute-def:schacPersonalUniqueCode (deprecated)
  
• urn:schac:attribute-def:schacPersonalUniqueCode
• urn:oid:1.3.6.1.4.1.25178.1.2.14
  

See the SCHema for ACademia Wiki for more information about this attribute. The upstream registry for the namespace  urn:schac:personalUniqueCode:* can be found at https://wiki.refeds.org/display/STAN/SCHAC+URN+Registry. For examples and notes for usage in SURFconext, see Attributes in SURFconext.

Syntax

Delegations in this space are of the following form:

• urn:schac:personalUniqueCode:nl:<scope>:*

where

• <scope> identifies the scope for the identifier. Currently, only local is allowed, which specifies that the identifier is meant for use within a specific institution only.

For the local scope, the urn is of the following form:

• urn:schac:personalUniqueCode:nl:local:<organisation_id>:<id_type>:<id_token>

where

• <organisation_id> identifies the organisation which has issued the specified identifier. The format is a domain name as specified in RFC 1035. For use in SURFconext, this identifier MUST be equal to the organisation's 
• schacHomeOrganization. 
• <id_type> identifies the type of the identifier. The following values are allowed:
  • employeeid: the following id_token specifies an employee of the organisation
  • studentid: the following id_token specifies a student of the organisation
  • memberid: the following id_token specifies a person with some kind of generic membership of the organisation. This could be used by organisations which use a common identifier for employees and students.

• <id_token> is the internal identifier of the specified type, issued by the specified organisation. Note that the identifier should be a proper URN, so the <id_token> may only consist of the characters specified in section 2.2 of RFC2141, i.e. only the following are allowed:

  • lower case letter (a-z)

  • capital letters (A-Z)

  • numbers (0-9)

  • the following special characters: ( ) + , . = @ ; $ _ ! * ' -

Delegation

Legacy delegations