What is Tin Can?

This is next in a series of related posts on Fun Tech Stuff going under the hood with XML and its uses in learning technologies: Learning Management SystemsSCORMTin CanMetadata, and XML, as well as examples of XML in SCORM and XML in eBooks.

The Tin Can application programming interface, or API, (also known as The Experience API or xAPI) is the next generation of SCORM.

Why is it worthwhile to evolve a new standard for learning content? We’ve seen how the SCORM standard can enable Web-based online learning content and a learning management system (LMS) to communicate, and it does a fine job of it. But here’s what it doesn’t do.

  • SCORM is not useful outside the context of an LMS. Tin Can is more versatile because it can manage information about learning that happens both inside and outside of an LMS.
  • SCORM can’t manage any learning that takes place outside of a Web browser. Tin Can is more useful because it can manage information about learning that happens both inside and outside of a Web browser.

What kind of learning happens outside of an LMS and outside of a Web browser? Learning based on mobile apps, for one. And learning that starts on a mobile app or in a classroom and ends up in a Web browser. Or learning that is hosted on a server that is separate from an LMS. Or learning that is based on games or simulations. Or learning that is informal, like learning that occurs via YouTube, a book, a TED talk, a conference program, a Wikipedia article, or a mentoring session. Tin Can can also track information that is interactive, or team-based, or long-term, or based on real-world performance. Because Tin Can handles a much wider set of learning situations, it can provide a much more accurate picture of learners and learning. It also does the usual things you’d expect, such as tracking completion, tracking time, tracking pass/fail, and reporting scores. Tin Can can report more fully on learning because of its wider scope and because more information is collected, which can be broken out or consolidated in many different ways. Many authoring tools (e.g., Articulate Storyline, Lectora) generate output for SCORM, as well as for Tin Can. And even though Tin Can expands the range of learning that can be tracked and decouples the hosting of learning content from its tracking, existing SCORM-based content is usable in a Tin Can environment with an appropriate software interface.

So what does Tin Can look like?

At its heart is a learning record with a date and time stamp that contains a statement in the form Actor – Verb – Object. This statement describes a learning event:

Mike Jones Watched ‘TED video Simon Sinek on how great leaders inspire action’
Gerry Brady Completed ‘Cable Box Z30 Repair’ with score 256
Gerry Brady Completed ‘Cable Box Z30 Repair Workbook’
Loretta Smith Read ‘How To Make an eBook’
Clark Kent Passed ‘Introduction to Flying’

Learners can use Tin Can–enabled Web browser plug-ins and mobile apps to capture and send such learning events to a Learning Record Store, or LRS.

tincan1

The Tin Can API defines how software applications build and report on the learning experiences described by the learning record statements in the LRS, and all the related information necessary to support it.

Because Tin Can is an open standard, the learning records in an LRS can be scrutinized in many ways, and information in multiple LRSs can be shared, consolidated, and analyzed as necessary. A learner can also post learning records to multiple LRSs.

tincan2

The learning records in an LRS can also be accessed and reported on by an LMS with the proper software interface, as constrained by the LMS’s reporting capabilities.

tincan3

Training and Performance

The Tin Can API is based on another specification called Activity Streams, which can record anything somebody does. The core Actor – Verb – Object parts of a Tin Can statement (e.g., “I Did This”), derive from the core Activity Streams specification. This means that it is possible to capture performance data as well, and correlate it with training data. For example, an LRS could record the following:

Gerry Brady Completed ‘Cable Box Z30 Repair’ with score 256
Gerry Brady Completed ‘Cable Box Z30 Repair Workbook’
Gerry Brady Successfully repaired ‘Cable Box Z30’ 30 out of 32 times

Tin Can is still a work in progress, but it provides the flexibility and openness to capture formal, as well as informal and social learning and performance as it actually happens. Like SCORM, Tin Can is overseen by Advanced Distributed Learning, a research group sponsored by the United States Department of Defense.

Both SCORM and Tin Can are examples of metadata, or information about information, which is the topic of our next post.

For further information:

http://scorm.com/tincan/

http://tincanapi.com/

http://www.adlnet.gov/

What is SCORM?

This is next in a series of related posts on Fun Tech Stuff going under the hood with XML and its uses in learning technologies: Learning Management SystemsSCORMTin CanMetadata, and XML, as well as examples of XML in SCORM and XML in eBooks.

SCORM stands for “Sharable Content Object Reference Model.” It is a set of technical standards that define how Web-based online learning content and LMSs communicate with each other. SCORM is managed by Advanced Distributed Learning (http://www.adlnet.gov/), a research group sponsored by the United States Department of Defense.

SCORM is composed of three sub-specifications: the content packaging section, the run-time section, and the sequencing section.

scorm

The content packaging section specifies how the content should be packaged and described. For example, it specifies that all the content should be contained either in a directory or a zip file. And it specifies that the content must contain an XML file named imsmanifest.xml, which contains all the information the LMS needs in order to deliver the content. The XML manifest file describes the parts of the course, and puts the parts into a hierarchical order. Any SCORM-compliant authoring tool would put its course material in a directory or a zip file, and would include an XML manifest file describing the course. And any SCORM-compliant LMS would know where to look for these files and know what to do with them. (More on XML and manifest files in a future post: they turn up in all kinds of interesting places, including in ebooks.)

The run-time section specifies how the content should be launched and how it communicates with the LMS using its APIs, or application programming interfaces. These APIs permit the LMS and the learning module to communicate with each other via Javascript by using a built-in vocabulary. The learning module can tell the LMS whether the learner passed the module, what grade was achieved, how much time was taken, and other information relevant to course management.

The sequencing section specifies how the learner can navigate between the parts of the course. Like the content packaging section, it is defined by a set of rules and attributes in an XML manifest file. For example, the sequencing section defines which navigation controls the learner will see, determines whether there will be a navigable table of contents, defines any prerequisites within the content, controls which questions display, and determines whether the learner will be taken back to any sections not mastered.

The SCORM specification has evolved over the years. Two versions have gained widespread acceptance: SCORM 1.2 and SCORM 2004.

SCORM continues to evolve. The next generation of SCORM is called the Tin Can API, which we’ll talk about in the next post.

 

What is an LMS?

This is the first of a related series of posts on Fun Tech Stuff going under the hood with XML and its uses in learning technologies: Learning Management Systems, SCORMTin CanMetadata, and XML, as well as examples of XML in SCORM and XML in eBooks.

When you take an online class, you typically go to a Web site, sign in with a login and password, and see a class or a list of classes you are scheduled to take. After going through the material, you and your organization usually receive some sort of notification of completion, and depending on the curriculum, you may be queued up to take the next class. Along with the course material, your learning experience was brought to you by an LMS.

lms

An LMS, or Learning Management System (LMS) is a software application that provides a framework for the course material, and takes care of all the back-end administration that is necessary to make the learning experience happen. This includes a wide range of functionality, including:

  • course registration and profile management
  • course sequencing and scheduling
  • instructional content management and delivery
  • testing and assessment
  • tracking and reporting of individual progress
  • tracking and reporting of organizational progress

Colleges and universities use LMSs like Blackboard and Moodle to deliver online courses, and corporate training departments use a wide variety of LMSs to deliver online learning, finding them very handy for tracking such things as compliance training and continuing professional education.

Since the LMS provides a framework for course material, it has to be able to handle courses developed by a wide range of authoring systems. How can this happen? Through the magic of standards. If an LMS supports the relevant standard, in this case a standard called SCORM, and the authoring tool supports it, then the content produced by the authoring tool will play well with the LMS. Most LMSs on the market today are SCORM-compliant.

SCORM stands for “Sharable Content Object Reference Model,” and is the de facto industry standard for e-learning interoperability. In the next post we’ll take a closer look at SCORM.