CMI 5 Working Group Meeting Minutes – November 1st - AICC/CMI-5_Spec_Current GitHub Wiki
cmi5 Working Group Meeting Minutes – November 1st
Attendees
- Bill McDonald (Working Group Leader)
- Andy Johnson (ADL)
- Florian Tolk (ADL)
- Mark Grant (Independent)
- David Pesce (Exputo)
- Henry Ryng (inXsol)
- Art Werkenthin (RISC, inc)
- Patrick Selby (Lexis Nexus)
Notes
The group continued to edit the cmi5 vs "TinCan Package" document.
The group added the following sections.
Authentication management The cmi5 specification provides for a “fetch URL” service that supplies an authentication token to the AU. The fetch URL is “one time” use URL that the AU uses to retrieve the authentication token. Additional calls to the fetch URL are rejected. This method reduces the risk of token reuse by unauthorized actors.
Allows launching and tracking of multiple AUs in a course The cmi5 specification requires the LMS to support courses with 1 to (at least) 1000 AU’s. This allows for a large, hierarchical structure of course elements (AUs) that can be reused and recombined in other structures in an interoperable manner. The TinCan package only allows for one launchable activity.
Is conformant to the xAPI Specification The TinCan package, by adding additional parameters in calls to the xAPI Statement API, will fail LRS Conformance unless a specific “allow list” exception is made. In addition, the LRS action expected based on these parameters is not thoroughly defined. This creates many interoperability issues. cmi5 has no features (or requirements) that conflict with the xAPI specification. LRS’s that support cmi5 can pass the xAPI conformance test without such conflicts.
The document will be uploaded to the aicc.github.io site for final review and formatting.
http://aicc.github.io/CMI-5_Spec_Current/tincan/
The next meeting will the group will return to working on the cmi5 narrative presentation.