CMI 5 Working Group Meeting Minutes – May 5th - AICC/CMI-5_Spec_Current GitHub Wiki
cmi5 Working Group Meeting Minutes – May 5th, 2017
Attendees
- Bill McDonald - cmi5 working group leader
- Andy Johnson - ADL
- Bernard Bouyt - Airbus
- Ben Clark - Rustici Software
- Brian Miller - Rustici Software
- Dennis Hall - Learning Templates
- Clayton Miller - NexPort Engineering
- Charles Touron - USARMY CAC
- Christopher Thompson – Medcom Inc.
- David Pesce - Exputo
- Giovanni Sorrentino – E-CO e-Learning Studio
- Henry Ryng - InXSOL
- Art Werkenthin - RISC Technology
- Kevin Schippler - IBM
Notes
SCORM vs. cmi5 Comparison Document
The group agreed to the following changes:
#1 - Modify Data Access and Data Portability
Data Access No Yes In SCORM, there is no standard bulk data access exposed. cmi5 uses xAPI which is designed to provide bulk access to learner data with simple filtering. Data Access
In SCORM, the only specification protocol for returning data was available at Run-Time for the current user within current SCO only. Access to data requires access to the Database (which is outside the scope of SCORM). cmi5 uses xAPI which has bulk data retrieval capabilities (using GET Requests) built-in to allow return of data. LRSs cannot be write-only. All requests for data subject to security policies.
Data Portability No Yes SCORM does not allow for standardized system integration. cmi5 uses xAPI which provides a standard journaling-based data format well suited for transport. Data Portability
SCORM does not allow for standardized system integration. cmi5 uses xAPI which provides a standard journaling-based data format well suited for transport.
SCORM has a standard model but does not have a standardized data format for export/retrieval. cmi5 is xAPI based and uses a standardized JSON / document structure. cmi5 adds context requirements to xAPI more easily group statements based on learner sessions.
#2 - Remove Data Readability (as it is redundant)
Data Readability No Yes With SCORM, the structure of data is not defined so the data format varies from system to system. cmi5 is xAPI based with a standardized JSON / document structure.
Discussion for next week
- Review xAPI Compliance Testing Team's methodology
- Discuss approach to cmi5 compliance testing
All Previous cmi5 Meeting Minutes
https://github.com/AICC/CMI-5_Spec_Current/wiki
cmi5 on GitHub: