...
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
...
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
...
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.