-
Notifications
You must be signed in to change notification settings - Fork 91
CMI 5 Subgroup Meeting Notes – Jan 26th, 2024
Bill McDonald edited this page Jan 27, 2024
·
2 revisions
cmi5 Subgroup Meeting Notes – Jan 26th, 2024
Pending....
Gitlab Status
Compliance items still pending: CLA’s, IEEE personal and process changes, Verifying “significant contributions”
"Derived Requirements" Review
The group continued its review of "Derived Requirements" (from CATAPULT documentation) to identify areas of the spec that may need revision:
- 11.0.0.0-1 (d) The LMS must reject xAPI Agent Profile requests that do not include the actor as provided by the LMS at AU launch time.
- Agreed
- 11.0.0.0-3 (d1) The LMS must track that the AU has retrieved the learner preferences document.
- LMS must verify that AU has called the xAPI Agent Profile with the LMS provided actor before the AU issues an initialized statement
- 11.0.0.0-3 (d2) The LMS must reject initialized statement received before the learner preferences document has been retrieved.
- Agreed - per 11.0.0.0-3 (d1)
- 11.0.0.0-5 (d) The LMS must reject requests from the AU to set the Agent Profile document that are not JSON, or whose content is not an object, or whose content does not include the two named properties.
- Agreed
- 11.1.0.0-1 (d) The LMS must reject requests from the AU to set the Agent Profile document if the languagePreference value is not a comma separated list of RFC 5646 language tags.
- Agreed
- 13.1.2.0-1 (d) The LMS must reject course structure data that has a block with an "id" value that is duplicated in the course structure.
- Agreed
- 13.1.3.0-1 (d) The LMS must reject course structure data that has an objective with an "id" value that is duplicated in the course structure.
- Agreed
- 13.1.4.0-1 (d) The LMS must reject course structure data that has an AU with an "id" value that is duplicated in the course structure.
- Agreed
- 13.1.4.0-2 (d) The LMS must reject course structure data that an AU with a "url" element attribute value that is not conformant with RFC1738.
- Agreed
- 13.1.5.0-1 (d) The LMS must reject course structure data that does not provide an XML Schema Definition when custom namespaced elements are used.
- Agreed
- 13.1.5.0-2 (d) The LMS must reject course structure XML containing vendor specific metadata that causes the XML to be invalid.
- Agreed
- 13.2.0.0-1 (d) The LMS must reject course structure XML that does not conform to the CourseStructure.xsd.
- (Now in section 14.0)
- Agreed
- 14.0.0.0-1 (d) The LMS must reject course packages that are neither Zip32, Zip64, nor an XML file.
- Agreed
- External reference to PKWARE
- 14.1.0.0-1 (d) The LMS must reject zip files that do not follow the zip file format specified at https://www.pkware.com/support/zip-app-note.
- Agreed
- 14.1.0.0-2 (d) The LMS must reject zip file course packages that do not contain a cmi5.xml file in the root directory.
- Agreed
- 14.1.0.0-3 (d) The LMS must reject zip course packages that do not use relative URL references in the course structure XML for media included in the package.
- Agreed
- (External AU case covered in spec)
- 14.1.0.0-4 (d) The LMS must reject zip course packages that do not use fully qualified URLs for media not included in the package.
- The Spec (now) only deals with the AU entry point in the package, not the dependent media of the AU that may or may not be in the package
- 14.2.0.0-1 (d) The LMS must reject course structure XML files that include non-fully qualified URLs.
- A “standalone” cmi5.xml file (course structure without a ZIP) must have fully qualified URLs