-
Notifications
You must be signed in to change notification settings - Fork 91
CMI 5 Working Group Meeting Minutes – January 13th, 2023
Bill McDonald edited this page Feb 3, 2023
·
1 revision
cmi5 Working Group Meeting Minutes – January 13th, 2023
Attendee List
- Bill McDonald (Working Group Leader)
- Andy Johnson (ADL)
- Martin Koob (VideoLinkWell)
- James Taite (DLA)
- Brian Miller (Rustici Software)
- Thomas Turrell-Croft
- Christopher Thompson (National Council For Mental Wellbeing)
- Florian Tolk (ADL)
- Megan Bohland (ADL)
- Henry Ryng (InXSOL)
- Simon Hsu (Keybridge Technologies)
- Tyler Mulligan (SANS)
- Vineet Mahesh (InXSOL)
- Yifei Dong (Keybridge Technologies)
Notes
Statement Voiding
The group continued its discussion on Statement Voiding in the context of cmi5...
Possible Voiding Best Practices/Recommendation Document (cmi5):
- In general, Voiding any statements in xAPI is problematic as statements may reference other statements.
- Voiding Statements should be reserved for extreme or unusual circumstances where the data should not have been recorded. This does NOT include the following situations:
- Where a technical failure has occurred causing the AU to crash., in this situation, the Abandoned statement should be used.
- If a training session “goes badly” and the trainee needs a “do over”. In this situation a Waived statement can be issued.
- Voiding cmi5 defined statements could cause cascading effects with MoveOn conditions (and cmi5 rules). If a cmi5 defined statement is voided, if the possible that the rest of the statements in the session would need to be voided to maintain consistency.
- Voiding cmi5 allowed statements does not affect cmi5 MoveOn and course completion rules but should you should take the same care in voiding that you would for any other xAPI statement.
All Previous cmi5 Meeting Minutes
https://github.com/AICC/CMI-5_Spec_Current/wiki
cmi5 on GitHub: