Skip to content

CMI 5 Working Group Meeting Minutes – May 12th

Jump to bottom Edit New page
Bill McDonald edited this page May 13, 2017 · 2 revisions

cmi5 Working Group Meeting Minutes – May 12th, 2017

Attendees

  • Bill McDonald - cmi5 working group leader
  • Andy Johnson - ADL
  • Brian Miller - Rustici Software
  • Dennis Hall - Learning Templates
  • Clayton Miller - NexPort Engineering
  • Christopher Thompson – Medcom Inc.
  • David Pesce - Exputo
  • Giovanni Sorrentino – E-CO e-Learning Studio
  • Henry Ryng - InXSOL
  • Art Werkenthin - RISC Technology
  • Dinesh Vardham - IBM

Notes

Best Practice #11 – Use “progressed” verb for indicating progress during a session.

The group added a new best practice for measuring "progress" as shown below. The purpose of the best practice is to offer guidance on how to report progress to the LMS during an AU session. The associated JSON example Usage of Progress Extension was also update to reflect this new best practice

Best Practice #11 – Use “progressed” verb for indicating progress during a session.

For recording progress during a session, it is recommend to use a cmi5 allowed statement with the progressed verb (http://adlnet.gov/expapi/verbs/progressed) and a progress extension in the result (see section 9.5.5.1 of specification). Progress statements should not be sent for progress value of 100% as that indicates completion. Once the learner reaches 100% it is recommended that a cmi5 defined “completed” statement be issued instead.

Gherkin/Cucumber Style Tests

The group explored describing cmi5 compliance tests in Gherkin notation. The following is an initial take on testing an LMS's content launch capability:

Feature: Learner Launch (LMS tests)

Given: A launch link is requested (by learner action…)
When: The launch link is provided
Then: The launch links is verified (verify all name/value pairs are present and have valid values)

Given: A launch Link from the LMS
When: the fetch URL is executed
Then: The fetch URL return value is verified (a valid JSON structure for authentication per spec)

Given: A launch Link from the LMS
When: the endpoint is executed to retrieve the LMS.Launch Data document (from State API)
Then: A valid LMS.Launch Data document is returned

Discussion for next week

  • Review xAPI Compliance Testing Team's methodology
  • Discuss approach to cmi5 compliance testing

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/

cmi5 Working Group Wiki

Home

Meeting Minutes

Working Documents

Clone this wiki locally