Dashboard > Web Services and Service Oriented Architecture > 2007 > August > 22 > Contextual Information in a Launch Request
  Web Services and Service Oriented Architecture Log In   View a printable version of the current page.  
  Contextual Information in a Launch Request
Added by Icodeon Customer Support, last edited by Icodeon Customer Support on Aug 22, 2007
Labels: 
(None)

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:

courseID

 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.

I am keeping this "thread" for discussions around the launch service. I have started a new thread for discussion around the outcome service on a new page.

Icodeon have developed a first "go" at a deployment descriptor for the TI Launch service, to include parameters to determine which SCORM package to launch, the UI features and language and so on. At the IMS Redmond meeting these were hard coded in, but now they parameter values are editable in a deployment descriptor.

The deployment descriptor is attached, and has been tested on Sakai 2.4.0.

For further details on the parameters and their values please see the SCORM Player configuration guide here. 

Comments? 

Assuming an out-of-band agreement that would link a SCORM course/module to a course site in the Sakai CLE, the proxy tool consumer, upon loading the deployment descriptor, could leverage Sakai's course management (CM) service to gather up the required course parameters, data types and values required by the producer.  The proxy tool could then provide this information to the producer during the launchRequest via the contextual profile and/or the tool settings.  

August 2007
Sun Mon Tue Wed Thu Fri Sat
      1 2 3 4
5 6 7 8 9 10 11
12 13 14 15 16 17 18
19 20 21 22 23 24 25
26 27 28 29 30 31  

Sending SCORM Tracking Data to a IMS TI Outcome Service
Web Services for SCORM

Powered by Atlassian Confluence, the Enterprise Wiki. (Version: 2.5.2 Build:#807 May 20, 2007) - Bug/feature request - Contact Administrators