CMI 5 Working Group Meeting Minutes – April 28th - AICC/CMI-5_Spec_Current GitHub Wiki
cmi5 Working Group Meeting Minutes – April 28th, 2017
Attendees
- Bill McDonald - cmi5 working group leader
- Andy Johnson - ADL
- Ben Clark - Rustici Software
- Dennis Hall - Learning Templates
- Clayton Miller - NexPort Engineering
- Ray Lowery - Pratt & Whitney
- Christopher Thompson – Medcom Inc.
- Steven Warwick - Health Decisions
- David Pesce - Exputo
- Patrick Selby - LexisNexis
Notes
SCORM vs. cmi5 Comparison Document
The group agreed to the following changes:
#1 - Remove the following entries from the detailed comparison table (as redundant):
- Support for Non-traditional Learning Types
- Flexible Content Types
- Communication Interface
#2 - Update the Client Agonistic description to combine verbiage from Communication Interface
Client Agnostic
For all practical purposes, SCORM is dependent on browser delivery due to the use of JavaScript API/object for communication. cmi5 uses a RESTful web service (xAPI) that the content uses to send requests/receive responses with JSON data structures.
Since cmi5 does not rely on JavaScript, a web-browser is not required for content delivery. Because of this, content can be developed in any programming language that can support HTTP communication.
#3 - Create Distributed Content Descrption
Distributed Content
With SCORM all content is required to be located in the package and typically stored on the same domain as the LMS. With cmi5, content does not have to be in the package and can be located on any domain/local device.
The cmi5 course structure (cmi5.xml) can contain either relative or fully qualified URLs to the content launch point. Content can be hosted in central locations allowing for automated updates and simple distribution for content discovery. Content can also by dynamically created and configured at runtime if hosted.
The cmi5 course structure also provides for an “entitlementKey” which allows for content for metered access to content as a service.
Entitlement Key
The group had a lengthy discussion about how entitlementKey is used to support content as service (CaaS).
Negotiation between the LMS and the content service for keys was determined to be out of scope for cmi5.
Discussion for next week
- Complete last 3 entries - Data Access, Readability, and Portability
- Discuss approach to compliance testing
All Previous cmi5 Meeting Minutes
https://github.com/AICC/CMI-5_Spec_Current/wiki
cmi5 on GitHub: