CMI 5 Working Group Meeting Minutes – December 17th - AICC/CMI-5_Spec_Current GitHub Wiki

cmi5 Working Group Meeting Minutes – December 17th

Attendees

  • Bill McDonald (Working Group Leader)
  • Andy Johnson (ADL)
  • Florian Tolk (ADL)
  • Art Werkenthin (RISC, Inc)
  • Brian Miller (Rustici Software)
  • George Vilches (Rustici Software)
  • Paul Tyson (Oberon Technologies)
  • Matt Westover (ECZ & Company)
  • Mateusz Wojczal (Escola)
  • Chetan Sachdev ()
  • Geir Fuhre Pettersen (Conexus)
  • Carsten König (TUTORize GmbH)
  • Christopher Thompson (Medcom, Inc.)
  • Thomas Turrell-Croft (berrycloud)
  • Yifei Dong (Keybridge Technologies)

Notes

The group continued its discussion reviewing derived testing requirements against the cmi5 spec to determine if related spec changes are necessary.

#1 (Not Listed in Derived Requirements) - Section 6.3

  • Current Spec language:

6.3 LMS Statement API Requirements The LMS MUST NOT provide permissions/credentials which allow the AU to issue voiding Statements. The LMS SHOULD reject statements that conflict with the "Statement API" requirements as defined in Section 9. The LMS MUST Void statements that are NOT rejected AND conflict with the "Statement API" requirements as defined in Section 9.

  • “Not Rejecting Statements” is a condition that cannot be tested since the spec states “SHOULD” (per 6.3)
  • Should me changed that to match the VOID requirements?
  • LMS must EITHER reject or void is what it says but hard to implement the above due to LRS integration difficulty. So not really a spec issue.
  • VOID vs REJECT decisions are made by the implementers

#2 - 9.1.0.0-1(d) - The LMS must reject statements received that do not contain a statement id.

  • The AU MUST assign a statement id property in UUID format (as defined in the xAPI specification) for all statements it issues.
  • Is this still needed? xAPI spec requires LRS to create ID if one not provided
  • Review Issue - https://github.com/AICC/CMI-5_Spec_Current/issues/625

#3 – (Not Listed in Derived Requirements) Should the LMS be required to follow AU rules for statements (actor, ID, content, etc.)

#4 - 3.0.0.0-1 (d) - The LMS must reject course structure data that contains non-fully qualified IRIs or IRI references in any data element using an IRI value space.

  • Related Testing Requirements
    • 13.2.0.0-1 (d) - The LMS must reject course structure XML that does not conform to the CourseStructure.xsd.
    • 6.1.0.0-3: The LMS MUST support course structures conforming to the XSD schema defined in Section 13.2.
    • 6.1 Course Handling Requirements - The LMS MUST support course structures conforming to the XSD schema defined in Section 14.0
    • Should language be added to specifically indicate that the LMS Must Reject course structures that do not conform to the XSD schema ?

CATAPULT

*More LMS Test Suite Instructions needed (it is LMS implementation specific since LMS tests require continuous integration)

XAPI Profile Related Questions

  • Common guidelines for analytics
  • Using profiles best practices
  • Product differentiation vs. Best practices

Next Meeting

  • Due to the end of year holidays, the group will not meet again until January 7, 2022.
  • Discussion will continue with review of derived testing requirements

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

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