CMI 5 Working Group Meeting Minutes – May 20th, 2016 - AICC/CMI-5_Spec_Current GitHub Wiki
cmi5 Working Group Meeting Minutes – May 20th, 2016
Attendees
- Bill McDonald - cmi5 working group leader
- Andy Johnson - ADL
- Ben Clark - Rustici Software
- Brian Miller - Rustici Software
- Art Werkenthin - RISC
- David Merryweather - MacMillan
- David Pesce - Exputo
- Dennis Hall - eLearning Templates
- Henry Ryng - inXsol
- Giovanni Sorrentino - E-CO e-Learning Studio
Notes
Issue #449 - Can Waived contain a Score?
Per May 20th Meeting will merge pull request #467 and add the following:
9.5.4 Duration
The duration property is an ISO 8601 formatted time value required in certain statements as defined in this section. Other cmi defined statements MAY include the duration property.
To fully resolve this issue
Issue #424 - Explicitly allow the LMS to override the masteryScore, LaunchParameters, and moveOn
Per May 20th Meeting, Will add the following to pull request #470 to resolve outstanding issues raised:
10.0 xAPI State Data Model
masteryScore
LMS Usage:
If a masteryScore is present in the course structure the LMS MUST provide a masteryScore in the State API document. The masteryScore value written in the State API Document MAY be different than the one in the course structure (e.g. based on administrative rules defined by the LMS).
moveOn
LMS Usage:
The LMS must provide a moveOn value in the state API document. The moveOn value written in the State API Document MAY be different than the one in the course structure (e.g. based on administrative rules defined by the LMS)
launchParameters
LMS Usage: The LMS MUST provide a launchParameters value in the state API document. The launchParameters value written in the State API Document MAY be different than the one in the course structure (e.g. based on administrative rules defined by the LMS).
9.6.3.2 masteryScore
Description: "masteryScore" as provided in the LMS Launch Data for AU plus registration used to determine the pass/fail result based on score.
Issue #447 - Launch URL should be recorded in Launched statement
Move the previously proposed language to "description":
9.6.3.4 launchURL
Description
A fully qualified URL equivalent to the one that the LMS used to launch the AU without the name/value pairs included as defined in section 8.1.
Issue #451 - Redundant requirements?
The group did not have sufficient time to come to consensus on this issue and will discuss it further. The following represents proposed language with the understanding that the reporting requirements for the LMS (section 4.2) needs more discussion.
4.1 Assignable Unit (AU)
See Section 7 – AU Requirements.
An Assignable Unit MUST conform to all requirements as specified in the xAPI specification (see References).
An Assignable Unit MUST NOT implement any features or functionality (optional or mandatory) described in this specification in a non-conforming manner.
4.2 Learning Management Systems (LMS)
The LMS MUST conform to all LRS requirements as specified in the xAPI specification (see References).
The LMS MUST provide the ability to retrieve
and showall statements (including attachments and extensions) to a user (with the understanding of scaling permissions/authorization).
The LMS MUST decode the attachment and make it available as a file with the original MIME type.
See Section 6 – LMS Requirements.
All Previous CMI-5 Meeting Minutes
https://github.com/AICC/CMI-5_Spec_Current/wiki
CMI-5 on GitHub: