CMI 5 Working Group Meeting Minutes – May 6th, 2016 - AICC/CMI-5_Spec_Current GitHub Wiki
cmi5 Working Group Meeting Minutes – May 6th, 2016
Attendees
- Bill McDonald - cmi5 working group leader
- David Delgado - Incaem
- Andy Johnson - ADL
- Art Werkenthin - RISC
- Dennis Hall - eLearning Templates
- Henry Ryng - inXsol
- David Pesce - Exputo
- Mike Kennedy - Workday
- Patrick Selby - LexisNexis
- Giovanni Sorrentino - E-CO e-Learning Studio
Notes
cmi5 Release Announcement - Austin, TX – June 8, 2016.
Currently, the cmi5 working group plans to make the formal announcement of the cmi5 "quartz" release at xAPI Camp (Colocated with FocusOn Learning) Austin, TX – June 8, 2016.
The host of xAPI camp has tentatively agreed to allow cmi5 working group members to attended gratis for the announcement presentation.
Issue #424 - Explicitly allow the LMS to override the masteryScore, LaunchParameters, and moveOn
The Group agreed to following changes to resolve this issue:
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 change (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 change (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 change (e.g. based on content vendor options that may be used by the LMS admin users.)
Issue #425 - AU May refuse to issue passed or completed when course structure is changed
The Group agreed to following changes to resolve this issue:
10.0 xAPI State Data Model
AU Usage:
If the AU issues "Passed" or "Failed" statements they MUST be based on the "masteryScore" provided. (See Sections 9.3.6 and 9.3.7).
Issue #447 - Launch URL should be recorded in Launched statement
The group agreed that the LMS should record the URL used to launch an AU in the launched statement. The sections will be changed as follows:
9.6.3 Extensions
9.6.3.4 launchURL
Description: Indicates the URL that was used to launch the AU by the LMS
LMS Usage: LMS Must write the URL used launch the AU in context Extensions of the Launched Statement.
AU Usage: Not Applicable
AU Obligation: None
LMS Obligation: Required
Data type: string
Value space: URL
Sample value: "xxx.com?name=value...."
All Previous CMI-5 Meeting Minutes
https://github.com/AICC/CMI-5_Spec_Current/wiki
CMI-5 on GitHub: