slide1 n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
Presentation for “Learning Networks for Lifelong Competence Development” 29-31 March 2006 PowerPoint Presentation
Download Presentation
Presentation for “Learning Networks for Lifelong Competence Development” 29-31 March 2006

Loading in 2 Seconds...

play fullscreen
1 / 12

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


  • 104 Views
  • Uploaded on

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.

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'Presentation for “Learning Networks for Lifelong Competence Development” 29-31 March 2006' - meadow


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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
presentation for learning networks for lifelong competence development 29 31 march 2006

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

coppercore service integration
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.
the challenge
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
coppercore
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
ccsi solution
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.
ims qtiv2
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
integration requirements
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
coppercore service integration1
CopperCore Service Integration

Orchestration

Provisioning

Extended Service Contract

Basic Service Contract

Original Service Contract

Generic event handling

Service Implementation

conclusions
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