IMS Learning Design Runtime Tools Paul Sharples Institute for Educational Cybernetics University of Bolton

IMS Learning Design Runtime A runtime system needs to be able to…  Import an IMS LD Zip file  Read the manifest to ascertain the structure & content  Instantiate the Learning Design template

IMS Learning Design Runtime A runtime system also needs to…  Allow some management of the Learning Designs  Allow users to “play” the Learning Design  Save the “state” of the Learning Design

Open source software tools  CopperCore Learning Design Engine  Service Based Learning Design Player (SLeD)  CopperCore Service Integration (CCSI)  Tools are all “Java” J2EE based. They typically run within a JBoss application server

LD Runtime Components The architecture of the major components

Services in IMS LD Within an IMS Learning Design a user has access to content but also something called “services”. IMS Learning Design specifies a generic set of services Concrete Implementations were not available These generic services are vague These services are not easily extendable

Extending the services Idea for extending LD services taken from the web 2.0 world and specifically widgets/gadgets Widgets and gadgets can be found both on the desktop and on the web in various flavours They usually are small applications comprised of HTML and Javascript Examples include Apple Mac Dashboard widgets, Windows Vista Sidebar gadgets & Google gadgets

Windows Sidebar gadgets

Apple Mac Dashboard Widgets

Extending the services W3C released the draft Widget specification (2007) A Widget Server was implemented using the W3C specification as basis. Architecturally: Separation of concerns Widget server is extendable Widget Server advertises which widgets it can offer

Widget service for runtime

LD Runtime Tools Lets take a look…

What next? Create a new Learning Design Player Utilising CopperCore engine Replacing SLeD Based more on the “widget” look & feel Use Ajax for better User Interface

LD Runtime Tools Contact: Paul Sharples