CMI 5 Working Group Meeting Minutes January 16th, 2015 - AICC/CMI-5_Spec_Current GitHub Wiki

CMI 5 Working Group Meeting Minutes - January 16th, 2015

Attendees

• Bernard Bouyt - Airbus
• William A. McDonald – Boeing Flight Services
• Andy Johnson – ADL
• Henry Ryng – INXSOL
• Ben Clark – Rustici Software
• Vijay Budhram - Rip Tide
• Art Werkenthin – RISC
• Ray Lowery – Pratt & Whitney
• Pankaj Agrawal - Next Software Solutions

If I missed anyone, please let me know…

Notes

CMI-5 Conformance Testing Procedures

The group continued its discussion of conformance testing procedures for the CMI-5 Course Structure

The following test procedure overview was discussed in more detail based on last week’s meeting.

Import Test

Import a Reference Course Structure

There will be a reference course structure as part of testsuite software and it will have the following properties:

• 1000 AU's
• Each AU will have specific metadata:
  • AU metadata will program generated by the TestSuite
  • URL with Query String of "vendor defined" name/value pairs
    • TestSuite Design will not exceed URL size for most major browsers.
  • LaunchParameters - vary the size - randomize the structure * Verify that ActivityID is unique. (check for uniqueness within course) * Verify that ActivityID is a valid IRI (IRI format check) * Check all fields for format / data type / Vocab (XSD schema validation)
• Launching (Reference) Content
  • The content will check to see if the launch parameters sent. (By computer)
    1. Check for the Launch Parameters, Mastery Score, Entitlement Key, LaunchMethod at runtime - verify they are present (and the same as in ref course struct) in a State API call (Per section 10 of runtime)
    • Content will check launch window (as user launches content)
  1. Verify correct launchmethod was used - inspect window and window sibilings/framset
     • Verify Hierarchy (Blocks) in UI (possibly by human)
     • verify other required "behaviors" (possibly by human)

CMI-5 Specification Changes

The discussion over AU launchMethod verification sparked a long discussion over the content requirements for launch window.

It was generally agreed that, rather than specifying “NewWindow” or “ExistingWindow”, LaunchMethod should specify whether or not the AU requires “its own browser window” (which means either a redirect on the existing window or a new browser window). If an AU does not require “its own browser window”, then it could be place in a frameset, etc (still given its own window).

So the launchMethod will be changed to have 2 Vocabulary values:

• “OwnWindow” – The LMS must launch AU either a new window or redirected window
• “AnyWindow” - Content does not care about the window context (all browser windows options are acceptable – FrameSet, New Window, redirect, etc.) LMS can use whichever method desired.

In light of this change, the CMI-5 Runtime Specification will need to be changed to have the LMS determine when to set the ReturnURL (whether the LMS is redirecting or spawning a new window). AU must redirect to ReturnURL when closing if it is specified in State API.