CMI 5 Working Group Meeting Minutes – October 16th, 2015

cmi5 Working Group Meeting Minutes - October 16th, 2015

Attendees

• Bill McDonald - cmi5 Working Group Leader
• Andy Johnson – ADL
• Brandt Dargue – Boeing Research & Technology
• Bernard Bouyt - Airbus
• Ben Clark – Rustici Software
• Art Werkenthin – RISC Inc
• Henry Ryng – inXsol
• Andrew McGarrity – Thrivist
• Yegor Yenikyeyev - Thrivist
• Dennis Hall - Learning-Templates.com
• Richard Hodgins - Intuition Publishing
• John Blackmon – Trivantis
• David Pesce – Exputo
• Charles Touron – ASTC
• Patrick Selby – LexisNexis
• Rodolfo Long – ETS

Notes

Multiple Passed/Failed (cmi5 defined) Statements in a single session.

The Pull Request – “Issue 262/263 - Multiple Passed/Failed Statements #290” was reviewed by the group and it was determined that more edits were needed. It was deemed necessary to group verb ordering rules in one place for greater clarity.

The following will changes will be made to “9.3 Verbs”:

Add the following language:

Note that “cmi5 allowed” statements are NOT subject to the usage rules in this section. All statements in this section refer to "cmi5 defined" statements unless otherwise noted.

Add the following language:

AU Verb Ordering Rules within an AU session are as follows:

1. No (cmi5 defined) verbs can be duplicated

2. Only zero or one of the set of {Passed,Failed}

3. Initialized must be first statement (cmi5 allowed or defined)

4. Terminated must be the Last statement (cmi5 allowed or defined)

Remove: "(cmi5 defined)" in the verb specific subsections of 9.3

Remove: All references to “passIsFinal” (In all sections of the cmi5 specification)

Multiple Attempt Use Case / Best Practice document.

The issues regarding the definition of what an “attempt” is and how it maps to an AU session have been re-visited multiple times (over a long period of time) causing a few reversals in direction. The group determined that how these issues can be addressed in cmi5 need to be defined and documented in a detailed best practices/use cases document so that the “why” of the related decisions are well understood. (i.e. how to do I handle the use case of multiple attempts at test within a cmi5 AU session, etc.)

Next Meeting:

Next Meeting: October 23rd, 2015 – 10:30 am US Eastern Time