CMI 5 Subgroup Meeting Notes – September 29th, 2023 - AICC/CMI-5_Spec_Current GitHub Wiki
cmi5 Subgroup Meeting Notes – September 29th, 2023
Attendee list pending...
The group continued its discussion about how cmi5 should address xAPI Version Compatibility.
Questions to raise at the cmi5 voting meeting:
- Q1 - Should the cmi5 spec be updated to provide a mechanism for xAPI Version Compatibility?
- Q2 – Should the cmi5 spec use the course structure (AU level xAPI version supported)
Should the cmi5 spec be updated to provide a mechanism for xAPI Version Compatibility?
- Propose that the course structure be updated to include supported xAPI version(s) by the AU (for the LMS to use). AU level property (minimum supported version) added to the course structure.
Options:
- Default value 1.0.x or specific single minimum value
- List of versions
(Quality of Implementation) Actions by the LMS:
- May Rejects AU at import time
- On a per AU basis, the LMS will provide the specified xAPI version end-point
- If multiple versions are specified, the LMS should provide an xAPI endpoint with the highest xAPI version that supports.
- The LMS must not place any elements in the contextTemplate that are not supported by the version of xAPI for the endpoint provided to the AU.
- The LMS must send an Abandoned statement if the AU launches and fails due to an incompatible version of xAPI. AU
- AU should call the About resource and determine the xAPI version endpoint
- The AU should adjust it headers and statement formation to match the xAPI version endpoint provided
- (best practice) AU should display an error message and may exit if it cannot support the version of the xAPI endpoint provided .