CMI 5 Working Group Meeting Minutes – June 25th - AICC/CMI-5_Spec_Current GitHub Wiki

cmi5 Working Group Meeting Minutes – June 25th

Attendees

  • Bill McDonald (Working Group Leader)
  • Andy Johnson (ADL)
  • Florian Tolk (ADL)
  • Art Werkenthin (RISC, Inc)
  • Brian Miller (Rustici Software)
  • George Vilches (Rustici Software)
  • Henry Ryng (INXSOL)
  • Christopher Thompson (Medcom, Inc.)
  • Megan Bowe (Making Better)
  • Yifei Dong(KeyBridge Technologies)
  • Simon Hsu (KeyBridge Technologies)
  • Thomas Turrell-Croft (berrycloud)
  • Carsten König ()

Notes

  • "termination" events - The group talked about “termination” events as related to the browser and it was agreed it is a bad practice to wait for browser/application closing events, it is recommended as a best practice in the spec! A PR ( https://github.com/AICC/CMI-5_Spec_Current/pull/725 )to remove it.

  • newline characters - The group discussed the notion of newline and other characters that can take place within a “String” type. LRSs may handle these differently. While there was not a definitive consensus, the group generally agreed that they should not be included in the examples.

  • resuming a session - The group discussed what it means to “resume a session” – and in fact, you cannot resume a session. By definition, a session is bound by terminated/abandoned because there is a one-time sessionID supplied at launch. cmi5 does NOT address the notion of attempts – this is considered instructional and not functional. As long as there is no “terminated”, the session is considered active. Use of state document can be used to effectively suspend/resume, but doesn’t change what a session is.

  • resuming a session - The notion of abandoned was discussed. There is no “terminated” that is retroactively created. It isn’t something necessarily abnormal that caused it, it just originates FROM THE LMS. In 9.3.7 we want to get rid of the other of “other AUs” when really it is “any AU”.

  • simultaneous AU sessions - Per comment in Issue 721 (June 25, 2021) - The group will revisit the Section 9.3.7 text as well as the notion of not allowing two simultaneous sessions for the same AU or same registration (however, it seems you could have simultaneous sessions for the same learner). Multiple "open" sessions on the same AU or registration would lead to potential conflicting Statements or moveOn criteria (and cheating). The group discussed the possibilities of having two active sessions. The three key questions are:

    • Can the same learner have two sessions in the same AU? (This is an easy “no” because of registration conflicts and possibilities of repeating Statements)
    • Can the same learner have two sessions in the same Course? (This is also an easy no because of registration conflicts and possibilities of stacking “moveOn”)
    • Can the same learner have two sessions in the same LMS? (We believe this is an implementation detail. cmi5 doesn’t forbid it. The two sessions for the learner would have to be different registrations.

  • registration- Overall, a registration is the unique construct that determines what else can and cannot be launched.

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/

cmi5 Working Group Wiki

⚠️ **GitHub.com Fallback** ⚠️