October 15 CMI Harmonization Meeting
Tyde Richards
Date: Friday, October 15
Time: 8am US Pacific; 11am US Eastern; 4pm UK
Duration: 1 hour
Proposed Agenda
- Approval Agenda/Minutes last meeting
- IEEE LTSC WG11 updates
- CMI Core updates
- Focus Topic: Planning discussion/dependencies of ADL/AICC/IEEE LTSC/LETSI activities related to CMI harmonization and the 1484.11.1 data model revision
Please send comments on the agenda or draft minutes from last meeting (appended below) to: tyderi...@gmail.com
Dial-in:
Skype phone: +9900827049304412
Conventional phone: local number + access code 9304412
US 201-793-9022
United Kingdom 0870 0990 931
Visuals:
https://my.dimdim.com/letsi
Draft Minutes: October 8 CMI Harmonization Meeting
Attending
Avron Barr
Tiajuana Benson-Bond
Ethan Estes
Don Holmes
Scott Lewis
Bill McDonald
Frank Polster
Jonathan Poltrack
Tyde Richards (convener)
Chris Sawwa
Kent Weeks
Agenda
- IEEE LTSC WG11 Updates
- CMI Core Updates
- Focus Topic: Extension Mechanism
- Infrastructure for collaboration
- IEEE LTSC WG11
Discussion with the IEEE on IP/access to the 1484 standards is still on hold due to IEEE staff travel.
The IEEE LTSC Sponsor Executive Committee approved extending the joint study group (this activity) six months.
A project authorization request (PAR) for a revision of the 1484.11.1 data model standard was submitted to the IEEE for approval.
There was discussion about getting more international participation in the activity. Tyde will contact some SC36 participants who historically have been interested. Jono will investigate the relevance of the ADL Partnership Labs.
There was brief discussion about the relationship of the data model to accessibility, an issue which has been raised in SC36 several times with respect to SCORM. This may be out of scope, but a statement clarifying the relationship will become desirable if the 1484.11.1 standard is eventually progressed through ISO-IEC.
- Core CMI Update
A deadline of one month was suggested for completing a ADL/AICC recommendation on a data model core. This seemed reasonable and Jono (ADL) will coordinate with Ed Cohen (AICC) to discuss.
There was discussion about creating a software adaptor to mediate, historically, between AICC CMI and ADL SCORM versions of the data model, and, prospectively, with the revision of the 1484.11.1 standard plus an extension mechanism. This is a topic of interest and future discussion.
- Focus Topic: Extension Mechanism
There was discussion about future support for an extension mechanism with the 1484.11.1 data model revision. Three issues were discussed. First, should the extension mechanism be defined in the underlying data model, or in bindings (XML, ECMAScript) of the data model? Second, should the extension mechanism use structured extensions (each extension has defined parts) or unstructured extension (a collective bucket)? Third, what is the relationship of the extension mechanism to conformance testing?
The participants on the call concluded that the extension mechanism should be part of the underlying data model, that a structured approach should be taken at least to the extent of giving each extension an identifier, and that this approach would align with conformance testing software that could be adapted by scripts to the requirements of different communities of practice.
- Infrastructure for collaboration
We agreed to continue using the CMI Harmonization reflector that ADL set up for discussion and meeting announcements (cmi-harm...@adlnet.gov).
Parties wishing to join the collaboration should go the associated goggle site and register to join:
https://sites.google.com/a/adlnet.gov/scorm-harmonization/home