Skip to content

CMI 5 Subgroup Meeting Notes – Dec 22nd, 2023

Bill McDonald edited this page Dec 22, 2023 · 2 revisions

cmi5 Subgroup Meeting Notes – Dec 22nd, 2023

Attendee List

  • Andy Johnson
  • Bill McDonald
  • Christopher Thompson
  • Franklin Ludgood
  • Henry Ryng
  • Florian Tolk
  • Megan Bohland
  • Martin Koob
  • Yifei Dong
  • Brian Duck
  • Simon Hsu

Notes


"Derived Requirements" Review

The group continued its review of "Derived Requirements" (from CATAPULT documentation) to identify areas of the spec that may need revision:

  • 9.3.0.0-2 (d) The LMS must track which "cmi5 defined" statement verbs have been used in a session.

    • “track meaning” ?
    • Not really actionable? - An overarching statements (there are a collection of statement rules for each of the cmi-5 defined statements in a session.
  • 9.3.0.0-2 (d) The LMS must reject "cmi5 defined" statements that use verbs already used in a session.

    • Agreed
  • 9.3.0.0-3 (d) The LMS must reject "passed" or "failed" statements received after the first "passed" or "failed" statement.

    • Agreed – another “AU reciprocal requirement”
  • 9.3.0.0-4 (d1) The LMS must track when the "initialized" statement has been received for a session.

    • Not really actionable?
    • Does “When” mean an event or a timestamp (timestamp or received) ?
    • To enforce order ?
    • “track meaning” ?
  • 9.3.0.0-4 (d2) The LMS must reject statement requests received before the "initialized" statement.

    • Agreed – another “AU reciprocal requirement”
  • 9.3.0.0-5 (d1) The LMS must track when the "terminated" statement has been received for a session.

    • Not really actionable?
    • Does “When” mean an event or a timestamp (timestamp or received) ?
    • To enforce order ?
    • “track meaning” ?
  • 9.3.0.0-5 (d2) The LMS must reject statement requests received after the "terminated" statement.

    • Agreed – another “AU reciprocal requirement”
    • Add language specifying - … (in a session)
    • Order enforcement
    • “track meaning” ?
  • 9.3.0.0-6 (d1) The LMS must track when a "completed" statement has been received for a registration.

    • Does “When” mean an event or a timestamp (timestamp or received) ?
    • To enforce order ?
    • “track meaning” ?
  • 9.3.0.0-6 (d2) The LMS must reject "completed" statements received for a registration after a "completed" statement has already been received.

    • Agreed – another “AU reciprocal requirement” (or sorts)
    • Current language for AU - Multiple completed statements are not allowed per registration
    • Clarify if sequence vs multiple should be specified
  • 9.3.0.0-7 (d1) The LMS must track when a "passed" statement has been received for a registration.

    • “track meaning” ?
    • Does “When” mean an event or a timestamp (timestamp or received) ?
    • To enforce order ?
  • 9.3.0.0-10 (d) The LMS must track that an "abandoned" statement has been recorded for a session.

  • 9.3.0.0-11 (d1) The LMS must track that a "waived" statement has been recorded for a session.

    • Not needed (see next)
  • 9.3.0.0-11 (d1) The LMS must track that a "waived" statement has been recorded for an AU for a registration.

    • “track meaning” ? – (LMS must track itself)
    • Implementation pre-requisite for the next rules (the specific rules in the statement sections should cover the requirement)

All Previous cmi5 Meeting Minutes/Notes

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

cmi5 on GitHub:

http://aicc.github.io/CMI-5_Spec_Current/

Clone this wiki locally