skip to main page content CETIS: Click here to return to the homepage
the centre for educational technology interoperability standards

skip over the long navigation bar
Press centre

Inside Cetis
what is Cetis?
Contact us
Cetis staff
Jobs at CETIS


XML: Click here to get the news as an RSS XML file XML: Click here to get the news as an Atom XML file iCAL: Click here to get the events as an iCalendar file

what are learning technology standards?
who's involved?
who's doing what?

CETIS Groups
what are cetis groups?
what difference can they make?
Assessment SIG
Educational Content SIG
Enterprise SIG
Metadata SIG
Life Long Learning Group
Portfolio SIG
Accessibility Group
Pedagogy Forum
Developer's forum

Accessibility (310)
Assessment (74)
Content (283)
Metadata (195)
Pedagogy (34)
Profile (138)
Tools (197)
For Developers (569)
For Educators (344)
For Managers (339)
For Members (584)
SCORM (118)
AICC (18)
CEN (34)
DCMI (36)
EML (47)
IEEE (79)
IMS (302)
ISO (21)
OAI (24)
OKI (20)
W3C (37)

print this article (opens in new window) view printer-friendly version (opens in new window)

MIT's Open Knowledge Initiative releases first APIs

MIT have released the first set of Application Programming Interfaces for the Open Knowledge Initiative - a project aiming to produce an open architecture for educational software.

The release of the APIs is an important milestone for the project, which has raised expectations in the education community with its promise of free, open-source, standards-based components for building Learning Management Systems and Virtual Learning Environments.

The first set of API's aim to provide a common services framework. The set includes:

  • Authentication
  • Shared
  • Logging
  • Authorization
  • Scheduling
  • Rules
  • Usermessaging
  • DBC
  • LUID
  • File
For each of the available APIs, the OKI project provides technical documentation, Java code, and code examples.

Currently only the Authentication and Shared APIs have been published on the OKI website; although MIT indicate that the other API specifications will be "available soon".


The Authentication API provides a standard process for gathering security credentials from an 'agent' (either a person or another program), and for establishing their authenticity.

Security credentials typically consist of a user name and password, but can include certificates, cookies, and security protocols such as Kerberos and Shibboleth.

According to MIT, the OKI authentication API allows applications to "determine and manipulate the authentication status of an agent without having to manage the details of a particular institution's environment."


The Shared API specification provides interfaces for the 'players' in an OKI application, such as Agents and Groups. It provides a standard way to define Agents - either people or applications - so that they can take part in OKI transactions such as authentication and logging. The API also includes the base Exception class for OKI error handling.

This API is a much more fundamental piece of the OKI architecture than the Authentication API, and forms the basis of the Common Services layer.

Both API definitions are available from the OKI website from today. We'll take a look at them in more detail soon.

Related items:


Creative Commons License This work is licensed under a Creative Commons License.

syndication |publisher's statement |contact us |privacy policy

 go to start of page content