Presentation and demo at EPUB Accessibility and EDUPUB Alliance Summit in February 25, 2016.

1. EDUPUB Implementation Demo Showcase
- Reference SW using Readium JS -
Principal researcher, KERIS
Yong-Sang CHO, Ph.D
zzosang@keris.or.kr
FB: /zzosang Twitter: @zzosang
EPUB Accessibility and EDUPUB Alliance Summit
February 25, 2016

2. DIGITAL TEXTBOOK IN KOREA
Case Study:

3. Current Digital Textbook is
pursuing open platform based on with EPUB3
<source: MOE of Korea and KERIS, 2011>

4. beyond content itself; multiscreen service and analytics
 BYOD and Learning Analytics
Current Digital Textbook will be
<source: MOE of Korea and KERIS, 2011>

5. Is it possible to make dreamed textbook?

6. We have expected there is a possible way …
That is the EDUPUB

7. However, we need to prove the concept for careful
stakeholders prior to adopt EDUPUB.
This is the reason why we choose READIUM
as a reference software!

8. DESIGN
Readium JS with IMS Caliper sensor API and LTI integration
It is too early to show you my team’s trial 

9. Pseudo Platform Readium-JS
readium-shared-js
readium-js-extension
readium-js-viewer
readium-js
(core)
caliper event
generator
lti-launcher
ims-caliper-sensor
(js version)
Transmission of Data
data sending
(JSON)
manage contents
manage users
session logging
content launching
oa manager
Mongo DB
(EVENT/OA)
Log(Session)DB
Resource DB
User DB
Annotation Viewer
Endpoint
(LA Platform)
Quick review design for EDUPUB

10. Integration Annotation event with OAinEPUB
• Using ‘extension’ in ‘generated’ property
Quick review design for EDUPUB

11. DEMO
Readium JS with IMS Caliper sensor API and LTI integration
Again, it is too early to show you my team’s trial 

12. 1. Session Event – Log in (Pseudo Platform)
- JSON DataCapture a session event
1

13. 2. Navigation Event – Page navigation - JSON Data
Capture navigation event
1

14. 3. Annotation Event – Highlight (OAinEPUB)
Capture annotation event
1
2

15. (FYI) Capture image for annotation event in JSON format

16. 4. Annotation Event – Bookmark (OAinEPUB)
2
3 1
Capture annotation event

17. (FYI) Capture image for annotation event in JSON format

18. 5. Session Event – Log out (Pseudo Platform) - JSON Data
1
Capture a session event

19. 6. Dashboard via real time analytics for engagement

20. NEXT STEP?
We know there is more works than the achievements.

21. Well …
Step 1?
• Evaluate codes that we developed with inside and outside project team
• Ask pull request to Readium (GitHub)
- Caliper sensor API and OAinEPUB first
Step 2?
• Revise codes for LTI integration
following IMS Caliper with LTI integration guideline when it confirms
Step 3?
• Support to reflect EPUB for Education on current Readium project
• Develop QTI integration
And more?

22. GUIDELINE
FOR DATA INTEROPERABILITY
What I am doing in ISO/IEC JTC1 SC36 WG8 (LAI)

23. Subject
Triple Bindings
Predicate Object
With contexts information
Learning Applications
Generated (objects)
Outcomes Courseware
GroupTimestamp
Data Structure of learning activities

24. Event Store
Learning
Record
StoreIMS Caliper
Sensor APIs
xAPIs
Data Mapping
& Matching
Process
_______________
P1. Structural &
Syntactic
Mapping
P2. Semantic
Matching
Learning
Environments (a) on
S/W apps, platform and
web
Repository
Metadata
Repository
Metadata
……
Learning
Environments (b) on
S/W apps, platform and
web
……
IMS Caliper
Metric Profiles
xAPIs
Recipes
Data Flows and exchange assumed

25. <IMS Caliper properties of assignable>
<xAPI Statement properties>
P1. Example for structural/syntactic mapping rules

26. <IMS Caliper> <xAPI + Recipes>
Class Class
http://www.imsglobal.org/caliper/ http://adlnet.gov/expapi/Entities …
Concept tree
Property/relation Property/relation
Concept detail tree
{actor, action, event, target, generated, etc…} {actor, verb, object, context, etc…}
Instance Instance
{
“action”: “completed”
}
{
“verb”: “finished”
}
Instance Table
- ontology mapping
rule
Structural/
Syntactic
Mapping
Semantic
Mapping
P2 (a). Example for ontological mapping rules
(under assumption xAPI’s recipes are looked as single form)

27. Semantic
Filter/
Mapper
IMS Caliper
Sensor APIs
xAPI – recipe (a)
xAPI – recipe (b)
xAPI – recipe (c)
…
Ontology Repo
(for common sense)
P2 (b). Example for ontological mapping rules
(under assumption xAPI’s recipes are looked differently)

28. Learning
Environments
…
Data
Collection APIs
……
Collected
Data Stores
…………………
Data
Mapping & Matching
…
(4) Notify learning
activity occurred
(5) Capture & Store data
temporarily at end-
point of APIs
(6) Authorization for
transmission
(8) Test conformance &
store received data (9) Request transform of data for
target repository
(10) Query metadata for repositories’
features, i.e. data model and URI
(11) Transmit source data
(7) Transmit captured
data
(12) Structural/Syntactic
mapping
(13) Semantic matching
(14) Transmit transformed data
(1) Identify entities and properties for data model of APIs (2) Structural/Syntactic
mapping profiling
(3) Semantic matching
profiling
(15) Test received data and exception
for non-conformant data
Sequence for data mapping and transformation

29. Questions?