CMI 5 Working Group Meeting Minutes – February 12th, 2016 - AICC/CMI-5_Spec_Current GitHub Wiki

cmi5 Working Group Meeting Minutes – February 12th, 2016

Attendees

  • Bill McDonald - cmi5 Working Group Leader
  • Benard Bouyt - Airbus
  • Ben Clark – Rustici Software
  • Brian Miller – Rustici Software
  • Mike Kennedy - Workday
  • Christopher Thompson - Medcom Inc
  • Henry Ryng - InXSOL
  • David Pesce - Exputo
  • Dennis Hall - Learning-Templates.com

Notes

Issue #378 - Explicitly allow the LMS to override the "masteryScore" as defined in the course structure

The group discussed this issue at length as it raises significant questions about the scope of cmi5 and the level of interoperability expected. See the following Issue discussion thread for background: https://github.com/AICC/CMI-5_Spec_Current/issues/378

This issue began as a question on whether the "masteryScore" could be overridden by the LMS administration (i.e. a course edit after import) and then evolved into a discussion over how activity (AU) ID's and course ID's are managed. This is particularly important and the ID's are supposed to be globally unique for LRS records management. It is expected by many that xAPI Activity ID's are supposed to be meaningful identifiers on a global scale for learning credentials that maybe transferred between different companies, schools, etc.

The following change management scenarios were discussed:

  • AU Content (Media) Changes
  • AU Definition changes in Course Structure
  • (Non AU definition) Course Structure Changes:
    • Sequences
    • Organization/Blocks/Membership
    • Course Level Metadata

Some in the group believed that AU content (media) changes were out of scope for cmi5 as the cmi5 course structure is not intended to be a "manifest" like in SCORM and the course structure will often not include a ZIP file with media.

AU Definition changes (including launch parameters, etc) and (Non AU definition) Course structure changes with seen as the most likely candidates for some kind of ID related (change) management. The following proposals were made for dealing with the associated ID's for such changes.

Proposal #1 - Add an "Original ID" Attribute. This new attribute would be added to the "" element if the course structure changed at all. This attribute would contain the course ID as it was originally imported. The new ID value (for the existing "id" attribute) would be set to a a "hashed" value based on the contents of the course structure. The same method would be used for individual AU definitions if they changed within the course structure as well.

Proposal #2 - Add a "Changed ID" Attribute. This is the same method as proposal #1 except that the existing "id" attributes would retain their original values and the "Changed ID" attributed would added to the "" element and the ""elements that changed. The "Changed ID" would also be based on a "hash" algorithm.

Both proposals would need additional considerations:

  1. Is this an optional or required feature ? (A SHOULD or MUST) ?
  2. Do the "additional ID's" need to be transmitted in cmi5 statements ?

There was also a brief discussion about a "version attribute" which sounded similar to Proposal #2.

The issue was far from resolved so the discussion will continue next week.

All Previous CMI-5 Meeting Minutes

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

CMI-5 on GitHub:

https://github.com/AICC

cmi5 Working Group Wiki

⚠️ **GitHub.com Fallback** ⚠️