CMI 5 Working Group Meeting Minutes – June 9th

cmi5 Working Group Meeting Minutes – June 9th, 2017

Attendees

• Bill McDonald (Working Group Leader)
• Andy Johnson (ADL)
• Dennis Hall (Learning Templates)
• Henry Ryng (InXSOL)
• Ray Lowery (Pratt & Whitney)
• Christopher Thompson (Medcom, Inc.)

Notes

---

The group discussed the following issues:

Issue #546 - What is a "course registration"?

The term "course registration" is referred to multiple times in the spec but not clearly defined. Upon searching the specification the following reference was found.

10.0 xAPI State Data Model

registration: Registration id representing the LMS learner enrollment in the course. This MUST match Registration ID used by the LMS at AU launch time.

This was not considered sufficient and other items were found to need clarification. As a result of this discussion, the group proposed the addition of the following clarifying definitions to the spec:

3.0 Definitions

• Registration - LMS learner enrollment in the course. (Registration ID uniquely identifies this)
• Session – A period of time marked by the launch of an AU until its termination.
• 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 #549 - Are multiple overlapping launched sessions in one registration allowed?

The short answer to this question is "No". If the same AU is launched (with the same registration) before its previous launch session is closed, the LMS must issue an Abandoned statement. See specification reference below:

9.3.6 Abandoned - LMS Obligations

In the absence of a "Terminated" statement, the LMS MUST make the determination if an AU abnormally terminated a session by monitoring new statement or state API requests made for the same learner/course registration for a different AU. The LMS MUST record an "Abandoned" statement on behalf of the AU indicating an abnormal session termination. After recording an "Abandoned" statement, the LMS MUST NOT allow any additional statements to be recorded for that session.

This issue was closed.

Issue #550 - Should no-fail-after-pass be per registration?

The language in section 9.3 Verbs is unclear confusing as it mixes "per session" and "per registration" (see excerpt below). Some items are specifically called out as "per registration".

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).
• 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).
• The "Initialized" verb MUST be the first statement (cmi5 allowed or defined).
• The "Terminated" verb MUST be the last statement (cmi5 allowed or defined).

The issue calls out "Failed" statement bullet item (above) as needing clarification. The team agreed with Brian Miller's response that "per registration" is correct.

• A "Failed" statement must not follow a "Passed" statement (in cmi5 defined statements per registration.

The group proposed the following language to clarify Verb ordering rules:

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.

---

---

Discussion for next week

• Discuss the addition of definitions Registration, Session, and Activity
• Develop cmi5 Conformance Testing Requirements

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/