CMI 5 Working Group Meeting Minutes – May 4th

cmi5 Working Group Meeting Minutes – May 4th

Attendees

• Bill McDonald (Working Group Leader)
• Andy Johnson (ADL)
• Clayton Miller (NextPort)
• Ray Lowery (Pratt & Whitney)
• Jeremy Chapman (Pratt & Whitney)
• Mark Grant (independent)
• Christopher Thompson (Medcom, Inc.)
• Dennis Hall (Learning Templates)
• Charles Touron (USARMY CAC)
• Art Werkenthin (RISC, Inc)

Notes

---

cmi5 Conformance Testing

The group continued its discussion on AU testing. It was determined that AU test's would all assume a course structure as part of the AU (test). The primary scenario would simple launch and exit. Follow on scenarios would focus on moveOn Criteria and masteryScore variations.

cmi5 AU Testing Scenarios

STEP #1 (Launch and Exit each AU in the course – Initialize and Terminate)

• cmi5_8.1_5 endpoint - Assignable Unit (AU): The AU MUST get the endpoint value from the query string and use the endpoint value as the Base Endpoint for xAPI requests.
• cmi5_8.1_7 fetch - Assignable Unit (AU): The AU MUST retrieve the fetch value from the query string.
• cmi5_8.1_9 actor - Assignable Unit (AU): The AU MUST get the actor value from the query string. The AU MUST use the actor value in API calls that require an "actor" property when sending xAPI requests.
• cmi5_8.1_11 registration - Assignable Unit (AU): The AU MUST use the registration id provided query string in API calls that require a "registration id" when sending xAPI requests.
• cmi5_8.1_13 activityId- Assignable Unit (AU): The AU MUST get the activityId value from the query string and use the activityId value in API calls that require an "activity id" when issuing cmi5 defined statements. cmi5_8.2.1_3 Assignable Unit (AU):** The AU MUST issue only one request to the _ fetch _ URL.
• cmi5_8.2.1_4 Assignable Unit (AU): The AU MUST NOT issue any type of HTTP requests other than POST to the _ fetch _ URL.
• cmi5_8.2.2_2 Assignable Unit (AU): The AU MUST place the authorization token returned from the fetch URL in the Authorization headers of all HTTP requests made to the LRS endpoint.
• cmi5_9.1_1 Assignable Unit (AU): The AU MUST assign a statement id property in UUID format for all statements it issues.
• cmi5_9.2_3 Assignable Unit (AU): The Actor object defined by the LMS must be used as the actor in all cmi5 defined statements made by the AU.
• cmi5_9.3_4 Assignable Unit (AU): The AU MUST issue a Terminated (cmi5 defined) statement as its last statement in a session.
• cmi5_9.3.2_1 Assignable Unit (AU): The AU MUST issue a Initialized (cmi5 defined) statement as its first statement in a session.
• cmi5_9.3.2_2 Assignable Unit (AU): The AU MUST NOT issue more than one Initialized (cmi5 defined) statement in a session.
• cmi5_10_1 Assignable Unit (AU): The AU MUST NOT modify or delete the LMS.LaunchData State document.
• cmi5_10_8 Assignable Unit (AU): If the returnURL is provided in "LMS.LaunchData", the AU MUST redirect the current browser window to the returnURL when the AU is terminated.
• cmi5_10_2 Assignable Unit (AU): The AU MUST NOT overwrite any values provided by the LMS in the contextTemplate.
• **cmi5_10_11 Assignable Unit (AU) : AU MUST get the "contextTemplate" value from the "LMS.LaunchData" State document.
• **cmi5_10_12 Assignable Unit (AU) : The AU MUST use the contextTemplate as a template for the "context" property in all xAPI statements it records to the LMS.
• **cmi5_10_13 Assignable Unit (AU) : The AU MUST NOT overwrite any values provided in the contextTemplate.
• cmi5_9.5.4.1_1 Assignable Unit (AU): The AU MUST include the "duration" property in "terminated" statements.
• cmi5_9.3.2_1 Assignable Unit (AU): The AU MUST issue a Initialized (cmi5 defined) statement as its first statement in a session.
• cmi5_9.3.2_2 Assignable Unit (AU): The AU MUST NOT issue more than one Initialized (cmi5 defined) statement in a session.
• cmi5_9.3.8_1 Assignable Unit (AU): The AU MUST record a (cmi5 defined) statement containing the "terminated" verb as the last statement in a session.
• cmi5_9.4_1 Assignable Unit (AU): The AU must provide an object in all (cmi5 defined) statements.
• cmi5_9.4_2 Assignable Unit (AU): For all (cmi5 defined) statements issued by the AU, the Object's "id" property must match the activityId defined in the launch URL.
• cmi5_9.5.2_3 Assignable Unit (AU): The AU must not include the success property for (cmi5 defined) statements other passed and failed.
• cmi5_9.5.3_2 Assignable Unit (AU): The AU must not include the "completion" property for (cmi5 defined) statements other completed.
• cmi5_9.6.2.1_2 Assignable Unit (AU): The LMS must include An Activity object with an "id" of "https://w3id.org/xapi/cmi5/context/categories/cmi5" in the "category" context activities for all cmi5 defined statements it issues.
• cmi5_9.7_2 Assignable Unit (AU): All statements issued by the AU MUST include a timestamp property in UTC time.
• cmi5_11_1 Assignable Unit (AU): The AU MUST call the agent profile API to retrieve the “cmi5LearnerPreferences” document.

moveOn (Single Pass)

• Step #2 – Launch AU’s with MoveON Criteria of “Completed” (Don’t Complete)
• Step #3 – Launch AU’s with MoveON Criteria of “Completed” (And Complete)
• Step #4 – Launch AU’s with MoveON Criteria of “Passed” (Don’t Passed) (Mastery Score)
• Step #5 – Launch AU’s with MoveON Criteria of “Passed” (And Pass)
• Step #6 – Launch AU’s with MoveON Criteria of “CompleteAndPassed” (Don’t Pass or Complete)
• Step #7 – Launch AU’s with MoveON Criteria of “CompleteAndPassed” (Complete)
• Step #8 – Launch AU’s with MoveON Criteria of “CompleteAndPassed” (Pass) (Mastery Score)
• Step #9 – Launch AU’s with MoveON Criteria of “CompleteOrPassed” (Don’t Pass or Complete)
• Step #10 – Launch AU’s with MoveON Criteria of “CompleteOrPassed” (Complete)

moveOn (Multiple Pass)

• Step #11 – Launch AU’s with MoveON Criteria of “CompleteOrPassed” (Restart then Pass) (Mastery Score)

moveOn (Multiple Pass – MasteryScore Modify MasteryScore - Lower)

• Step #4 – Launch AU’s with MoveON Criteria of “Passed” (Don’t Passed) (Mastery Score)
• Step #5 – Launch AU’s with MoveON Criteria of “Passed” (And Pass)
• Step #6 – Launch AU’s with MoveON Criteria of “CompleteAndPassed” (Don’t Pass or Complete)
• Step #7 – Launch AU’s with MoveON Criteria of “CompleteAndPassed” (Complete)
• Step #8 – Launch AU’s with MoveON Criteria of “CompleteAndPassed” (Pass) (Mastery Score)
• Step #9 – Launch AU’s with MoveON Criteria of “CompleteOrPassed” (Don’t Pass or Complete)
• Step #10 – Launch AU’s with MoveON Criteria of “CompleteOrPassed” (Complete)
• Step #11 – Launch AU’s with MoveON Criteria of “CompleteOrPassed” (Restart then Pass) (Mastery Score)

moveOn (Multiple Pass – MasteryScore Modify MasteryScore - Higher)

• Step #4 – Launch AU’s with MoveON Criteria of “Passed” (Don’t Passed) (Mastery Score)
• Step #5 – Launch AU’s with MoveON Criteria of “Passed” (And Pass)
• Step #6 – Launch AU’s with MoveON Criteria of “CompleteAndPassed” (Don’t Pass or Complete)
• Step #7 – Launch AU’s with MoveON Criteria of “CompleteAndPassed” (Complete)
• Step #8 – Launch AU’s with MoveON Criteria of “CompleteAndPassed” (Pass) (Mastery Score)
• Step #9 – Launch AU’s with MoveON Criteria of “CompleteOrPassed” (Don’t Pass or Complete)
• Step #10 – Launch AU’s with MoveON Criteria of “CompleteOrPassed” (Complete)
• Step #11 – Launch AU’s with MoveON Criteria of “CompleteOrPassed” (Restart then Pass) (Mastery Score)

---

Discussion for next meeting

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/