Packaging update and requirements

Overview OAI Object Re-use and Exchange (ORE)‏ What it is Where it is at Content Packaging 1.2 What it is Where it might go: split and standardisation IEEE RAMLET What it is Where it is going: implementation strategies Packaging service What it could be

OAI Object Re-use and Exchange (ORE)‏

What it is

Where it is at

Content Packaging 1.2

What it is

Where it might go: split and standardisation

IEEE RAMLET

What it is

Where it is going: implementation strategies

Packaging service

What it could be

OAI Object Re-use and Exchange From the digital repository world (compare OAI PMH)‏ Consists of: Abstract data model Vocabulary Atom profile Meant for the exchange of web resources Alpha out now, beta by March 3 UK ORE information day April 4, Southampton

From the digital repository world (compare OAI PMH)‏

Consists of:

Abstract data model

Vocabulary

Atom profile

Meant for the exchange of web resources

Alpha out now, beta by March 3

UK ORE information day April 4, Southampton

ORE Datamodel

What is new in IMS Content Packaging 1.2 General housekeeping: Metadata element and other fixes Resource vocabulary Organization vocabulary Completely new documentation set New functionality: New element to indicate alternative resources with different accessibility characteristics New element to include remote parts of remote packages

General housekeeping:

Metadata element and other fixes

Resource vocabulary

Organization vocabulary

Completely new documentation set

New functionality:

New element to indicate alternative resources with different accessibility characteristics

New element to include remote parts of remote packages

Resource & Organization vocabularies Resource used to be just ‘webcontent’ and various IMS specific types defined elsewhere (QTI items etc.)‏ now is an extensible vocabulary in a VDEX file can be extended by anyone Organization used to be just ‘hierarchical’ extensible (e.g. use TopicMaps)‏

Resource

used to be just ‘webcontent’ and various IMS specific types defined elsewhere (QTI items etc.)‏

now is an extensible vocabulary in a VDEX file

can be extended by anyone

Organization

used to be just ‘hierarchical’

extensible (e.g. use TopicMaps)‏

Providing alternative resources with different accessibility characteristics Variant resource Variant

Providing alternative resources with different accessibility characteristics

What is new in IMS Content Packaging 1.2 Ipointer:

Ipointer:

Where CP 1.2 is at Public draft 1 was out IMS internal draft 2 documentation has been out since February last year To be made public after testing and implementation by IMS members more implementation test profiles: one lax and abstract, one production and strict

Public draft 1 was out

IMS internal draft 2 documentation has been out since February last year

To be made public after testing and implementation by IMS members

more implementation

test profiles: one lax and abstract, one production and strict

Where CP could go There have been no CP 1.2 implementations, so: Possibility 1: mothball it until there is interest Delays IMS QTI 2.1 No clean and clear CP documentation for implementors Possibility 2: spin the new functions out in a new speclet Ipointer and accessibility element live in their own namespace anyway Clear road for intended ISO SC 36 standardisation plan

There have been no CP 1.2 implementations, so:

Possibility 1: mothball it until there is interest

Delays IMS QTI 2.1

No clean and clear CP documentation for implementors

Possibility 2: spin the new functions out in a new speclet

Ipointer and accessibility element live in their own namespace anyway

Clear road for intended ISO SC 36 standardisation plan

IEEE RAMLET; what it is RAMLET MPEG 21 DID Atom METS IMS CP Atom mapping METS mapping IMS CP mapping MPEG 21 DID mapping

Where RAMLET is at Use case document out METS, IMS Content Packaging, IETF Atom and MPEG 21 DID mapping complete Therefore: core ontology pretty stable Work on human readable description (scope notes) almost done

Use case document out

METS, IMS Content Packaging, IETF Atom and MPEG 21 DID mapping complete

Therefore: core ontology pretty stable

Work on human readable description (scope notes) almost done

Where RAMLET is heading One library archive project in application One project to chart implementation options: Dedicated library a la universal feed parser Traditional data warehousing Coordinated set of XSLTs Triple store / ontological knowledgebase etc. Applicable to Question and Test formats?

One library archive project in application

One project to chart implementation options:

Dedicated library a la universal feed parser

Traditional data warehousing

Coordinated set of XSLTs

Triple store / ontological knowledgebase

etc.

Applicable to Question and Test formats?

Package transcoding service; the issue Many IMS CP derivatives: SCORM 1.2 SCORM 2004 CP 1.1.2/3/4 Common Cartridge 1.0 / K12 /... NLN etc. Many proprietary ... flavours: Blackboard WebCT etc.

Many IMS CP derivatives:

SCORM 1.2

SCORM 2004

CP 1.1.2/3/4

Common Cartridge 1.0 / K12 /...

NLN

etc.

Many proprietary ... flavours:

Blackboard

WebCT

etc.

Package transcoding service

Package transcoding service: requirements Human, REST and SOAP interface All three? In that order? Location National, institutional or both? Standards IMS CP flavours first, RAMLET later?

Human, REST and SOAP interface

All three?

In that order?

Location

National, institutional or both?

Standards

IMS CP flavours first, RAMLET later?

Questions? Wilbert Kraan [email_address]

Wilbert Kraan

[email_address]