-
Notifications
You must be signed in to change notification settings - Fork 91
CMI 5 Subgroup Meeting Notes – Mar 15th, 2024
cmi5 Subgroup Meeting Notes – Mar 15th, 2024
- Andy Johnson
- Bill McDonald
- Christopher Thompson
- Franklin Ludgood
- Jim Taite
- Megan Bohland
- Simon Hsu
- Yifei Dong
The group reviewed the issues backlog to identify possible updates for the pending IEEE cmi5 specification.
Issue #715 What is the best practice for when to send completed or passed statements?
This was previously indicated for a best practice and the group generally agreed with this assessment but believed a best practice for this scenario should be generalized for scenarios where the AU design may delay sending statements.
The following initial draft language was discussed:
Best Practice #18 – Send statements as close to Learner events as possible. There are certain practices that and AU designer should avoid in order to prevent data loss and ensure data is available when it is needed.
Situations to avoid (Online):
- Delaying sending statement after a learner completes a significant milestone (such as passing a scored assessment)
- Sending Completed and Passed statements on a browser window exit event. (may result in data loss)
- “Batching” statements to longer time events For Offline use cases, these situations are not as sensitive to data loss/availability issues.
Course Structure Extensions
The group continued its discussion on alternative means to add "extensions" to the course structure (per March 8th meeting)
IEEE Gitlab Status
IEEE Gitlab for cmi5 is still not deployed yet. In addition to the license agreements, there are policy discussions regarding the separation of actual Standard from Supplementary Content that still need to be resolved.