CMI 5 Working Group Meeting Minutes – March 18th, 2016

cmi5 Working Group Meeting Minutes – March 18th, 2016

Attendees

• Bill McDonald - cmi5 working group leader
• Andy Johnson - ADL
• Art Werkenthin - RISC
• Ben Clark - Rustici Software
• Ray Lowery - Pratt & Whitney
• Bernard Bouyt - Airbus
• David Pesce - Exputo
• Christopher Thompson - Medcom Inc
• Mike Kennedy - Workday
• Henry Ryng - InXsol

Notes

Issue #378 - Explicitly allow the LMS to override the "masteryScore" as defined in the course structure

This issued is really about how Activity ID's are to be managed with cmi5. (The question about changing the AU metadata in the course structure raise the issue about the definition of Activity ID's). The group has struggled with this issue for several weeks and has agreed to the following approach:

1. Activity ID for launch line (comes from the LMS – LMS generates it)
   • LMS MUST NOT use the “Publisher ID” (the AU ID the from the course structure).
2. LMS writes "Publisher ID" to the state
3. AU Reads "Publisher ID" from the state
4. AU writes the "Publisher" ID Context in its statements

The rationale being that the LMS will manage the Activity ID generation, but the ID from the course structure will also be added to statements as a "reference".

As a result of this decision, the cmi5 specification will change as follows:

8.1 Launch Method

activityId

Description: The Activity ID of the AU being launched.

LMS Usage: The LMS MUST generate a unique actvitityId for the AU. The LMS MUST place its value in the query string. The actvitityId generated MUST NOT match the AU’s id from the course structure (See Section 13.1.4 - AU Metadata). The LMS MUST use the same generated actvitityId on all subsequent launches (for the same AU) within the same registration. The LMS SHOULD use the same generated actvitityId (for the same AU) for all registrations.

AU Usage: The AU MUST get the activityId value from the query string. The AU MUST use the activityId value in API calls that require an "activity id" when sending xAPI requests. Data type: String (URL-encoded) Value space: IRI (as defined in the cmi5 Course Structure Section 13.1.4 - AU Metadata)

9.6 Context

Sample JSON:

   "context": {
     "registration": "<registration value provided by LMS>",
     "contextActivities": {
        "category": {[
          {"id": "https://w3id.org/xapi/cmi5/context/categories/moveon"},
          {"id": "https://w3id.org/xapi/cmi5/context/categories/cmi5"}
        ]}
     },
     "extensions" {
       "https://w3id.org/xapi/cmi5/context/extensions/sessionid":"<the value of session ID provided by the LMS>",
       "https://w3id.org/xapi/cmi5/context/extensions/publisherid":"<the unaltered value of the AU’s id from the course structure>"
       "https://w3id.org/xapi/cmi5/context/extensions/masteryScore": 0.50,
       "https://w3id.org/xapi/cmi5/context/extensions/launchMode" : "Normal"
      }
   }

All Previous CMI-5 Meeting Minutes

https://github.com/AICC/CMI-5_Spec_Current/wiki

CMI-5 on GitHub:

https://github.com/AICC