Many JISC-funded projects are involved in the development of important aspects of the technological infrastructure which will support teaching and learning, research and administrative activities across the sector. Other projects may be developing digital content for use across the sector.

But how robust if the technical infrastructure and how sustainable with the content and the services be? Such issues will be dependent on factors such as standards which are used and sustainable business models. But an additional important factor is the persistency of Internet domain names.

The API draft is now available for public viewing and covers:

• Levels of privacy and other contextual terminology.
• Public query API by way of illustrative HTTP query dialogues.
• Protected Data query via OAuth.
  • OAuth Workflow is illustrated in some depth

This is a pre-release of the API; it is nearly there, but it would be foolish to assume that the API will not change if any difficulties arise or if a better way is agreed upon.

Google Doc version of API:

ORCID in a nutshell (current strategy):

• ORCID is a registry of profiles for people involved in research – a profile can be created by the person themselves (self-registry) or by what is termed a Trusted Partner, such as a University or Publisher.
• The people using the system decide who is and is not a researcher, not the system itself.
• A self-registered profile, for “John Smith” for example, can state that it is the same ‘John Smith’ in a profile created by a Trusted Partner and vice-versa.
  

The following is from an email exchange with Nicky Ferguson. These are my answers to the questions
he posed, and as such shouldn’t be considered the opinion of the ORCID project itself. They are the
answers I believe are correct, based on the meetings and discussions I have been part of on the
technical advisory group.

If any other member of the advisory group can correct any inaccuracies in the comments, I’d be
most appreciative.