CMI 5 Working Group Meeting Minutes – Sept 30th, 2022 - AICC/CMI-5_Spec_Current GitHub Wiki

cmi5 Working Group Meeting Minutes – Sept 30th, 2022

Attendee List

  • Bill McDonald (Working Group Leader)
  • Andy Johnson (ADL)
  • Florian Tolk (ADL)
  • Christopher Thompson (Medcom, Inc.)
  • Yifei Dong (Keybridge Technologies)
  • Brian Miller (Rustici Software)
  • George Vilches ()
  • Henry Ryng (InXSOL)
  • Vineet Mahesh (InXSOL)
  • Tyler Mulligan (SANS)
  • Art Werkenthin (RISC, Inc)

Notes

The group continued its discussion of proposed (new) cmi5 Features for spec version 2.0 (IEEE)

#1 - “Requires” - LMS would then be responsible for restricting the UX and the UI accordingly

  • LMS already understands when moveOn criteria is met, this is only a restriction
    • Also understands when an AU is waived, which is the functional equivalent (of MoveOn Criteria being met)
  • Requires does work on a block
    • LMS interprets this as “requires” on each element within that block
  • Can the requires idref be a block?
    • LMS interprets this as a list of “requires”
    • LMS would check the block’s Satisfied Status (Satisfied Statement issued)
  • LMS has to recognize a condition where nothing is launchable and consider the course status (in regard to the user registration) as blocked.
    • Requires could create a non-launchable course (the LMS has to be able to recognize this condition but is not required to provide specific actions)
  • LMS MAY optionally evaluate – as an import function, determine if a course is unsatisfiable and then SHOULD reject its import.
  • If the idref of a requires is not in the coursestructureformat, then reject the coursestructureformat
  • LMS course admin can override

Course Structure Topics

  • Where do we allow course structures to be mutated?
  • MasteryScore example for changing a course after import. (is different because of runtime)
  • As a general rule, the LMS may choose to modify course post import.
    • Course Sequencing
      • The requires and collateralCredit extensions provide basic rules (perquisites and equivalency) that many LMS systems provide
      • There is not a general consensus whether course sequencing features (requires and collateralCredit) should be included in cmi5
      • The DoD community needs limited sequencing interoperability

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/

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