CMI 5 Working Group Meeting Minutes – June 23rd - AICC/CMI-5_Spec_Current GitHub Wiki

cmi5 Working Group Meeting Minutes – June 23rd, 2017

Attendees

  • Bill McDonald (Working Group Leader)
  • Andy Johnson (ADL)
  • Art Werkenthin (RISC, Inc)
  • Ben Clark (Rustici Software)
  • Dennis Hall (Learning Templates)
  • Henry Ryng (InXSOL)
  • Ray Lowery (Pratt & Whitney)
  • Clayton Miller (NextPort Engineering)
  • David Pesce (Exputo)
  • Christopher Thompson (Medcom, Inc.)
  • Steven Warwick - Health Decisions
  • Giovanni Sorentino –(E-CO e-Learning Studio)

Notes

The group discussed the following issues and continued work on the cmi5 testing requirements document.

Issue #548 - Conflict of Satisfied Rules with Session Rules

This issue deals with confusion over ordering rules for LMS issued statements versus AU issued statements. The group determined that the best way to address this issue was to add clarifying language for LMS issued statements as follows to section 9.3 Verbs :

LMS verb ordering rules are as follows:

  • LMS may issue multiple satisfied statements (in a session)
  • LMS SHOULD NOT issue multiple satisfied statements (in a registration)
  • LMS MUST NOT issue more than one abandoned statement in a session
  • LMS MUST NOT issue more than one waived statement per session and MUST not issue more than one waived statement per registration per AU.

Issue #556 - Section 8.1 AU usage for activityId inconsistent with 9.4

Section 9.4 of the specification indicates that

When the Object is the AU, the value of the Object's "id" property for a given AU MUST match the activityId defined in the launch URL.

Section 8.1 as written is inconsistent with Section 9.4 and prevents AU's from issuing "cmi5 allowed" statements with activity ids determined by the AU (which is not the intent for "cmi5 allowed" statements).

To resolve this, Art Werkenthin has proposed the following revision section 8.1 :

8.1 Launch Method

activityId

AU Usage: The AU MUST get the activityId value from the query string. The AU MUST use the activityId value as the id property of the Object in all "cmi5 defined" statements.

The group will discuss this revision further next week.


Discussion for next week

  • Develop cmi5 Conformance Testing Requirements
  • Discuss Issue #556

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** ⚠️