cmi5 Profile not in line with Spec #84
Comments
MrBillMcDonald
added a commit
to MrBillMcDonald/xapi-authored-profiles
that referenced
this issue
Feb 7, 2020
Per the cmi5 working group meeting (February 7 , 2020) the group determined that this profile is invalid and must be corrected prior to implementation. Scope note added to this effect
FlorianTolk
added a commit
that referenced
this issue
Feb 7, 2020
Issue #84 - Disclaimer from cmi5 working group
|
The cmi5 working group is concerned that developers are viewing this profile and attempting to implement cmi5 (incorrectly). We fully the support the use of xAPI profiles and look forward to resolving this issue in collaboration with @jhaag75 and any other interested parties. The cmi5 working group meets weekly and welcomes participation from all. See this conference link to register: https://attendee.gotowebinar.com/register/7685442641624643843 |
|
Per the March 6th cmi5 meeting, the group has proposed updating the next cmi5 release to move the moveOn objects from contextActivities.categories[] to contextActivities.other[] in order to more closely align. See issue below: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The cmi5 Profile is not aligned with the actual spec: https://github.com/AICC/CMI-5_Spec_Current/blob/quartz/cmi5_spec.md
Wherever the spec is in disagreement with the profile, the cmi5 spec is considered correct.
The text was updated successfully, but these errors were encountered: