-
Notifications
You must be signed in to change notification settings - Fork 91
CMI 5 Working Group Meeting Minutes – July 24th
cmi5 Working Group Meeting Minutes – July 24th
Attendees
- Bill McDonald (Working Group Leader)
- Andy Johnson (ADL)
- Florian Tolk (ADL)
- David Pesce (Exputo)
- Art Werkenthin (RISC, Inc)
- Henry Ryng (inXSOL)
- Jason Haag (Veracity)
Notes
New moveOnAllowed AU metadata element / Best Practice #17
The group continued to work on moveOnAllowed and drafted the following for Best Practice #17 :
Best Practice #17 – AU should Define supported moveOn Values in the Course structure.
The LMS administrator may change the value of moveOn after course structure import. This is the moveOn value that the LMS passes to the AU in the state document. Since an AU design might not be able to support all possible moveOn values, the ones that can be supported should be documented in the course structure file by adding a moveOnAllowed element to the AU’s element with the following structure (see XSD below):
< xs:element name="moveOnAllowed" >
< xs:complexType >
< xs:all minOccurs="1">
< xs:element name="Completed" maxOccurs="1" minOccurs="0"/>
< xs:element name="Passed" maxOccurs="1" minOccurs="0"/>
< xs:element name="CompletedOrPassed" maxOccurs="1" minOccurs="0"/>
< xs:element name="CompletedAndPassed" maxOccurs="1" minOccurs="0"/>
< xs:element name="NotApplicable" maxOccurs="1" minOccurs="0"/>
< /xs:all >
< /xs:complexType >
< /xs:element >
The element names (above) reflect the moveOn values (as currently defined in the cmi5 specification) supported by the AU. The XSD for cmi5.xml is extensible and the addition of the “moveOnAllowed” element to the “au” element does not invalidate the course structure. This will not be a breaking change and can be implemented now without consequence. By documenting the supported moveOn values in this manner the LMS may be able to notify LMS admins if they change moveOn values incorrectly for a given AU. (Or a human could read the cmi5.xml and understand what moveOn values are valid for a given AU)
All Previous cmi5 Meeting Minutes
https://github.com/AICC/CMI-5_Spec_Current/wiki
cmi5 on GitHub: