Current work on IMS Tools Interoperability to intgerate  the Icodeon SCORM Player with the SAKAI Learning Platform

We need to find a way to send more contextual data from SAKAI in the launch request, as there are a number of Icodeon Player specific parameters that are required for launch of the Player. I am assuming that Icodeon would need to provide a small XSD to define these parameter names and data types along with the deployment descriptor.

For example, the Icodeon Player will need:

 that specifies a unique identifier for a particular SCORM Package to launch.

There are a number of mandatory and optional launch parameters for the Icodeon Player - full details are here.

Next Steps:

SAKAI to advise Icodeon on adding tool specific parameters to a launch request.

When the SCO has completed a session in the SCORM run time environment (RTE), the SCO calls a Terminate() function on the client side API. In the Icodeon RTE the Terminate() function then invokes a Terminate operation on a remote web service, and sends an XML document that represents the data model state of the SCO to the Terminate operation.

In the IMS TI implementation used in the Icodeon SCORM Player, the XML document that has been sent from the RTE is then routed to the host LMS that supports the IMS TI outcome service. 

The XML document is an instance of the IEEE 1484.11.3 schema for Content Object Communication Data Model - an XML binding of the SCORM CMI data model. Attached is the documentation and XSD for this XML binding (see the Attachments Tab on this page)

In Icodeon's experience, the Java tools for generating an object model from this (complex) schema are problematic - with the Apache AXIS tools set particularly weak. Icodeon used a combination of Apache AXIS and Castor to achieve results. See discussion here on Icodeon Labs. SO be prepared for some issues in generating Java classes from the XSD...

Comments?