CMI 5 Working Group Meeting Minutes – April 6th - AICC/CMI-5_Spec_Current GitHub Wiki

cmi5 Working Group Meeting Minutes – April 6th

Attendees

  • Bill McDonald (Working Group Leader)
  • Andy Johnson (ADL)
  • Art Werkenthin (RISC, inc)
  • Clayton Miller (NextPort)
  • Ray Lowery (Pratt & Whitney)
  • Jeremy Chapman (Pratt & Whitney)
  • David Pesce (Exputo)
  • Mark Grant (independent)
  • Christopher Thompson (Medcom, Inc.)
  • Dennis Hall (Learning Templates)
  • Shouming (John) Jiang (independent)

Notes


cmi5 Conformance Testing

The group completed reviewing the (LMS specific) "testing requirements checklist" in order to verify which testing requirements were not covered by the current draft of testing scenarios.

The group determined that LMS specific features of cmi5 that are optional will be handled in additional tests for "higher levels" of conformance. Minimum conformance will be focused on first.

Requirement Removed

The following requirement is not necessary to test as it is a "roll-up" of other requirements:

cmi5_9.4._3 Learning Management System (LMS): The LMS must provide an object in all (cmi5 defined) statements.

New LMS Test Scenarios

The following requirement as identified as needing a new test scenario created:

cmi5_4.2_1 Learning Management System (LMS): The LMS MUST (have access to) be able to retrieve all Resource data (from the Statement API, etc., including attachments and extensions) about another distinct user across multiple sessions for that user.

Additions to all LMS Test Scenarios

The following items need to be added to all LMS Test scenarios:

  • Post processing required to review all LRS statements to verify (proving a negative) for the following requirements:

    cmi5_9.3.1_2 Learning Management System (LMS): The LMS MUST NOT issue multiple Launched (cmi5 defined) statements for given a session id.

    cmi5_9.5.3_4 Learning Management System (LMS): The LMS must not include the " completion" property for (cmi5 defined) statements other waived.

  • Verify that all cmi5 defined statement have the cmi5 category context:

    cmi5_9.6.2.1_1 Learning Management System (LMS): The LMS must include An Activity object with an "id" of "https://w3id.org/xapi/cmi5/context/categories/cmi5" in the "category" context activities for all cmi5 defined statements it issues.

  • All scenarios with a Launched Statement must add a check for this requirement:

    cmi5_9.6.3.4_1 Learning Management System (LMS): The LMS MUST put a fully qualified URL equivalent to the one that the LMS used to launch the AU without the name/value pairs included as defined in section 8.1 as a context extension of the "Launched" statement.

  • All scenarios must add a check for this requirement (timestamp):

    cmi5_9.7_1 Learning Management System (LMS): All statements issued by the LMS MUST include a timestamp property in UTC time.

  • All scenarios with course structures must add a check for these requirements:

    cmi5_10_3 Learning Management System (LMS): LMS MUST include a value for launchMode in LMS.LaunchData State document.

    cmi5_10_5 Learning Management System (LMS): LMS MUST include a value for launchParameters in LMS.LaunchData State document.

    cmi5_10_6 Learning Management System (LMS): LMS MUST include a value for masteryScore in LMS.LaunchData State document if a value for masteryScore is defined in the course structure.

    cmi5_10_7 Learning Management System (LMS): LMS MUST include a value for moveOn in LMS.LaunchData State document.

    cmi5_10_9 Learning Management System (LMS): LMS MUST provide an entitlementKey object in "LMS.LaunchData" if an entitlementKey value is present for the AU in the course structure.

    cmi5_10_10 Learning Management System (LMS): LMS MUST set the entitlementKey object property “courseStructure” to the value of entitlementKey.courseStructure present for the AU in the course structure.

    cmi5_13_1_1 Learning Management System (LMS): All leading/trailing whitespace MUST be removed by the LMS on import of the course structure for all of the data elements defined in section 13.

    cmi5_14_0_1 Learning Management System (LMS): The LMS MUST be able to import a course structure from a cmi5.xml file.

    cmi5_14_0_2 Learning Management System (LMS): The LMS MUST be able to import a course structure from a Zip64 file (containing a cmi5.xml file).

    cmi5_14_0_3 Learning Management System (LMS): The LMS MUST be able to import a course structure from a Zip32 file (containing a cmi5.xml file).

cmi5 Best Practices - Existing Window

The following testing requirement will be revised to remove "new window" as it is not in the vocabulary option for launchMethod and may cause confusion over the best practice of using the same browser window to redirect to the AU (and the AU redirecting back)

cmi5_8.1_2 Learning Management System (LMS): The AU MUST be launched by the LMS using the method specified in the course structure metadata. (new window, redirect existing window, or any window)


Discussion for next meeting

  • Add requirement cmi5_8.1_2 to test scenario #4 - Individual AU Test (2 AU Course - Abandoned) - Simple Launch (abandoned 2AU’s)

  • Continue to add other missing requirements on checklist to existing LMS testing scenarios

All Previous cmi5 Meeting Minutes

https://github.com/AICC/CMI-5_Spec_Current/wiki

cmi5 on GitHub:

http://aicc.github.io/CMI-5_Spec_Current/

⚠️ **GitHub.com Fallback** ⚠️