-
Notifications
You must be signed in to change notification settings - Fork 91
CMI 5 Working Group Meeting Minutes – January 15th, 2016
cmi5 Working Group Meeting Minutes – January 15th, 2016
Attendees
- Bill McDonald - cmi5 Working Group Leader
- Bernard Bouyt - Airbus
- Andy Johnson – ADL
- Ben Clark – Rustici Software
- Brian Miller – Rustici Software
- Ray Lowery - Pratt & Whitney
- David Pesce - Exputo
- Mike Kennedy - Workday
- Christopher Thompson - Medcom Inc
- Charles Touron - ATSC
- Anthony Altieri - American Red Cross
- Patrick Selby - LexusNexis
Notes
"Fast Tracking" Pull Requests
The group agreed to "fast track" pull requests between meetings to help accelerate cmi5 spec work. Pull requests that get "thumbs up" comments from Andy Johnson (ADL), Bill McDonald, and 1 or more other active participants will be added prior to the next meeting. All changes can be revisited prior to formal release.
cmi5 Specification Changes
The following pull requests were reviewed and applied:
- Remove "authenticationMethod" from AU metadata - #377
- Switch to example.com for remaining sample URLs - #376
- Remove redundancy in "Terminated" and "Abandoned -#375
- Items related to Result objects -#374
- Fix items related to "passed" and "failed" verb statements - #373
- Improve language for "contextTemplate" - #371
- Switch to use "request" instead of "message" - #370
- "CMI5" -> "cmi5" - #369
- Improvements to "masteryScore" and "moveOn" in LaunchData section - #368
- Note example launch URL not encoded - #367
- Remove unnecessary description of Activity - #366
- Remove unnecessary language from IRI definition - #364
- Set version of xAPI specification to 1.0.x - #363
- Markdown fixes - #362
- Add masteryScore as context extension - #359
- Indicate score properties are inclusive - #355
Issue #297 - cmi5 Statement Sequencing Issues (Per Oct 23 Meeting)
The group agreed on the following change to the timestamp property definition to indicate that there can be duplicate timestamp entries.
9.7 Timestamp
To ensure statement ordering requirements are met, all statements MUST include a timestamp property per the xAPI specification. All timestamps MUST be recorded in UTC time. Timestamps are not required to be unique in statements within a session. The time recorded should indicate when the condition actually occurred.
All Previous CMI-5 Meeting Minutes
https://github.com/AICC/CMI-5_Spec_Current/wiki
CMI-5 on GitHub: