Workgroup Charter

Title: SCORM Runtime Workgroup
Author: Jon Gorrono
Revision: r.02
Revision Date: 2004-11-10
Status: draft

Revision Information:

Instructions

This document outlines a charter for proposing an SAKAI Workgroup. Workgroups with formal charters are the primary means through which SAKAI operates. SAKAI recommends that proposed Workgroup charters be discussed with the SAKAI Board member who has Workgroup responsibility (see sakaiproject.org website for contact information). Once completed, this form should be sent to the SAKAI board for review. It will be shared with other Workgroup leaders and the board to discern how it fits with the work of existing Workgroup efforts.

Workgroup title

SCORM Runtime Workgroup
Chair
Jon Gorrono, IET Mediaworks, UC Davis, jgporrono@ucdavis.edu

Problem area

The relatively few extant implementations of SCORM2004 (and earlier version) are minimal, inaccurate, incomplete and/or not scalable.
Educational institutions need ready access to a responsive common-interest community of developers and users in order to develop a
mature implementation. Additionally, the SAKAI Project can benefit from examination and implementation of the content object aggregation,
delivery (e.g., 'Runtime'), and sequencing architecture patterns of SCORM2004.

Charter

This workgroup will develop, as a primary deliverable, an implementation of:

a 'fully-SAKAI-integrated' SCORM2004 Runtime Environment (IEEE 1484.11.1, IEEE 1484.11.2)

and, the SCORM2004 Sequencing/Navigation specification.

Specifically, the minimum target is to meet two SCORM conformance goals: 'LMS RTE 1.3.1' and 'LMS SN 1.3.1', namely:

LMS RTE 1.3.1 (Implemented as a SAKAI Tool)

• be able to launch an Asset, and
• be able to launch a known conformant SCORM 2004 Conformant Sharable Content Object (SCO), and
• provide and expose an API Instance as a Document Object Model (DOM) object that correctly implements all of the API methods, and
• correctly implement support for all SCORM 2004 Run-Time Environment Data Model Elements,
• implement support for all SCORM 2004 Navigation Data Model Elements.

LMS SN 1.3.1 (Implemented as a SAKAI Service)

• correctly implement all of the sequencing behaviors defined by the pseudo-code included in the SCORM Sequencing and Navigation Version 1.3.1, and
• correctly implement support for all SCORM 2004 Navigation Data Model Elements, and
  correctly implement support for Navigation User Interface requirements.

Additional deliverables
multiple client-side 'server-proxy' technology implementations
Major coding and design contributions to other SAKAI workgroup efforts to develop more general sequencing services for SAKAI
Contributions to related authoring tools, content storage,access and aggregation efforts as the use or can benefit from this group's efforts
Administration (UI) of global objectives and other preferences
Basic Reporting of (CMI) DataModel elements
Definition of a database schema, hibernate mappings, and schema-build scripts for SAKAI supported DB's

Post Version 1.0 release deliverables may include examination and proposal for alternative communication mechanisms for SCORM2004 and IEEE 1484.11.2 (API Specification) if at such time the rumored IEEE activity to revise or amend IEEE 1484.11.2 does not materialize. Or, the tool team will incorporate the changes if they do materialize.

Out-of-scope proximate topics:
A generalized (a superset of, or other than, SCORM2004) sequencing service is considered out of scope for this group and will be anticipated to any extent possible.

Content packaging/dis-aggregation will likely be a focal point of Content Managements Services workgroup(s). Work progress will require rudimentary (unpolished) implementations of such services, primarily for QA, and will also be available for the edification of those in the Content Management development efforts.

Workgroup members

Thomas Amsler, UC Davis; Jon Gorrono, UC Davis

Method of participation
The group membership is open. Based on a very informal survey with respect to interest and experience, we expect coding participation from
3-5 institutions: about 5-7 programmers. Interest to participate has been forwarded by UC-Davis, Toronto, UW-Madison, and the Pachyderm Project
(NMC-SF MOMA).

Anticipated Membership Growth
The goals that can be gained from a successful implementation and the impact on the more general SAKAI interests in content storage, delivery, aggregation, and sequencing could be significant. Initially < 20 people, the group may grow significantly or evolve or splinter into others towards the end of public beta rounds.

Milestones and durations

Phase 1: Target Date: 12/01/2005 - ADL Sample RTE code UML documentation, SAKAI code UML documentation, overlap and remainder
analysis, OKI DR (SCORM) example analysis, Requirements Gathering, Seq. Service API Proposal, UI pilot. If we get more than the current commitment from UCD of 1 FTE (across 2 programmers), we might be able to get all that done.

Phase 2: May 2005
Integrate into fixed and evolving specifications for API's (AuthN, AuthZ, Content Services, Sequencing, etc).

Version 1.0 - June 2005
Resources required to fulfill the workgroup's charter
If we get more than the current commitment from UCD of 1 FTE (across 2 programmers), we will not have to reconsider the current ambitious pace of Phase 1.