07 distance learning standards-common cartridge

Distance Learning Standards –

Common Cartridge

Timothy K. Shih

Outline

• The Overview of Common Cartridge• The Architecture & Run-Time Model• The Content Resources• The Authorization Service• QTI in Common Cartridge• Learning Tools Interoperability• Supporters of IMS Common Cartridge• Learning Tools Interoperability

- Existing Example –• The Future of IMS Common Cartridge

THE OVERVIEW OF COMMON CARTRIDGE

The Overview of Common Cartridge

• Leading providers of digital content products, learning systems, and services will be introducing Common Cartridge compatible products in the coming year

• Support from 35 education industry leaders, including– Publishing Industry: Digital Spirit, Elsevier, GTCO Calcomp,

Harcourt, Houghton Mifflin Company, Lason, LearningMate, McGraw-Hill, Pearson, Thomson

– Learning Platforms: ANGEL, Blackboard, Desire2Learn, eCollege, Giunti, HarvestRoad, Horizon Wimba, Moodle, Sakai, Tribal, uCompass

• Compatible products as early as Spring ‘07– Pearson, McGraw-Hill, ANGEL, Sakai

• A digital learning interoperability standard consisting of a suite of four interoperability specifications (formats of data exchange between cooperating software applications)

– Packaging of digital content (Content Packaging)– Question and test formats (QTI)– Metadata (tagging of content with descriptive attributes) (LOM)– Launch and data exchange with standalone learning tools -

such as adaptive tutors, assessment systems, etc. (Tools Interoperability etc)

The Overview of Common Cartridge cont

Common Cartridge specification

• Profile Based Document Draft v1.0 (19 March 2007)• The imscc_profv1p0cmdn.pdf includes the following:

– IEEE LOM v1.0– IMS Content Packaging v1.1.4– IMS Question & Test Interoperability v1.2.1– IMS Common Cartridge Authorization Web Service v1.0– IMS Tools Interoperability Guidelines v1.0– SCORM 1.2/2004

Common Cartridge Features

• IMS Common Cartridge– SCORM 1.2/2004 and IMS QTI v1.2.1 are embraced– A new resource type like discussion forum– Included the question bank which offering tutors additional

questions to those contained within the pre-configured assessments, which they can configure around the core material

• IMS Authorization Web Service v1.0– Optional authorization to protect either the whole cartridge, or

select cartridge resources

• IMS Tools Interoperability Guidelines v1.0 – Learner access to remotely hosted, third-party two-based

applications

• Likely to become the most widely supported educational digital content standard ever

• Shaping and support by the educational publishers • Collaboration between open source and commercial

communities• Potential to reduce the lock-in that many CMS/LMS

users fear• Leadership of the higher education community in

learning tech standards

Common Cartridge Features

• Meta-data is only mandated at the cartridge level• Inter-package links are not supported• Common Cartridge meta-data only uses the 15

elements from DCM v1.1(Simple DC)• Assessments have been simplified to the 6 commonly

used QTI question types1. Multiple choices(single response)

2. Multiple choices(multiple response)

3. True/false

4. Essay

5. Simple fill in the blank

6. pattern match

Common Cartridge Simplification

• Cartridge support for Authorization data• Add the resource type like Discussion Forum• Included the Tools interoperability descriptor

– For user redirection to third-party services

Common Cartridge Enrich Items

THE ARCHITECTURE & RUN-TIME MODEL

Common Cartridge Architecture

LMS

LMSContent Mgt/RepositoryImport

Function

Runtime

Ass

essm

ent

Too

ls I

nter

opIn

terf

ace

Dis

cuss

ion

For

um

Aut

hori

zati

on

SCO

RM

E

ngin

e

XM

LR

ende

ringCommon

Cartridge

CommonCartridge

AuthorizationService

Web / Enterprise Learning

Application

Learner

Learning content distribution format containing – digital content– description (metadata)– assessment– external tool invocation (forum, virtual world, …)– authorization service invocation

• Functional Overview

Common Cartridge Run-Time-Model

THE CONTENT RESOURCES

Common Cartridge File Structure

Cartridge

learningObjectFolder1

imsmanifest.xml

learning object 1 resources

learning object 1 web content

cartridge web content

learningObjectFolderN

learning object N resources

learning object N web content

.

.

.

filefolder

Sh

ared

Con

ten

t

Item Folder

Resource – Web Content

Resource – Web Link

Resource - Discussion Topic

Resource- SCORM Package (.zip)

Resource – Tools Interoperability Deployment Descriptor

Resource - Assessment

Resource Question-bank

Intra-Package Reference

IMS CC Meta-data

Of Type

IMS CC Package Metadata

Common Cartridge Interchange

Embedded paths should also include tokens to help import tools translate paths<img src=“$IMS-CC-FILEBASE$/images/icon.png”>

Common Cartridge Constraints

Common Cartridge Content Package Structures

• The Example of Content Package Structure (1)


• The Example of Content Package Structure (2)


• Metadata of Common Cartridge followed– IEEE LOM strict specification v1.0

• Describe the range of a mapping from the core element of the Dublin Core specification v1.1

<metadata>

<schema>IMS Common Cartridge</schema>

<schemaversion>1.0.0</schemaversion>

…metadata according to Common Cartridge profile of IEEE LOM …

</metadata>

Common Cartridge Metadata

• Mapping of Dublin Core elements to LOM Metadata elements

Common Cartridge Metadata

THE AUTHORIZATION SERVICE

• The Authorization can be applied to protect the whole cartridge or selected content.

• Each Common Cartridge that implements the authorization service needs the following information– Cartridge ID– URL to Web Service for authorization

Common Cartridge Authorization

• The Authorization model supports the requiring authorization on:

– Cartridge import– Cartridge usage– Usage of specific resources in the cartridge



• The Description Profile of Authorization

<manifest> <metadata /> <organization /> <resources /> <cc: authorizations access=“cartridge import=“false” xmlns: cc=“http://www.imsglobal.org/xsd/imsccauth_v1p0” xmlns: xsi=“http://www.w3.org/2001/XMLSchema-instance” xsi: schemaLocation=“http://www.imsglobal.org/xsd/imsccauth_v1p0 imsccauth_v1p0.xsd” <cc: authorization> <cartridgeId>12345</cartridge> <webservice>http://publisher.com/authme</webservice> </cc: authorization> </cc: authorizations></manifest>

Common Cartridge Communication Flow

LMS = Learning Management SystemWS = Cartridge Protection Web Service

LMS<Validation><ID>Cartridge ID</ID><URL>The LMS’s URL</URL>

</Validation>WS <Validation>

<Show>License Agreement</Show><Prompt> <Message>Please enter key: </Message> <Name>Key</Name>

<Type>Text</Type></Prompt>

</Validation>LMS<Validation>

<ID>Cartridge ID</ID><URL>The LMS’s URL</URL><Key>A Key</Key>

</Validation>

If Key is ValidWS <Validation> <Release>

<Key>The Key passed by LMS</Key><Exp>Expiration Date</Exp>

</Release> </Validation>

If Key is InvalidWS <Validation> <Invalid>

<Key>The Key</Key><Message>A Message</Message>

</Invalid> </Validation>

QTI IN COMMON CARTRIDGE

• A Common Cartridge may contain either/both of two Learning Object Resource types that are based on the CC QTI Profile– Assessments– Question Banks

• Assessments – Represent an ordered question set and may include optional

attributes that apply to the set as a whole. (Using <assessment>)

• Question Banks – Represent unordered sets of questions with no associated

attributes applying to the set as a whole. (using <objectbank>)

Common Cartridge QTI

• <questestinterop> is the root element for all CC QTI documents.

• The $IMS-CC-FILEBASE$ token may be used in any portion of questions, answers or feedback. – It is intended to help identify paths that reference media files

that are required by the assessment and are included in the common cartridge.

Common Cartridge QTI

• Assessments are represented with a single <assessment> element with :– must contain exactly one <section> element

• required “ident” and “title” attributes • optional “language” attribute. • contains one or more <item> elements only

– contain an optional <presentation_material> element– contain an optional <qtimetadatafield> element

• Object banks are represented as a single <objectbank> element which can contain one or more <item> elements only

Common Cartridge Assessments vs Object Banks

• A <qtimetadata> element can be present where CC specific meta-data elements are allowed within <qtimetadatafield>

Common Cartridge QTI Metadata

• <item> elements represent individual questions in assessments or object banks – There is a required “ident” attribute and an optional “title”

attribute which can be used when providing editors with question lists for selection or editing.

Common Cartridge QTI Metadata

• An <itemmetadata> element can contain a <qtimetadata> element where CC specific meta-data elements are allowed within <qtimetadatafield> structures

Common CartridgeQTI Metadata (Item Metadata)

• The <presentation> element contains elements for representing the question text and responses as presented to the student.– A <material><mattext> structure directly inside the <presentation>

element is used for the question text.– Multiple_choice, multiple_response, and true_false questions use a

<response_lid> element to contain the individual answers. – There is a required “ident” attribute which should be of the form

response_# to make processing easier, and an “rcardinality” attribute which should be set to “Single” for multiple_choice and true_false questions and “Multiple” for multiple_response questions.

– The <response_lid> element contains a single <render_choice> element with a “shuffle” (Yes/No) attribute to indicate whether or not scrambling of answer choices is allowed.

– The <render_choice> element contains one or more <response_label> elements with a required “ident” attribute.

– The <response_label> elements contain <material><mattext> structures holding the text of the individual answers.

– Response.rshuffle is not supported here.

Common CartridgeQTI Metadata (Presentation part)

• <resprocessing> is a direct child of the <item> element and is used to indicate correct answers and response scoring.– It should include an <outcomes><decvar> structure that sets

varname="SCORE"– <respcondition> elements are used to set the value of “SCORE”

appropriately for each response, and to identify any <itemfeedback> – A <respcondition continue="Yes"> can be used for general feedback

to be provided unconditionally– A <setvar action="Set" varname="SCORE"> element is used inside a

<respcondition> element to set the score. With simple multiple choice only one correct answer is allowed and it should set SCORE to 100. All other answers should set SCORE to 0

– The <conditionvar> element is used to establish the conditions for each scoring possibility

– There should be a <displayfeedback> element contained within the <respcondition> element for feedback appropriate to the response.

– This can be specific answer level feedback and/or feedback for all correct/incorrect answers, as determined by the conditionvar case

Common CartridgeQTI Metadata (Resprocessing part)

• <itemfeedback> elements with required “ident” attribute, corresponding to any references placed in <respcondition> elements, are used to define the feedback for each case. – Feedback text is contained in <material><mattext> structures– Hints can be represented as follows:

– Essay questions can indicate sample answers as follows:

Common CartridgeQTI Metadata (Item Feedback part)

• The initial release of the Common Cartridge will only support one role of assessment which maps to the IMS concept of ‘Examination’ (as defined by the QTI meta-data attribute ‘qmd_assessmenttype’).

• An assessment must contain a single section which contains all questions delivered by the assessment.

• Multiple sections and references to questions in an object bank are not supported.

• An assessment does support the use of a number of meta-data attributes which can carry additional delivery

Common Cartridge Assessment Data Model

Common Cartridge Item Data Model

Item.Attr ItemFeedback

ItemMetadata Presentation RespProcessing

Item

• Material– Material– Flow– FlowMaterial– Text– Image– Application– Applet– Audio– Video

Common Cartridge Material Data Model

• The Common Cartridge supports profiles of the following question types

– Single Choice (Single Response)– Multiple Choice (Multiple Response)– True/False– Essay– Simple Fill in the Blank

• single response box with single correct answer that is processed as an exact match

– Pattern Match• single response box with multiple potential answers that support

exact match, containment matching and regular expression matching

Common CartridgeQuestions Types Supported

• The profiles for each of these question types describe how they support:– feedback– hints– sample solutions– relative scoring

• In addition, questions support a number of meta-data attributes which describe:– a suggested weighting for the question in the assessment– a category for the question.

• Instances of these questions may be included in an assessment or a question bank.

Common CartridgeQuestions Types Supported

Common Cartridge Question Bank Data Model

LEARNING TOOLS INTEROPERABILITY

• How to help the developer to construct the specialized helpful tools in order to extend LMS functionalities and its capabilities?

– Tools Interoperability : To provide the reusable mechanism for integrating third-party tools with core LMS platforms

• The key enabling technologies is HTTP, SOAP, XML, WSDL, WS-Security.

Learning Tools InteroperabilityIntroduction

LMSLMSThe core LTI use case is that we can augment the tools included in an LMS with externally provided tools.


LMS

LMSTOOL

orContent

TOOLor

Content

LMS

LMS

LMS

LMS

….

LTI also enables large-scale of provisioning of features or content across multiple LMS Systems


LMS

LMS

ContentContent

CommonCartridge

LMS

LMS

When LTI is combined with the IMS Common Cartridge, publishers can distribute cartridges containing active, authenticated links back centrally hosted content.


Advanced:LTI also allows tools from a learning management system from one vendor to be used in a learning management system from another vendor. An example of this approach is the BlackBoard Connect project which integrates Sakai and Moodle (coming) functionality into BlackBoard.

LMS

LMS

LMS

LMS


ContextContextContextContext

ContextContext

Ultimately the “location” or “source” of a tool or content becomes less and less important.


Learning Tools InteroperabilityArchitecture

Proxy Tool Packages

Learning Management System

Tool Interoperability Runtime

Deployment Service

Configuration ServiceLaunch Service

Proxy Tool

Web Service

Learning Tool Container

Tool 1



Tool 2


Client Tier

Proxy Tool 1 Proxy Tool 2• Proxy tool – a proxy or a façade in the LMS.– The architecture defines a standard mechanism for packaging a

Proxy Tool for deployment to an LMS• Learning Tools Interoperability Runtime (LTIR)

– Is a collection of services– Allow Proxy Tools to be deployed, configured and launched– Include distinct services for managing the deployment, configuration,

launch of Proxy Tools from

• Tools Interoperability Runtime (TIR) services include:– Deployment Service

• Interpret and load the Proxy Tool definition into the host TIR via its deployment descriptor

– Configuration Service• Manage the runtime settings of the Proxy Tool

– Launch Service– Outcome Service– Security Management– Session Management

Learning Tools InteroperabilityInteroperability Run-Time

• Describes a “Proxy Tool” for a Learning Management System

• How the tool is installed and registered in the LMS• Tool lifecycle interactions• How the Tool is launched from the LMS including

passing roster information• Run-Time Services allowing the tool to read, write, and

exchange information with the LMS

Learning Tools Interoperability Proxy Tool

Learning Tools InteroperabilityArchitecture

Proxy Tool Packages

Learning Management System


Deployment Service

Configuration ServiceLaunch Service

Proxy Tool

Web Service


Tool 1



Tool 2


Client Tier

Proxy Tool 1 Proxy Tool 2

• Proxy Tools includes the following settings:• Core Settings• Contextual Settings• Outcome Settings• Security Settings• Tool Settings

Learning Tools Interoperability Component Interaction

• Adopts many patterns from the approach FaceBook uses for tool integration

• Architecturally aligned with the BlackBoard Proxy Tool in BlackBoard 9.0

Learning Tools InteroperabilityTechnical Inspiration

Learning Tools Interoperability LMS Integrations

• Content Integration– McGraw-Hill Katana– Pearson TPI

• LMS Integration– Angel– Sakai– Moodle– Microsoft QuickLMS

• Pearson / Angel


• McGraw-Hill / Microsoft


• McGraw-Hill / Sakai


• Moodle


SUPPORTERS OF IMS COMMON CARTRIDGE

• IMS GLC, with over 85 member and subscriber organizations, is the world’s leading provider of learning technology interoperability standards, for over 11 years

• IMS GLC has developed, ratified, evolves, and maintains 20 learning technology standards implemented widely around the globe, including standards for digital content, repositories, resource lists, learning tools, ePortfolio, learner information, educational objectives, metadata, assessment, learning design, and accessibility, including several specifications underlying SCORM

• Common Cartridge has been developed in a community standards process with the involvement and commitment of over 35 IMS GLC member and subscriber organizations

• See the members of IMS GLC at: http://www.imsglobal.org/

Supporters of IMS Common CartridgeIntroduction

http://www.imsglobal.org/

InstitutionalLeaders inLearning

Publishing,Assessment,

and Repository

LearningSoftware

and Systems

Enterprise Software,Systems, and

Services

LEARNING TOOLS INTEROPERABILITY- EXISTING EXAMPLES -

Icodeon Common Cartridge Platform

http://ccplatform.blogspot.com

http://ccplatform.blogspot.com/

Icodeon Ltd, Cambridge, UK

SCORM Player Common Cartridge Player

The Player web applications enable vendors of e-learning systems to rapidly add the full feature set of e-learning standards.

SCORM Player Common Cartridge Player

• What can I do with the software?

• How do I use the software?

• Where can I get help & support?

• Extras

(Easy) … (Expert)

Icodeon SCORM Player

Icodeon Common Cartridge Player

• What can I do with the software?

• How do I use the software?

• Where can I get help & support?

• Icodeon Extras

(Easy) … (Expert)

Common Cartridge Player

What can I do with the system?

• Import cartridge

• Embed cartridge link

• Make cartridge with HTML web content

• + web link

• + discussion (text only)

• + discussion (HTML, images)

• + discussion (HTML, images, attachments)

• + roles (teacher/learner)

• + authorization

• + QTI (text)

• + QTI (HTML, images)

• + Learning Tools Interoperability

Import Cartridge

Step 1: You need a cartridge zip file. If you do not want to build your own cartridge, you can download one from Learning Space (http://openlearn.open.ac.uk/)

Import Cartridge

Step 2: Upload the cartridge to Icodeon Common Cartridge Platform

(http://www.common-cartridge.com)

Import Cartridge

Step 3: Like You Tube…

Import Cartridge

Step 4: Add URL or Embed tags to blog, wiki, HTML page etc

Import Cartridge

Step 5: Launch Common Cartridge Player

Import Cartridge

Summary

Step 1: Get cartridge

Step 2: Upload

Step 3: Like You Tube…

Step 4: Add URL or embed tags to blog etc

Step 5: Launch Player

Common Cartridge Player

What can I do with the system?

• Import cartridge

• Embed cartridge link

• Make cartridge with HTML web content

• + web link

• + discussion (text only)

• + discussion (HTML, images)

• + discussion (HTML, images, attachments)

• + roles (teacher/learner)

• + authorization

• + QTI (text)

• + QTI (HTML, images)

• + Learning Tools Interoperability

Free the Content: Example 1

QTI Assessment in a Common Cartridge

QTI Assessment:

- an ordered sequence of different question types with feedback and scoring

Common Cartridge Web Services Platform

Apps, Blogs, Wikis, Widgets, Feeds. Mash-Ups…

+ LMS ?

Icodeon Common Cartridge Web Services Platform

Platform URL Language

Platform URL Language enables simple HTTP requests to be made to the web services platform:

http://{host-name}/cartridges/{cartridge-name}/...

URL Language: Example 1

Thumbnail Views of Cartridge Content

http://{host-name}/cartridges/{cartridge-name}/items/{item-name}/resource.jpg

http://{host-name}/cartridges/{cartridge-name}/items/~first/resource.gif

http://{host-name}/cartridges/{cartridge-name}/items/~last/resource.png


QTI Assessment

http://{host-name}/cartridges/{cartridge-name}/items/{item-name}/assessment.js


Cartridge Content Menus

http://{host-name}/cartridges/{cartridge-name}/items/~root.html (.xml)

http://{host-name}/cartridges/{cartridge-name}/items/~root.json

http://{host-name}/cartridges/{cartridge-name}/items/~root.atom

THE FUTURE OF IMS COMMON CARTRIDGE

• Adoption of specification revisions– Question & Test Interoperability v2.1– Learning Tools Interoperability v2.0– Candidates for extending functionality– Accessibility – Lesson Plans (Learning Design?)– Common Cartridge repositories– High-stakes assessment (security)– Custom publishing

Common Cartridge Future extension

07 distance learning standards-common cartridge

Education