CMI 5 Working Group Meeting Minutes – April 12th

cmi5 Working Group Meeting Minutes – April 12th

Attendees

• Bill McDonald (Working Group Leader)
• Andy Johnson (ADL)
• Florian Tolk (ADL)
• Mark Grant (Independent)
• Art Werkenthin (RISC, inc)

Notes

---

cmi5 client Library

Art Werkenthin briefed the group on updates to the cmi5 client library, they are as follows:

• Move FinishAU() to from wrapper to the cmi5Controller
• Cmi5AllowedStatement() – make context an extensions parameters optional – default to LMS.Launch data

---

cmi5 spec errata.

The group agreed to more clearly indicate cmi5 defined statements in section 10.0 xAPI State Data Model for launchMode - AU Usage:

The AU MUST conform to the following based on the value of launchMode

• Normal The AU MUST record "Initialized" and "Terminated" verb statements. The AU MUST record other cmi5 defined statements per the requirements defined in section 9.3 – Verbs.

• Browse The AU MUST record "Initialized" and "Terminated" verb statements. The AU MUST NOT record other cmi5 defined statements.

• Review The AU MUST record "Initialized" and "Terminated" verb statements. The AU MUST NOT record other cmi5 defined statements.

---

cmi5 Best Practices

The group approved language for the following best practices:

Best Practice #15 – LMS should use the Session ID and authentication token to validate actor

When the LMS receives a Statement, it should verify that the Actor in the statement matches the actor provided on the launch URL and that the authentication token provided was the same one issued for that specific launch session. If the Session ID, authentication token, actor in statement, and actor do not match, then the LMS/LRS should reject the Statement with a HTTP 403 (Forbidden) Error.

Best Practice #16 – cmi5 AU’s should use a derived activity ID for “cmi.interaction” statements

When the AU issues statements with an activity type of “cmi.interaction” it should use an activity ID derived from the AU’s activity ID by appending the following convention:

/test/{TestID}/question/{QuestionID}

Where :

• {TestID} is a vendor defined identifier for the test embedded in AU.
• {QuestionID} is a vendor defined identifier for the test question.

Example: https://example.com/au/xyz123/test/997980ef-2089-4685-97ee-6949541a27e5/question/3f45e67c-f070-4ded-8fd8-82c4069e8526

---

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/