The document discusses the principles of xAPI and IMS Caliper, two data capturing technologies used in learning analytics, focusing on their interoperability and design implications. It outlines how xAPI allows for the secure delivery and storage of experiential learning data and highlights the goals of IMS Caliper in standardizing learning interaction data collection. Additionally, the document raises questions and considerations for improving the interoperability between xAPI and IMS Caliper data models.

1. Quick review for xAPI and IMS Caliper
- Principle of both data capturing technologies -
Korea Education & Research Information Service
Yong-Sang Cho, Ph.D
zzosang@keris.or.kr
FB: /zzosang Twitter: @zzosang

2. xAPI
Transcript/learning data
can be delivered to LMSs, LRSs
or reporting tools
Experience data
LMS: Learning Management System
LRS: Learning Record Store

3. IMS
Caliper
<Source: New Architect for Learning (Rob Abel, 2014)
http://www.slideshare.net/JEPAslide/day3-edupub-tokyoims?qid=76ce5d4a-1ccf-468f-a428-c652584c395a&v=default&b=&from_search=4>

4. Principle of both specifications
Subject
Triple Bindings
Predicate
Object
With contexts information
Learning Applications
Generated (objects)
Outcomes
Courseware
Group
Timestamp

5. “The Experience API is a service that allows for statements of experience to be delivered
to and stored securely in a Learning Record Store (LRS). These statements of experience are
typically learning experiences, but the API can address statements of any kind of experience.
The Experience API is dependent on Activity Providers to create and track these
learning experiences“
< from the specification of xAPI,
https://github.com/adlnet/xAPI-Spec/blob/master/xAPI.md#roleofxapi >

6. Implications of xAPI are
(from the perspective of learning analytics interoperability)
• xAPI is an well designed abstract level architecture for learning
experience (or activity) data
• Predicates (a.k.a “verb” in xAPI) may be profiled in application domain,
because the xAPI does not specify any particular Verbs
• Object is well designed for SCORM object and interaction based on
interactions of cmi data model
• But, to use Object in more diverse learning situations this needs to be
profiled for specific purposes with controlled vocabulary of object types
• xAPI data model is well relevant to JSON binding like IMS Caliper
-> It seems not difficult to make interoperable data between specs

7. “The purpose of the IMS Caliper project is to define a standard for enabling the collection
of rich contextual data about learning interactions and a Sensor API™ for capturing and
reporting this data. This work will enable learning environments to capture data from learning
interactions and share it with other learning environments and consumers of learning analytics. “
< from IMS Caliper Implementation Guide,
http://www.imsglobal.org/caliper/caliperv1p0/ims-caliper-analytics-implementation-guide#1 >

8. Implications of IMS Caliper are
(from the perspective of learning analytics interoperability)
• IMS Caliper is started with minimum metric profile for learning activity
like a lean-startup
-> It may be extended to be wider due to feed back from adopters
• It may be met with intersection point between too much detail
(or complex) and simple (or ambiguous)
• Sensor APIs per learning activity need to be well combined with existing
learning environments to generate value of properties, such as ‘generated
’
or ‘target’
• Caliper data model is well relevant to JSON binding like xAPI
-> It seems not difficult to make interoperable data between specs

9. Event Store
Learning
Record
Store
IMS Caliper
Sensor APIs
xAPIs
Mapped to
JSON data
Instance idea for interoperable data between IMS Caliper and xAPI

10. • How to mapped between xAPI and IMS Caliper data?
i.e. see next slide
• Is there any principle (or guideline) for design (or profiling) of learning data
in terms of learning analytics interoperability?
i.e. to use xAPI for specific purpose or adopt IMS Caliper profiles
• How to make ISO/IEC 20748 Learning analytics interoperability to be
practical standards (TRs) for diverse stakeholders?
- Part 1: Reference model
- Part 2: System requirements
- …
- Part x: Principle of data design enabling learning analytics interoperability
- Part y: Guideline for profiling learning activity (experience) data
Question list to Study Group of SC36/WG8:

11. Instance example for mapping between IMS Caliper and xAPI
<IMS Caliper properties of assignable>
<xAPI Statement properties>

12. More Questions?
Korea Education & Research Information Service
Yong-Sang CHO, Ph.D
zzosang@gmail.com
FB: /zzosang Twitter: @zzosang