Today's sell-out workshop on the Experience API (xAPI but also known as Tin Can API) was full of useful insights from our speakers and delegates.
We even managed to collect two large bags of tins to donate to the All Souls Clubhouse - to distribute to local vulnerable elderly people.
Andy Wooler spoke about Hitachi Data System's long term vision of how they will use "big data" to support learning and development. His description of multiple systems all feeding data into a Learning Record Store (LRS) was compelling.
Stuart Jones (Unicorn Training) then gave a tour around some of the authoring tools on the market and their ability to create xAPI statements. He highlighted the fact that, with xAPI content, you no longer need to host your content inside the LMS. It can be hosted by the content provider or on a Content Delivery Network (CDN) without all the problems associated with trying that with SCORM content.
Ben Betts (HT2) took us into some of the detail of xAPI, how it works in practice and some of the painful lessons he has learned over the past year. He demonstrated Learning Locker, a new, open-source LRS and illustrated how it could capture data from multiple sources. He made an important point that an LRS is a highly-defined piece of software - built to comply with the xAPI specification. It can sit inside a Learning Management System, or outside it.
Andrew Downes (Epic) completed the day with a set of guidelines on how learning experiences should be designed in the light of the xAPI. By thinking about learning as a series of inter-related events, driven by the data flowing out of each event, the learning experience can be more integrated with everyday life and thus more personalised.