CMI 5 Working Group Meeting Minutes – June 16th - AICC/CMI-5_Spec_Current GitHub Wiki
cmi5 Working Group Meeting Minutes – June 16th, 2017
Attendees
- Bill McDonald (Working Group Leader)
- Andy Johnson (ADL)
- Art Werkenthin (RISC, Inc)
- Brian Miller (Rustici Software)
- Dennis Hall (Learning Templates)
- Henry Ryng (InXSOL)
- Ray Lowery (Pratt & Whitney)
- Clayton Miller (NextPort Engineering)
- David Pesce (Exputo)
- Christopher Thompson (Medcom, Inc.)
Notes
The group discussed the following issues:
Issue #546 - What is a "course registration"?
Last week's proposal to resolve this issue was further refined to clarify registration. The following clarifying language will be added to the specification:
3.0 Definitions
- Registration - An enrollment instance of a learner in a course. (Registration ID uniquely identifies this)
- Session – A period of time marked by the launch of an AU until its termination (or abandonment).
- Activity – In this spec it is representative of an AU or the Object of a statement with objectType of “Activity”. Thus the granularity can be anything from a single AU course down to a specific interaction.
Issue #550 - Should no-fail-after-pass be per registration?
The changes proposed from last week were discussed and it was determined that the role of timestamps in determining the sequence see section 9.7 of statements needed to be emphasized so the following language was added:
For all requirements listed below including language involving order, the order is determined by the value of the timestamp property.
The rest of the proposed wording was accepted with out further changes:
AU Verb Ordering Rules within an AU session are as follows:
- Verbs MUST NOT be duplicated (in cmi5 defined statements).
- More than one of the set of {"Passed","Failed"} verbs MUST NOT be used (in cmi5 defined statements).
- The "Initialized" verb MUST be the first statement (cmi5 allowed or defined).
- The "Terminated" verb MUST be the last statement (cmi5 allowed or defined).
AU Verb Ordering Rules within a Registration (per AU) are as follows:
- Only one "Completed" cmi5 defined statement is allowed per registration.
- Only one "Passed" cmi5 defined statement is allowed per registration.
- A "Failed" statement must not follow a "Passed" statement (in cmi5 defined statements) per registration.
Issue #552 - May an LMS change moveOn for a person taking it "during" a registration?
After much discussion it was determined that the specification does not address this scenario, but probably should. Since this would result in a functional change, the group decided to add this issue to the list for the next major release of cmi5.
Issue #553 - returnURL vs. returnUrl
The JSON Samples on the cmi5 website were found to have errors regarding the capitalization of the "returnURL" property in the LMS.LaunchData state document. It was improperly shown as "returnUrl". All examples will be corrected.
Discussion for next week
- Develop cmi5 Conformance Testing Requirements
All Previous cmi5 Meeting Minutes
https://github.com/AICC/CMI-5_Spec_Current/wiki
cmi5 on GitHub: