CMI 5 Working Group Meeting Minutes – February 14th - AICC/CMI-5_Spec_Current GitHub Wiki
cmi5 Working Group Meeting Minutes – February 14th
Attendees
- Bill McDonald (Working Group Leader)
- Andy Johnson (ADL)
- Florian Tolk (ADL)
- Marcus Birtwhislte (ADL)
- Jason Haag (Veracity)
- Mark Grant (Independent)
- Henry Ryng (InXSol)
- Dennis Hall (Learning Templates)
- Art Werkenthin (RISC, inc)
- David Pesce (Exputo)
- Christopher Thompson (Medcom, Inc.)
Notes
(cmi5) jsonld - xAPI Profile
The group reviewed the cmi5 (jsonld) profile (see below) with Jason Haag (xapi-profiles specification expert) to understand what changes would be necessary to make the profile accurately reflect the cmi5 specification:
The cmi5 jsonld was originally considered a "draft" and did not get much review. Since the cmi5 specification was developed BEFORE the xapi-profiles specification, the cmi5 jsonld used conventions (from xapi-profiles) that was in conflict with the cmi5 specification. Is is also generally understood that the cmi5 specification can not be entirely defined with the xapi-profiles specification as it has conditional behaviors that cannot be validated with xapi-profiles schema. After some discussion about the status of the xAPI Profile server development and how the xapi-profiles are structured, the group agreed on the following next steps:
1. Profile ID - The Profile ID will be changed to correctly match the cmi5 context category id (e.g. "https://w3id.org/xapi/cmi5/context/categories/cmi5"). This does not follow the xapi-profiles recommended conventions, but is necessary to be functionally correct and does not cause conformance issues.
2. Profile ID versioning- In the xapi-profiles specification, The profile ID version number is appended to the profile ID and will be updated throughout the cmi5 jsonld with the correct cmi5 context category id (e.g. "https://w3id.org/xapi/cmi5/context/categories/cmi5/v1.0")
3. Remove Templates & Patterns - The xapi-profiles templates/patterns are likely not correct and updating them manually (without tools) would likely be error prone. Given how it is very early in the adoption of the xapi-profile specification, it is better to remove them now and add them back in later when tools are available (see note #5).
4. Add scope notes to explain Authoritative sources and version id alignment - Add scope notes to explain in key places that:
- The cmi5 specification is the authoritative source of truth should there be any conflict (with xapi-profile for cmi5)
- The cmi5 specification has conditional behavior that cannot be defined in the jsonld schema and explain what those behaviors are (or reference parts of the cmi5 specification that explain those behaviors)
- In future revisions of the cmi5 specification, the Profile ID will likely be changed to follow the Profile ID convention in the xapi-profiles specification.
5. After xAPI Profile Server design is finalized - add new templates & patterns - Once the design of the xAPI profile is finalized, there will be a better understanding xapi-profiles specification implementation and possibly tools to make the process less error prone. The xAPI Profile Server design is expected to be finalized in Q4 2020.
All Previous cmi5 Meeting Minutes
https://github.com/AICC/CMI-5_Spec_Current/wiki
cmi5 on GitHub: