-
Notifications
You must be signed in to change notification settings - Fork 91
CMI 5 Subgroup Meeting Notes – Oct 20th, 2023
Bill McDonald edited this page Oct 29, 2023
·
2 revisions
cmi5 Subgroup Meeting Notes – Oct 20th, 2023
- Andy Johnson
- Bill McDonald
- Brian Miller
- Christopher Thompson
- Florian Tolk
- George Vilches
- Henry Ring
- Jim Taite
- Megan Bohland
- Simon Hsu
- Yifei Dong
The group discussed the following items:
- Add Issues in the New IEEE cmi5 repository (once operational) for all "Derived Requirements" defined in the CATAPULT documentation.
- The the cmi5 specification will need all of the "MUST"s changed to "SHALL"s to meet IEEE requirements
- Re-organize document structure to explicitly itemize requirements (without grouping/flow) in order eliminate duplicating/overlapping requirements language. (see the example: https://xhr.spec.whatwg.org/#the-open()-method )
The group reviewed the following "Derived Requirements" (from CATAPULT documentation):
- 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.
- Moveto course structure requirements section – instead of definitions
- 4.2.0.0-1 (d): The endpoint provided by the LMS passes the ADL LRS conformance test suite.
- Add reference to xAPI Spec
- All xAPI communication must comply with the xAPI specification
- Conformance Test Suite shouldn’t be references
- 4.4.0.0-1 (d): The LMS must reject courses that do not conform to requirements listed in Section 13 or Section 14.
- This is a collection of requirements and should be removed as each individual requirement will be specified in the spec
- 4.4.0.0-2 (d): The LMS must reject course structure data that does not conform to the specification.
- This is a collection of requirements and should be removed as each individual requirement will be specified in the spec
- 6.0.0.0-1 (d): The endpoint provided by the LMS passes the ADL LRS conformance test suite.
- The endpoint provided by the LMS must be xAPI conformant
- 7.1.1.0-1 (d1): The LMS must track that the AU has issued an "Initialized" statement.
- The LMS has to reject statements issued by the AU before the AU issues an initialized statement.
- 7.1.1.0-1 (d2): The LMS must reject attempts by the AU to store statements or void stored statements received before the "Initialized" statement.
- The LMS has to reject statements issued by the AU before the AU issues an initialized statement.
- The LMS has to reject VOIDed statements issued by the AU before the AU issues an initialized statement.
- Void is covered in 7.1.3.0-1 (d1)