CMI 5 Working Group Meeting Minutes – November 22nd

cmi5 Working Group Meeting Minutes – November 22nd

Attendees

• Bill McDonald (Working Group Leader)
• Andy Johnson (ADL)
• Florian Tolk (ADL)
• Mark Grant (Independent)
• Art Werkenthin (RISC, inc)
• Dennis Hall (Learning Templates)

(Complete attendee list pending...)

Notes

cmi5 Client Library Usage/best practices (for github.io site)

The group began work on creating pages for the demonstrating how to use the cmi5 client library following best practices. There are expected to be a total of 9 content use scenarios (based on previous meeting discussions). The first scenario (simple launch and exit) is as follows:

How to use. (Hello world)

1. Include ADL min library Reference
2. Include cmi5Controller.js & cmi5Wrapper.js library reference
3. Parse parameters passed on the command line and set properties of the cmi5 controller: a) Endpoint b) fetch URL c) registration d) activity id e) actor
4. Call the cmi5Controller.startUp() method. Two call back functions are passed:
   • cmi5Ready.. This function is called once the controller has fetched the authorization token, read the State document and the agent Profile.
   • startUpError.. This function is called if the startUp() method detects an error.
5. Create the “cmi5Ready” function.
   • Set Object Identifiers for your AU - cmi5Controller.setObjectProperties()
   • Issue the initialized Statement
6. Add reference to FinishAU() in your UI for learner exit event.
   • Best Practice is to use the same window (and use returnURL to redirect back to LMS user interface)

cmi5 Client Library Changes

The group agreed to update the cmi5 Client Library to reference latest "bundled" version of xapiwrapper.min.js (which has all dependent libraries combined) see links below:

• https://github.com/adlnet/xAPIWrapper/tree/master/dist
• https://github.com/adlnet/xAPIWrapper/blob/master/dist/xapiwrapper.min.js

cmi5 Client Library Repository:

• https://github.com/adlnet/cmi5-Client-Library

cmi5 github.io website

The group agreed to reorganize the github.io website navigation menu to have the following hierarchical structure:

Top Level Menu

• Home
• Why cmi5?
  • SCORM vs cmi5
  • TinCan Packages vs. cmi5
• For Developers
  • Best Practices
  • JSON Examples
  • Common Mistakes
  • Library Usage/Examples
• Adoption
• Github