CMI 5 Subgroup Meeting Notes – Oct 27th, 2023 - AICC/CMI-5_Spec_Current GitHub Wiki

cmi5 Subgroup Meeting Notes – Oct 27th, 2023

• Andy Johnson
• Bill McDonald
• Christopher Thompson
• Franklin Ludgood
• Henry Ryng
• Jim Taite
• Martin Koob
• Megan Bohland
• Simon Hsu

---

The group discussed the following items:

Best Practices - AU awareness of the other AU’s of the course (there status and which ones are members)

• AU launch of other AU’s
• Auto launch of “next AU” indicated by current AU
• Send manifest data in the context template
  • State API – Content
  • State API
  • Activity Profile API
• Super Router/AU
• LMS created activity for the course (manifest):
  1. LMS creates Activity ID for the course
  2. Activity ID passed in the context template (for the Manifest)
  3. AU queries the Activity ID profile to get course manifest

Possible New cmi5 Features for IEEE version:

• Multi learner actors (class)
• AU awareness of other AU’s in the course

Migrate cmi5 1.0 – to gitLab cmi5 2.0 end state – functional changes

The group reviewed the following "Derived Requirements" (from CATAPULT documentation):

7.1.2.0-1 (d1) : The LMS must track that the AU has issued a "Terminated" statement.

• What is the purpose of this derived requirement?
• What is the LMS supposed to do to comply with this requirement?
• Must verify that the AU has issued a Terminated Statement (or Issue an abandoned statement) before launch a new AU session ?

7.1.2.0-1 (d2): The LMS must reject attempts by the AU to store statements received after the "Terminated" statement.

• LMS must reject the all statements (AU Activity ID/actor/registration/session id) received after a "Terminated" statement for that (AU Activity ID/actor/registration/session id)
• Statement Rejection as defined in the xAPI specification
• Statement Voiding as defined in the xAPI specification

7.1.3.0-1 (d1): The LMS must reject attempts by the AU to store statements or void stored statements received before the "Initialized" statement.

• LMS must reject the all statements (AU Activity ID/actor/registration/session id) received before a " Initialized" statement for that (AU Activity ID/actor/registration/session id)
• Statement Rejection as defined in the xAPI specification
• Statement Voiding as defined in the xAPI specification

7.1.3.0-1 (d2): The LMS must reject attempts by the AU to store statements or void stored statements received after the "Terminated" statement."

• See 7.1.2.0-1 (d2):

8.1.0.0-6 (d): The LMS must inspect all AU URLs in the course structure data for query string parameters that conflict with "endpoint", "fetch", "actor", "registration", or "activityId" and reject import of course structure data with conflicts.

• The process by which an LMS creates an instance of cmi5 course is by processing a course structure format is called “import”
• Rejection of an import is an interruption of processing and not recognized that course.
• Error reporting ? (to admin user ? error conditions?)
• LMS must reject course structures (at Import time) that have AU URLs with "endpoint", "fetch", "actor", "registration", or "activityId"

---

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

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