CMI 5 Working Group Meeting Minutes – September 9th, 2016

cmi5 Working Group Meeting Minutes – September 9th, 2016

Attendees

• Bill McDonald - cmi5 working group leader
• Ben Clark - Rustici
• Brian Miller - Rustici
• Andy Johnson - ADL
• Art Werkenthin - RISC
• Henry Ryng - inXsol
• Christopher Thompson - Medcom Inc
• Billy White - Thrivist
• David Pesce - Exputo
• Dennis Hall - eLearning Templates
• Amanda Bond - COAR
• Charles Touron - ATSC

Notes

cmi5 conformance Testing

The group discussed conformance testing for cmi5.

Since cmi5 is xAPI based, the group discussed coordination with DISC (datainteroperability.org) - the group tasked with xAPI compliance testing. Products will need to be compliant with xAPI in order to be cmi5 compliant. However, cmi5 compliance will have additional requirements on top of xAPI and that will additional compliance testing.

cmi5 examples to assist in testing

Currently no compliance/conformance testing software exists for cmi5, but there are some reference implementations that may be helpful for developers to get started. The following example called the "AU simulator" is a reference implementation of cmi5 compliant content that is useful for testing cmi5 LMS systems:

• https://github.com/cawerkenthin/cmi5-AU-Simulator

The group will continue to compile this and other examples to help grow the cmi5 community.

cmi5 conformance Testing Document

The group agreed to start outlining conformance testing document to assist cmi5 developers and provide a basis for test suite software requirements. The following is outline of what was discussed:

---

LMS Testing

1. LMS must be XAPI/LRS Conformant – DISC cert testing
2. LMS must able to import a cmi5 course structure
   • The LMS MUST support course structures containing more than 1000 AUs
   • Reject no-conformant course structures
3. LMS conform to cmi5 launch (Launch Test)
   • Launch Mechanism
     • All launch params (LRS end-point, actor, registration, activityID, fetchURL)
     • Implement Fetch URL
4. Reject multiple calls to Fetch URL (LMS receives message = 1st use)
   • Write to State API
   • Write Launched Statement
5. LMS conform to session management
   • LMS must not allow AU to void statements
   • LMS must either reject or void statements that conflict with the cmi5 "Statement API"
   • All JSON properties included with non-null values MUST be recorded in the LRS.
6. LMS must conform to course structure rules
   • Must write satisfied statement for Block and Course completion
   • “MoveOn” ? – Verify that Satisfy Statements are written for given Move Criteria
   • AnyWIndow / OwnWindow

Content Testing

1. AU conform to cmi5 launch (Launch Test)
   • Parse Launch Parameters
   • Call Fetch URL and get Auth Token
     • If HTTP Error occurs – retry
     • If error out – then close
   • Read from State API
   • Read Agent Profile
   • Write Initialized Statement
     • Use Context Template (retrieved from StateAPI)
   • Write optional statements (conforming manner)
     • cmi5 Defined
     • cmi5 Allowed
     • Use Context Template (retrieved from StateAPI)
   • Write Terminate Statement
     • Use Context Template (retrieved from StateAPI)

Test Suite Design Considerations

• LMS/LRS – to for testing content/authoring
• Content – matching examples
• Content – Course structure – relative and hosted content URLS
• Content – cmi5 content simulator
  • Random Timing
  • Full set of statements/sessions

---

All Previous CMI-5 Meeting Minutes

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

CMI-5 on GitHub:

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