1 / 12

Presentation for “Learning Networks for Lifelong Competence Development” 29-31 March 2006

Integrating IMS LD and IMS QTIv2 using CopperCore Service Integration Hubert Vogten, Harrie Martens, Rob Nadolski, Colin Tattersall, Peter van Rosmalen, Rob Koper. Presentation for “Learning Networks for Lifelong Competence Development” 29-31 March 2006. CopperCore Service Integration.

meadow
Download Presentation

Presentation for “Learning Networks for Lifelong Competence Development” 29-31 March 2006

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Integrating IMS LD and IMS QTIv2 using CopperCore Service IntegrationHubert Vogten, Harrie Martens, Rob Nadolski, Colin Tattersall, Peter van Rosmalen, Rob Koper Presentation for “Learning Networks for Lifelong Competence Development” 29-31 March 2006

  2. CopperCore Service Integration • Funded by JISC ELF toolkit strand • Joint development of OUNL and OUUK based on earlier work done in the SLeD project • Goal: to provide a framework for integrating Learning Services with CopperCore, an IMS Learning Design service.

  3. The Challenge • IMS LD Specifies • activities, resources, services and a learning flow through an XML binding • declarative incorporates learning services, like synchronous and asynchronous services • described integration with other IMS specs on a XML level, like IMS QTI • however does not describe in detail the runtime integration of these services

  4. CopperCore • Is intended to be used as runtime service which should be included in the context of a learning environment. • Therefore has no GUI. • Therefore does not implement any of the services mentioned directly

  5. CCSI solution • Glue between the services • The CCSI will be presented by describing the integration of two services : • CopperCore for IMS LD specification IMS QTIv2 the APIS as outcome of the APIS project.

  6. IMS QTIv2 • New model of QTI items • includes “Interoperability Integration Guide” describing the synchronisation of QTI outcomes with IMS LD • practical solution based on: • property name matching • resource id matching • data type matching

  7. Integration requirements • Architecture should be non intrusive: • implementing services should not have to be modified. • Implementation independent • multiple service implementations may exist. Services should be interchangeable. • Should allow any extended functionality of service • Existing clients should be able to benefit with minimal changes

  8. CopperCore Service Integration Orchestration Provisioning Extended Service Contract Basic Service Contract Original Service Contract Generic event handling Service Implementation

  9. Demo

  10. Conclusions • The presented CCSI architecture: • can handle the integration of LD and QTI • minimal/none intrusion on existing service implementations. Only adapter have to be created dealing with cross service concerns • allows services to be interchanged • allows richness of service to be exploited • requires minimal changes on existing clients

More Related