CMI 5 Working Group Meeting Minutes – July 10th - AICC/CMI-5_Spec_Current GitHub Wiki
cmi5 Working Group Meeting Minutes –July 10th
Attendees
- Bill McDonald (Working Group Leader)
- Florian Tolk (ADL)
- Matty Kahler (Articulate)
- Art Werkenthin (RISC, Inc)
- Henry Ryng (inXSOL)
- Jason Haag (Veracity)
- Mike Hernandez (Design Interactive)
- Christopher Thompson (Medcom, Inc.)
Notes
New moveOnAllowed AU metadata element / Best Practice #17
The group continued to discuss the proposed best practice for adding the moveOnAllowed to the cmi5 course structure.
The group reviewed the proposal from last week to add an AU attribute the moveOnAllowed and some found the proposal counter intuitive since all the possible combinations of moveOn values supported were mapped to discrete values.
An alternative proposal was drafted to add a new moveOnAllowed element that would provide a list of supported moveOn values by the AU.
< xs:element name="moveOnAllowed" >
< xs:complexType >
< xs:sequence >
< 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:sequence >
< /xs:complexType >
< /xs:element >
The group will continue to discuss the different 2 approaches at the next meeting:
-
moveOnAllowed Expressed as Collection
- Pro: Much easier to understand (a simple list of moveOn values supported)
- Con: Inconsistent with other AU Attributes (moveOn is an AU attribute)
-
moveOnAllowed Expressed as Attribute
- Pro: Using a an AU attribute to express moveOnAllowed is consistent (with the moveOn attribute)
- Con: Very Hard to understand/map (and does not necessarily express moveOn Rules)
All Previous cmi5 Meeting Minutes
https://github.com/AICC/CMI-5_Spec_Current/wiki
cmi5 on GitHub: