-
Notifications
You must be signed in to change notification settings - Fork 91
CMI 5 Working Group Meeting Minutes – May 14th
cmi5 Working Group Meeting Minutes – May 14th
Attendees
- Bill McDonald (Working Group Leader)
- Andy Johnson (ADL)
- Art Werkenthin (RISC, Inc)
- Brian Miller (Rustici Software)
- George Vilches (Rustici Software)
- Henry Ryng (INXSOL)
- Christopher Thompson (Medcom, Inc.)
- Megan Bowe (Making Better)
- Simon Hsu (KeyBridge Technologies)
- Russ Engoran ()
- Carsten König ()
- Thomas Turrell-Croft (berrycloud)
Notes
cmi5 spec clarification discussion
The group discussed the following spec clarifications, pull requests are pending next meeting:
- change agent definition to the following: "agent: Agent representing the enrolled LMS learner"
- A course MUST be packaged with course structure data that conform to all requirements listed in Section 13 and Section 14.
- Drop/modify existing Pull Request -
- Remove 13.2 (change all 13.2 references to 14.0
- Replace text in 14.0 with the text proposed by Andy Johnson
Conceptually, a course package is a collection of all of the components (AUs) of the course. While previous standards often equated this with the gathering of all resources into a single archive (often a .ZIP file), cmi5 does not have this restriction; all files can be “packaged”, even by reference.
Technically, a course package is an XML file format with a course structure. It can be standalone or contained in a ZIP file. A course package, when located in a ZIP file, MUST be named “cmi5.xml”. The course package MUST conform to the following XSD:
- https://w3id.org/xapi/profiles/cmi5/v1/CourseStructure.xsd.
- Available locally in v1/CourseStructure.xsd
An LMS MUST provide functionality such that a targeted course package is processed, resulting in a Course Structure import (See Section 13). An LMS MUST support Course Packages in at least these three file formats:
- Standalone XML file
- 32-bit Zip Format
- 64-bit Zip Format An LMS MAY support alternate forms of course packages.
cmi5 spec issues
The project CATAPULT team has found issues in the cmi5 specification for the group to resolve.
The group reviewed and approved the following pull requests:
- https://github.com/AICC/CMI-5_Spec_Current/pull/684
- https://github.com/AICC/CMI-5_Spec_Current/pull/683
- https://github.com/AICC/CMI-5_Spec_Current/pull/682
- https://github.com/AICC/CMI-5_Spec_Current/pull/681
- https://github.com/AICC/CMI-5_Spec_Current/pull/680
- https://github.com/AICC/CMI-5_Spec_Current/pull/679
- https://github.com/AICC/CMI-5_Spec_Current/pull/678
- https://github.com/AICC/CMI-5_Spec_Current/pull/677
- https://github.com/AICC/CMI-5_Spec_Current/pull/676
- https://github.com/AICC/CMI-5_Spec_Current/pull/675
- https://github.com/AICC/CMI-5_Spec_Current/pull/674
- https://github.com/AICC/CMI-5_Spec_Current/pull/673
- https://github.com/AICC/CMI-5_Spec_Current/pull/672
All Previous cmi5 Meeting Minutes
https://github.com/AICC/CMI-5_Spec_Current/wiki
cmi5 on GitHub:
http://aicc.github.io/CMI-5_Spec_Current/