CMI 5 Working Group Meeting Minutes – August 28th, 2015

cmi5 Working Group Meeting Minutes - August 28th, 2015

Attendees

• Bill McDonald - cmi5 Working Group Leader
• Andy Johnson – ADL
• Art Werkenthin - RISC
• Ben Clark – Rustici Software
• Ray Lowery – Pratt & Whitney
• David Pesce – Exputo
• Severin Neumann – eLearning AG
• Shai Desai – Learning Plan
• Frederick Tillin –

Notes

cmi5 adoption

Both RISC and Rustici have starting working on cmi5 implementations. Feedback from both vendors will be considered in quartz.

Optional Values in JSON

The group agreed that the following language should be added to address the issue of optional JSON properties and how their values should be recorded.

4.3 Optional JSON Values.

If JSON properties are indicated as "optional", you MAY leave such properties out of the JSON structure being described. All JSON properties included with non-null values MUST be recorded in the LRS.

State API Document

The group agreed to change section “10.0 xAPI State Data Model – contextTemplate: AU usage” as follows:

AU MUST get the contextTemplate value from the "LMS.LaunchData" state document. The AU MUST NOT modify or delete the "LMS.LaunchData" state document. The AU MUST use the contextTemplate as a template for the context property in all xAPI statements it records to the LMS. While the AU may include additional values in the context object of such statements, it MUST NOT overwrite any values provided in the contextTemplate. NOTE: this will include the session ID specified by the LMS.

Clarify error conditions for section “8.2.3.2 Error Values” (Issue #239)

Art Werkenthin also reported that developers are having confusion over error code usage. Based on this issue the group agreed to change the error code descriptions as follows:

Code/Meaning

• 1 Already in Use or Expired – Token has been used before or the AU session has expired
• 2 General Security Error – All other security issues including invalid tokens
• 3 General Application Error – Application or environment failures

(Issue#237) - RFC 2396 vs RFC 3986 vs RFC 3987

The cmi spec incorrectly refers to URI when it should reference the IRI specification (RFC 3987). A pull request will be generated for next week.

cmi5 overview (README) document for the GitHub repo

Frederick Tilkin raised the issue (#230) about a month ago regarding the lack of overview documentation on cmi5 for the Github repo. Links to articles on cmi5 were provided as possible starting points for README file to be drafted for this purpose.

Frederick’s feedback was to add the following topics:

• Emphasize Scope of CMI5 (What it can do and not do)
• Explain SCORM vs CMI5 differences (and advantages – why cmi5 is better)

Course Structure/AU Sequencing

Ben Clark raised the issue that there is some ambiguity over whether the LMS is required to control sequencing (allow/prevent learner launch) of AU’s based on their moveOn criteria. There is also ambiguity over default sequencing behavior. For example is the implied order from xml use for menu display and sequencing ? What is the default order, etc. The cmi5 spec should have some language to define if it is in or out of scope (and if it is in scope – specify the requirements)

The group will discuss this issue in detail next week.

Next Meeting

Next Meeting: September 4th, 2015 – 10:30 am US Eastern Time