skip to main page content CETIS: Click here to return to the homepage
the centre for educational technology interoperability standards

skip over the long navigation bar
Home
News
Features
Events
Forums
Reference
Briefings
Press centre

Inside Cetis
what is Cetis?
Contact us
Cetis staff
Jobs at CETIS


 




Syndication
XML: Click here to get the news as an RSS XML file XML: Click here to get the news as an Atom XML file iCAL: Click here to get the events as an iCalendar file

Background
what are learning technology standards?
who's involved?
who's doing what?

CETIS Groups
what are cetis groups?
what difference can they make?
Assessment SIG
Educational Content SIG
Enterprise SIG
Metadata SIG
Life Long Learning Group
Portfolio SIG
Accessibility Group
Pedagogy Forum
Developer's forum

Subjects
Accessibility (310)
Assessment (74)
Content (283)
Metadata (195)
Pedagogy (34)
Profile (138)
Tools (197)
For Developers (569)
For Educators (344)
For Managers (339)
For Members (584)
SCORM (118)
AICC (18)
CEN (34)
DCMI (36)
EML (47)
IEEE (79)
IMS (302)
ISO (21)
OAI (24)
OKI (20)
PROMETEUS (12)
W3C (37)

print this article (opens in new window) view printer-friendly version (opens in new window)

Digital Repositories Interoperability spec approved by IMS

The latest IMS spec to reach 'final' status deals with ways to store learning objects and make them available to other people. There are quite a few specs out there that will help systems do that already, but none specifically geared to make use of the IMS Meta-Data spec. Fortunately, IMS is not in the mood to start re-inventing the wheel, and has therefore liberally borrowed from existing specs.

In the much-vaunted learning object economy, where people would create, trade and use autonomous bits of online teaching material, the repository is a pretty pivotal part. Its where you submit learning objects for storage, expose them for searching and gathering by others, and from where you deliver them upon request. Ideally, you would alert other people when your repository is updated as well, but that's the part that IMS DRI doesn't do just yet.

But with the bits that are there, the idea is that learners, teachers and learning object authors can use their favourite VLE or Portal to submit, search and get at learning objects. Provided those systems will support IMS DRI, of course. Since not supporting it might deprive VLE and Portal users of a lot of useful content, that's not likely to be a major issue.

But submitting and querying at the VLE/Portal end is the easy bit. After that, some more sophisticated choreography is needed between the VLEs and Portals on the one hand, and databases, specialised learning object repositories and digital libraries on the other, with specialised search service inbetween. The difficulty here is essentially in translating between the different search languages, the combining of results from several repositories and simply having one 'agent' that keeps track of what all the systems are doing.

Though the functionality is potentially quite complex, most of IMS DRI should be easy for programmers to implement. Especially since important parts like the protocol for searching existing digital libraries is basically the same as the one libraries already use (Z39.50). Much the same goes for the protocol used for finding things inside learning objects (XQuery).

The picture is not quite so rosy for the mechanism used to exchange messages between all the different systems. While the basic technology (SOAP with attachments) is a well known quantity, the schema that is necessary to capture all the IMS DRI concepts in a SOAP message isn't there. Just like the public beta of more than six months ago, the final release binding document says that "An appropriate message schema is to be specified. It is anticipated that this schema will instantiate and refine more general message schemas to be developed by the appropriate IMS Project Groups."

Methods to ensure message security and ways to handle cascaded messages, failures, query cancellation and incomplete queries have not been implemented either, though the need for them is established. Given IMS' choice to go with existing specs as much as possible, that is neither surprising nor a major problem. Having half a message binding is.

The full documentation will be available from the IMS Digital Repositories page.

Related items:

Comments:

copyright cetis.ac.uk
Creative Commons License This work is licensed under a Creative Commons License.

syndication |publisher's statement |contact us |privacy policy

 go to start of page content