-
Notifications
You must be signed in to change notification settings - Fork 91
CMI 5 Subgroup Meeting Notes – Jan 19th, 2024
Bill McDonald edited this page Jan 26, 2024
·
5 revisions
cmi5 Subgroup Meeting Notes – Jan 19th, 2024
Pending....
"Derived Requirements" Review
The group continued its review of "Derived Requirements" (from CATAPULT documentation) to identify areas of the spec that may need revision:
There are requirements that seem to let the LMS change values, when it should instead be rejecting a Statement (9.5 series)
- 9.5.2.0-1 (d2) The LMS must set "result.success" to
true
for cmi5 defined statements that it stores using the "waived" verb. - 9.5.3.0-1 (d2) The LMS must set "result.completion" to
true
for cmi5 defined statements that it stores using the "waived" verb. * LMS is composing the Statements not modifying them
- 9.6.0.0-1 (d) The LMS must reject cmi5 defined statements that don't include a context object or include a context object that is not conformant to section 9.6.
- Agreed
- 9.6.1.0-1 (d) The LMS must reject cmi5 defined statements that don't include the "registration" property or include a different value than that provided by the LMS.
- Agreed
- 9.6.2.0-1 (d) The LMS must reject cmi5 defined statements that do not include all contextActivities values as provided by the context template.
- Agreed
- 9.6.2.2-1 (d1) The LMS must reject cmi5 defined statements that include the "result.success" or "result.completion" property that do not include the moveOn category activity in the "context.contextActivities.category" list. [Completed]
- Agreed
- 9.6.2.2-1 (d2) The LMS must reject cmi5 defined statements that include the "result.success" or "result.completion" property that do not include the moveOn category activity in the "context.contextActivities.category" list. [Passed]
- Agreed
- 9.6.2.2-1 (d3) The LMS must reject cmi5 defined statements that include the "result.success" or "result.completion" property that do not include the moveOn category activity in the "context.contextActivities.category" list. [Failed]
- Agreed
- 9.6.2.2-1 (d4) The LMS must have an Activity object with an "id" of "https://w3id.org/xapi/cmi5/context/categories/moveon" in the "category" context activities list for cmi5 defined statements that it stores using the "waived" verb.
- Statements containing the waived verb generated by the LMS must have an Activity object with an "id" of "https://w3id.org/xapi/cmi5/context/categories/moveon" in the "category" context activities list/
- 9.6.2.2-2 (d) The LMS must reject statements that include the moveOn category activity in a "context.contextActivities" list that are not cmi5 defined statements or that are cmi5 defined statements that do not contain either a "result.completion" or "result.success" property.
- Split into cmi5 defined statements vs not cmi5 defined statements
- The LMS must reject statements that include the moveOn category activity in a "context.contextActivities" list that are not cmi5 defined statements.
- The LMS must reject statements that include the moveOn category activity in a "context.contextActivities" list that are cmi5 defined statements that do not contain either a "result.completion" or "result.success" property
- 9.6.3.1-4 (d) The LMS must reject statements that it receives from the AU that do not include the session id in the session id context extension.
- Agreed
- 9.6.3.2-2 (d) The LMS must reject statements it receives from the AU that do not include the masteryScore extension value in the context but include a score and the "passed" or "failed" verb.
- Agreed
- 9.7.0.0-1 (d) The LMS must reject statements received from the AU that do not include the timestamp property.
- Agreed
- 9.7.0.0-2 (d) The LMS must reject statements received from the AU that include a timestamp property value that is not in UTC.
- Agreed
- 10.2.1.0-5 (d) The LMS must reject non-GET requests from the AU for the "LMS.LaunchData" state profile document.
- (HTTP GET)
- Agreed
- Revise Section 10.1 to specify “State API Properties:” instead of “State API PUT Properties:”
- Specify the API resource (xAPI State API)
- 10.2.1.0-6 (d) The LMS must reject statements that do not have a "context" object based on the "contextTemplate" provided to the AU via the launch data State API document.
- Agreed
- 10.2.1.0-7 (d) The LMS must reject statements that include a "context" object that has contextTemplate property values that have been overwritten.
- Agreed
- 10.2.2.0-1 (d) The LMS must track what launchMode was used for a given AU launch session.
- Observable data – Track is a means (Implementation specific)
- Anything with “track” is not really necessary for normative requirements
- 10.2.2.0-2 (d) The LMS must reject cmi5 defined statements that use the "passed", "failed", or "completed" verb received from the AU [during a session with a "Browse" launchMode].
- Agreed
- 10.2.2.0-3 (d) The LMS must reject cmi5 defined statements that use the "passed", "failed", or "completed" verb received from the AU [during a session with a "Review" launchMode].
- Agreed
- 10.2.2.0-5 (d) The LMS must reject statement requests that do not conform to the value of "launchMode".
- Agreed