CMI 5 Working Group Meeting Minutes – Sept 9th, 2022

cmi5 Working Group Meeting Minutes – Sept 9th, 2022

Attendee List

• Bill McDonald (Working Group Leader)
• Andy Johnson (ADL)
• Christopher Thompson (Medcom, Inc.)
• Brian Miller (Rustici Software)
• George Vilches (Rustici Software)
• Yifei Dong (Keybridge Technologies)
• Henry Ryng (INXSOL)
• Vineet Mahesh (INXSOL)
• Geir Fuhre Pettersen (Conexus)
• Tyler Mulligan (SANS)

Notes

The group continued its discussion on group actor support for cmi5 and reviewed sections of the cmi5 specification that would be impacted.

The following changes to the cmi5 specification would be needed to support group actors:

• 3.0 Definitions - Learner: The end user (or group of users) viewing/using the learning content (AUs).
• 9.2 Actor - The Actor property MUST be defined by the LMS. The Actor property MUST contain an "account" IFI as defined in the xAPI specification (for Agent or Identified Group).
• 8.1.3 actor - Description: A JSON Actor object (as defined in the xAPI specification) that identifies the individual learner (or group of learners) launching the AU so the AU will be able to include it in xAPI requests.
• 10.0 xAPI State Data Model - agent: Actor representing the LMS learner being enrolled. This MUST match the actor property used by the LMS at AU launch time
• 11.0 xAPI Agent Profile Data Model - In cmi5, Learner Preferences are scoped to the Actor representing the enrolled LMS learner.
• Actor Examples - Provide examples of Both a Group Actor AND an Agent/Individual Actor in designated sections. (e.g. Section 8)

Currently, most (if not all) LRS’s will the allow calls to the document API’s to use a group actor with an IFI and will ignore the member list if present. (Event though the xAPI spec may have some ambiguity about group actors with document APIs, these changes could be implemented and reasonably expected to work)

cmi5 Specification clarification

Section 10.0 xAPI State Data Model should change "State API PUT Properties:” should be “State API parameters:”. As the method (PUT or POST) is not called out as a requirement and is not relevant.

New cmi5 functional changes and handoff to IEEE

The group discussed the time frame for adding potentially new features to cmi5 (including group actor). It was determined that actual spec changes should wait until the cmi5 specification is handed off to the IEEE. The establishment on an IEEE working for cmi5 is expected sometime in Q1 2023. In the meantime the cmi5 working group will continue to identify new functional/feature changes.

---

All Previous cmi5 Meeting Minutes

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

cmi5 on GitHub:

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