1 / 11

An Application Profile for Small Learning Objects

An Application Profile for Small Learning Objects. Ingo Dahn University Koblenz-Landau The Telcert Project. The Context Problems. One learning objects must be build from various components at reuse time (? Distributed LO ?)

aquila
Download Presentation

An Application Profile for Small Learning Objects

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. An Application Profile for Small Learning Objects Ingo Dahn University Koblenz-Landau The Telcert Project

  2. The Context Problems • One learning objects must be build from various components at reuse time (? Distributed LO ?) • This must be done differently for reuse in different contexts (? Makefile in LO?) • One learning object may require for reuse in certain contexts the presence of other learning objects • Joint reuse of a collection of learning objects requires establishing a joint context How can we profile MD specs to support this?

  3. Specifications and Profiles • eLearning specifications are given by • A data model (not machine processable) • An XML binding (machine processable) • Other documents (Best practice, runtime spec.) • Application profiles • Adapt specifications to the service needs of communities • May, but need not, respect interoperability • Are supported by IMS and the Telcert project

  4. Application Profiles • Modify one base specification • May modify cardinalities or attribute properties • May have condition-dependent modifications • Can be • Restrictive, extensive or incompatible • Can have • Mild extensions (at wildcards) • Wild extensions (anywhere else) • May not reorder elements

  5. The Telcert Project • FP6 project 2004-2006 • Coordinated by D. Rose (Open Group) and K. Riley (eLoki) • Objective: • Develop tools/content/test suite for developing/certifying compliant content and systems • Make these adaptable to any specification and application profile • http://www.opengroup.org/telcert/ • See Cool Tools in IMS Public Dispatch (March 05)

  6. Slicing Book Services • Aggregate documents on the fly from small parts (learning objects) of pre-existing documents • Search for learning objects by multilingual key phrases • Search for objects of specific types • Complete selections for learning scenarios • Present objects in different styles/media

  7. Technical Context <ul> (start) <li>Content 1</li> (main) <li>Content 2</li> (main) </ul> (end) • Several resources for 1 learning object • Files have roles (start/main/end) and purposes (style/media)

  8. Objects have assigned… • Position (sourcereference) • Key phrases from a structured VDEX thesaurus • Types • Navigation titles • Relations: References, Requires, ReferencesPart, Explains, Translates, ExternalReference

  9. Metadata Calculation • By downward inheritance along source document structure (implicite) • Path Inclusion Principle • From content/style analysis (explicite) • By inference (implicite)

  10. TS Metadata Profile • Application Profile of IMS Metadata 1.2.2 • Restrictive • Mild extensions for • Roles, Positions • Metadata authors and MD Assignment confirmation • Inheritance • No conditional modifications, no wild extensions • Specific vocabularies •  Exists derived schema • Location points to multiple files

  11. Thank you See paper fo details Download MD application profile XML binding and samples from http://www.opengroup.org/telcert/

More Related