TinCan and The Confusion About the Next Generation of SCORM

Christian Glahn, , May 22, 2013
Commentary by Stephen Downes

This is a really useful post. It begins by deflating some misconceptions about TinCan replacing SCORM, and proceeds to offer a much wider description of ADL's overall plan. In a nutshell, writes Christian Glahn, e-learning today has become distributed, collaborative, networked, continuous (etc etc), and so, "this creates tensions with the centralised, single interfaced, individual learning, and course-centred concepts of SCORM." So by 2011 ADL decided to rewrite the specification. TinCan, or the Experience API, constitutes only the first part of this. The Training and Learning Architecture (or TLA) has, he writes, "four essential parts that are intended to extend the present capabilities of SCORM for maintaining interoperability in modern learning environments:" the Experience API and learning record stores (LRS), the content broker, learner profiles, and competence networks. See also tincanapi.co.uk and see also this response from Michael Roberts.

Views: 0 today, 110 total (since January 1, 2017).[Direct Link]
Creative Commons License. gRSShopper

Copyright 2015 Stephen Downes ~ Contact: stephen@downes.ca
This page generated by gRSShopper.
Last Updated: Oct 19, 2017 12:30 p.m.