Attending
Jill Abbott
Avron Barr
Frank Polster
Fanny Klett
Tyde Richards (convener)
Robby Robson
Schawn Thropp
Approvals
Agenda Approved
Minutes last meeting approved
General LETSI News
Tyde and Avron gave a report on developments related to Core SCORM at the ADL Implementation Fest which occurred the previous week. These and related telecon discussion are summarized under the Core SCORM Project section.
There was discussion of several events in the September/October timeframe during which discussion of LETSI and the future of SCORM will occur.
- September SC36 Plenary meeting in Toronto
- September AICC in St. Louis
- October ADL TWG meeting in Alexandria
- October Masie Conference in Orlando
- October ADL Workforce Colab eLearning Summit in Memphis
Each of these events will have opportunites and challenges for moving forward the LETSI technical agenda.
For the SC36 meeting, Tyde agreed to contact the known attendees with an interest in LETSI to see about arranging a side meeting. These include Avron, Fanny, Robby, Mokhtar, Kiyoshi, possibly Mike Collett. If you plan to attend and know other interested parties please inform Tyde.
The AICC meeting will have a half day workshop in which ADL and the AICC will discuss the possibility of collaborating on future SCORM version that both will adopt (referred to as [SCORM Next] below).
The ADL TWG meeting represents the SCORM implementer and vendor community whose concerns with issues such as compatibility and migration need to be addressed. It may offer an opportunity for side discussions with SIFA and Medbiquitous to better understand their community of practice requirements.
The Sunday preceeding the Masie Conference is an opportunity for the SEC and WGs to meet. Details of who will meet for what purpose are still under discussion. Tyde suggested that the Tech WG consider meeting with community of practice representatives and focus on requirements gathering.
The Memphis eLearning Summit will focus on tools, such as content authoring tools.
Mention was made of a possible resolution on the horizon of issues between ADL and IMS related to the use of IMS Specifications in SCORM 2004 3rd Edition
There was discussion of recent and favorable LETSI SEC review of the IEEE ISTO as a possible host organization for LETSI during its formative stage.
WG Infrastructure
No major problems were identified with the wiki or email reflector. A request was made that comments posted to the wiki be listed in reverse chronological order and some investigation is needed to determine if this is possible.
There was discussion of the importance of using the wiki to enable participation by parties who cannot attend the WG telecons. For a global audience, telecons by themselves are not generating the level of participation we hope to see. The Web appears to offer the best hope of effective collaboration.
WG Charter Project
The draft charter and posted comments were discussed. Schawn drafted a proposed revision to the wiki during the meeting. Comments are requested for the next WG meeting where the draft will hopefully be approved by the WG for submission to the SEC for approval.
Core SCORM Project
From the Implementation Fest report and posts to the Core SCORM Project section of the wiki it is clear that people are confused by the different names for future SCORM versions.
One distinction that needs to be clarified is the difference between a version of SCORM based on de jure standards and a future SCORM release that ADL proposes to develiver to LETSI in the 2008-2009 timeframe that is intended to serve the requirements of different communities of practice such as the AICC, Medbiqutious, SIFA.
Core SCORM was the working name a version of SCORM based on de jure standards. There was concern that the word "Core" carries the wrong meaning and should be changed.
There was WG agreement to rename the Core SCORM Project to the SCORM Technical Roadmap Project. Within this project two versions of SCORM will be discussed with the names in brackets to indicate that they are provisional and may be changed.
Robby suggested that at this stage longer, more explict names are fine.
Frank requested that we clarify what is in scope and out of scope for the project.
[de jure SCORM] is the working name for an "internation standard" that is the basis for future versions of SCORM after SCORM 2004 3rd Edition. ADL has a committment to a standards-based version of SCORM and to an approach that allows this version to be extended and adapted to meet the requirements of diverse communities of practice.
[SCORM Next] is the working name for what will minimally be the ADL community of practice adaptation of [de jure SCORM]. In defining [SCORM Next], ADL hopes to collaborate with multiple communities of practice, such as Medbiquitous and SIFA, so that [SCORM Next] is in fact adopted by multiple communities of practice.
There was brief discussion of the possible future disposition of the IMS CP and IMS SS specifications used in SCORM 2004 3rd Edition. One issue is the plan for [de jure SCORM] to require de jure standards, which these specifications currently are not. Another issue is that the current IMS relationship is with ADL, and a relationship would need to be established with LETSI as the future steward of these SCORM versions.
There was discussion of the need for a revised version of the "four box" model to assist communities of practice in coordinating their actions and in establishing a common direction. Note: this is another proposed WG project which we have not yet had time to initiate.
CoP Requirements Project
We discussed the need to identify communities of practice to help determine the requirements for [SCORM Next]. Medbiqutious and SIFA volunteered to assist. Several organizations, such as the AICC, are candidate prospects. We discussed the notion of communities of practice extending beyond formal organizations to cover particular pedagogic, linguistic, and technical concerns. Frank indicated an interest in simulation and gaming, and provided a pointer to current discussion on the adlcommunity.net site. The MIT OKI service architecture was mentioned as another possible technical community of practice that might be worth approaching.
Day/Time Next Meeting
Tuesday, September 18 12:00 UTC
