1
To learn more about Project Tin Can, visit TinCanAPI.com.
________________________________________________________________________
Tin Can API (REST binding — version 0.9)
Definitions
Tin Can API (TCAPI): The API defined in this document is the product of “Project
Tin Can”. It’s a simple, lightweight way for any permitted actor to store and retrieve
extensible learning records as well as learner and learning experience profiles, regardless
of the platform used.
Learning Activity Provider (AP): Like a SCORM package, the AP is the software
object that is communicating with the LRS to record information about a learning
experience.
Learning Activity (activity): Like a SCORM activity, the Learning Activity is a unit of
instruction, experience, or performance that is to be tracked.
Statement: A simple statement consisting of <Actor (learner)> <verb> <object>, with
<result>, in <context> to track an aspect of a learning experience. A set of several
statements may be used to track complete details about a learning experience.
Learning Record Store (LRS): An LRS is a system that stores learning information.
Currently, most LRSs are Learning Management Systems (LMSs), however this
document uses the term LRS to be clear that a full LMS is not necessary to implement the
TCAPI.
Learning Management System (LMS): Provides the tracking functionality of an LRS,
but provides additional administrative and reporting functionality. In this document the
term will be used when talking about existing systems that implement learning standards.
Registration: If the LRS is an LMS, it likely has a concept of registration — an instance
of a learner signing up for a particular learning activity. The LMS may also close the
registration at some point when it considers the learning experience to be complete.
For Tin Can purposes, a registration may be applied more broadly; an LMS could
assign a group of students to a group of activities and track all related statements in one
registration. Note: activity providers are cautioned against reporting registrations other
than when assigned by an LRS. An LRS that assigns registrations is likely to reject
statements containing unassigned registration IDs.
State: Similar to SCORM suspend data, but TCAPI State allows storage of arbitrary key/
document pairs. The LRS does not have to retain state once the learning experience is
considered done (LRS has closed its “registration”).
