CMI 5 Working Group Meeting Minutes – February 12th

Attendees

• Bill McDonald (Working Group Leader)
• Andy Johnson (ADL)
• Dennis Hall (Learning Templates)
• Ben Clark (Rustici Software)
• Brian Miller (Rustici Software)
• Megan Bowe (Making Better)
• Brian Duck (Duck Works, LLC.)
• Kevin Owens (University Texas, Austin)
• Simon Hsu (KeyBridge Technologies)
• Yifei Dong (KeyBridge Technologies)
• Henry Ryng (InXSOL)
• Christopher Thompson (Medcom, Inc.)
• George Vilches (JCA Solutions)
• Richard Shipmon (US Army -TRADOC)
• Jack Bowden ()

Notes

cmi5 FAQ

The group continued its discussion from December 2020 on Frequently asked Questions for the cmi5 gitHub.io site. The group approved the FAQ's from last week and revised the Why are you using Basic Auth? question as follows:

8. Why are you using Basic Auth? Basic Auth is not being used as a username/password encoding scheme in cmi5. Basic Auth (RFC 7235) was selected because it was the most widely used scheme at the time the xAPI specification was created. Basic Auth is used to provide a temporary “authorization” to the LRS (not authentication to the LRS). Authentication to the LRS is expected to be managed by the LMS or some other mechanism. With cmi5, a Basic Auth token is used in the HTTP header of xAPI requests made by the Learning Activity. Actual learner authentication is outside the scope of cmi5.

See GitHub IO site for published result: https://aicc.github.io/CMI-5_Spec_Current/about/faq.html

cmi5 Course Sequencing

The group continued the course sequencing discussion regarding the request from the US Army customers. Andy Johnson will reach out to other US Army representatives for more details to support next week's discussion on Course Sequencing.

cmi5 Test Suite

Brian Miller gave an informal status update on the cmi5 TestSuite / player project