LETSI Technical Working Group, April 1, 2008

Attending: Avron Barr, Bill Blackmon, Don Holmes, Frank Polster, Tyde
Richards, Robby Robson, Schawn Thropp, Tom Wason

Proposed Agenda:
1. Roll Call
2. Review/Approve Agenda
3. Review/Approve Minutes from 20080318
4. General LETSI news
5. WG Project Status Update
6. WG infrastructure (wiki, email reflector)
7. Day/Time Next Meeting
8. Adjourn

GENERAL LETSI NEWS

IMS GLC filed a bid protest with the U.S. government related to the formation of LETSI. The details and implications are not fully understood

Polster asked about going forward with SCORM 2004 4th Edition; this is not an issue for this LETSI group. Only ADL can issue a 4th Edition
(or alternative). The working group is about moving things forward with SCORM and competencies, etc

The general plan is to have a Requirements Gathering meeting in September 08. People would submit white papers about the future of
SCORM (requirements, solutions). A panel will review and the good white papers will be presented at the meeting. Afterwards, a strawman
version of SCORM 2.0 will be developed.

There are many meetings coming up:
* IEEE meeting in April 08 - many parts of SCORM are IEEE specs; participation in IEEE LTSC is by individual instead of by national
body, which, given the recent IEEE/ISO partnership agreement may enable more timely projects to be made in
* AICC in Hamburg in June 08 - Tom King is involved in AICC; Eifel is interested in adopting PENS and are meeting in Quebec 5/5/08 for an
interoperability event
* ADL should have a TWG meeting in April or more likely May 08

It was suggested that we have a formal inventory of the other organizations that we can work with.

OASIS may be an opportunity for working together, in one (or more) of their "member sections." For example, OASIS has done extensive work in
web services, and we could leverage their existing work, and perhaps draw in some of the existing members into the SCORM work. OASIS has a
low barrier to entry. Polster, Robson, and Thropp talked about the possibility of layering learning on top of existing work.

WG PROJECT STATUS

The Learning Functionality Framework (LFF) could turn into the technical roadmap -- it's useful for notating the capabilities in
SCORM today, communities in the future, etc.

The next step that must be completed is to determine what we need to capture for all future capabilities (to help with the white papers for
the Sept 08 meeting).

There was discussion about the future of content packaging/aggregation and increased support for learning-related capabilities.

Polster then said that we need to know our dynamic pieces before we identify the technical pieces of packaging and delivery. There was
then discussion that packaging is probably not what the next version of SCORM will require as the new SCORM will need to be more open and
dynamic than any pre-packaged model will allow.

ACTION ITEMS

* for the next call, we should try to get the structural part of theLFF approved
* coordinate with the Teaching WG on the Sept 08;
* call up other spec bodies to share what we're doing -- Barr said we can use our white papers as our entree into those organizations;
perhaps we should work harder on the IT departments, since they have a lot of sway in the DoD; Polster said the eLearning Guild has lots of
people we should talk to, including Steve Wexler