CMI 5 Subgroup Meeting Notes – Dec 15th, 2023 - AICC/CMI-5_Spec_Current GitHub Wiki
cmi5 Subgroup Meeting Notes – Dec 15th, 2023
- Andy Johnson
- Ang Boon Chong
- Bill McDonald
- Florian Tolk
- George Vilches
- Henry Ryng
- Martin Koob
- Megan Bohland
- Yifei Dong
"Derived Requirements" Review
The group continued its review of "Derived Requirements" (from CATAPULT documentation) to identify areas of the spec that may need revision:
Restarting sequence from 8.1.5-* 9.*
-
8.1.5.0-6 (d) The LMS must reject "cmi5 defined" statements from the AU that do not include the "activityId" as the "id" of the "object".
- Agreed – AU must use activityId value from the query string as the ID of object in cmi defined statements it makes
- HTTP error code for rejection? 400 Bad Request ?
- Review Catapult
-
8.2.1.0-2 (d) The LMS must handle POST requests to the URL provided in the "fetch" parameter.
- Agreed
- The LMS MUST implement (an HTTP Listener with) a HTTP POST method for the fetch URL
- The HTTP Listener must reject HTTP methods other than POST ? (new functionality)
-
8.2.3.0-1 (d) The LMS must track that the "fetch" URL has been requested.
- Not really actionable?
- (stopped by other mechanisms)
-
9.1.0.0-1 (d) The LMS must reject statements received that do not contain a statement id.
- Agreed – another “AU reciprocal requirement”
HTTP Error Code Discussion
The group also discussed what HTTP error codes should be used by the LMS/LRS when "rejecting" statements:
- Looking for a “statement allowed” - 200 or 204 (is a pass) all other status codes are a failure
- Looking for a “statement rejected” – 400 for xAPI error, 403 for a cmi5 error (is a pass) - all other status codes are a failure (with exceptions like “abandoned”)