CMI 5 Working Group Meeting Minutes – November 7th, 2014

CMI 5 Working Group Meeting Minutes - November 7th, 2014

Attendees

• William A. McDonald – Boeing Flight Services
• Bill Shook – Boeing Defense Systems
• Andy Johnson – ADL
• Art Werkenthin - RISC
• Wes Hargrove – Lynda.com
• Ben Clark – Rustici Software
• Chris Handorf – Pearson
• Henry Ryng – INXSOL

Notes

LRS Query Optimization This issue is considered closed for now. (In addition to the CMI-5 context tags) the CMI-5 group will make recommendations to the XAPI group for enhancement to XAPI’s query capabilities

More Spec “clean-up” The rest of the meeting was focused on general specification “clean-up” based on past discussions…

(CMI-5 Runtime Spec)

10.0 XAPI State Data Model

Add MasteryScore to LMS.LaunchData document as follows:

MasteryScore

Description: The MasteryScore from the Course Structure. Used by the LMS when launching the AU (in a web-browser environment) to tell the AU what the MasteryScore is.

LMS Required: Yes

AU Required: Yes

LMS Usage: LMS must include the MasteryScore value based on the value defined in the course structure for the AU being launched.

AU Usage: AU must issue Passed or Failed statements based on the MasteryScore provided. (See sections 9.3.6 and 9.3.7)

Data type: String

Value space: Decimal Value 0 to 1.0

Sample value: "0.75”

Add MasteryScore to Example

{
   "Context_Template": {
         "extensions": {
            "http://www.aicc.org/cmi-5/extensions/session": <LMS generated Session ID>
         }
   },
   "launchMethod": "<launch method from the Course Structure>",
   "launchMode": "<launchMode value>",
   "launchParameters": "<launch parameters from Course Structure>",
   "masteryScore":0.76,
   "returnURL": "<URL value>",
   "entitlementKey": {
       "courseStructure": "<Entitlement data or key from Course Structure>",
       "alternate": "<alternateEntitlementKey>"
   }
}

8.1.1 Launch Method

Add this reference: (See Course Structure 7.1.4 AU Meta Data - URL)

9.3.1 Launched

Add this reference: (See Statement API Section 10)

9.3.6 Passed

AU Obligations

Modify language as follows: The AU must record a statement containing the "Passed" verb when the learner has attempted and passed AU. The AU must not issue multiple statements with "Passed" for the same AU within a given AU session or course registration for a given learner. If the "Passed" statement contains a (scaled) score, the (scaled) score must be equal to or greater than the "Mastery_Score “indicated in the course structure. (See course structure section 7.1.4)

LMS Obligations

Modify language as follows: The LMS must record "Mastery_Score" data in the state API (if present in the course structure) for the AU prior to initial AU launch. (See section 10) The LMS must use either "Passed" or "Completed" statements (or both) based on the MoveOn criteria for the AU as defined in Course Structure. (See Course Structure Section 7.1.4 MoveOn).

Usage

Add this reference: (See Course Structure Section 7.1.4 MasteryScore).

9.3.7 Failed

AU Obligations

Add this reference: (See Course Structure Section 7.1.4 MasteryScore).

LMS Obligations

Add this reference: (See section 10) Strike the following (From Section 9 Passed & Failed): The LMS must use either "Passed" or "Completed" statements (or both) for determining for course completion (or course collateral credit) criteria for the AU.

Add this reference: (See Course Structure Section 7.1.4 MasteryScore).

Abandoned

The LMS must record an "Abandoned" statement on behalf of the AU indicating an abnormal session termination. (Remove reference)

9.3.10 Terminated

Clean up references to "Exit" (replace with “Terminated”)

Modify language as follows: “In this case the LMS must record an "Abandoned" statement on behalf of the AU indicating an abnormal session termination. (See 9.3.8 Abandoned)”

(CMI-5 Course Structure Spec)

7.1.4 AU Meta Data

URL - Add Example

MasteryScore – Add language to define MasteryScore value as a “scaled score”