1 / 11

DAM Runtime Implementation In a Nutshell

DAM Runtime Implementation In a Nutshell. By: LCdr Roger St-Pierre. Goals of this R&D was to explore:. How to create SCO content in an appearance neutral manner How to encode appearance properties; and How to implement this within an LMS. General Approach. XML Semantic Markup – DocBook

xenia
Download Presentation

DAM Runtime Implementation In a Nutshell

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. DAM Runtime Implementation In a Nutshell By: LCdr Roger St-Pierre

  2. Goals of this R&D was to explore: • How to create SCO content in an appearance neutral manner • How to encode appearance properties; and • How to implement this within an LMS

  3. General Approach • XML Semantic Markup – DocBook • SCOs devoid of stylistic information • XML schema was developed to constrain the appearance of a SCO • IEEE LOM • Technical.format • Educational.learningResourceType • AccLIP IMS user preferences

  4. ADL DAM RTE LMS: CP LMS: Sequencer LMS TILE: Auxiliary Srvc Logo, Part Location ToC Tools Hdr, Ftr SCO AccLIP: CSS Metadata XSL DAM: XSL DAM: Match Content To Location, Add Content Elements DAM: User CSS SCO: XHTML + Intra-SCO Navigation SCO: XHTML + Intra-SCO Navigation + Top, Bottom, Left, Right Content SCO: Final XHTML Overall Sequence of Events

  5. CP Manifest • ORGANISATION Appearance: • declaration of XSL based on • Technical.format and • Educational.learningResourceType • location of Logo and its • Alternative text Logo Info LMS DAM: XSL Default ITEM LOM: Technical.format and Educational.learningResourceType XSL Style Sheet LMS DAM: … ITEM LOM: Technical.format and Educational.learningResourceType Technical.format Educational.learningResourceType SCO: DocBook XML Styling Information

  6. Semantic Model-View-Controller model • XML Expresses the “Model” • XML SCOs contain no style (“View”) and no code (“Controller”) • Who provides additional “controller” information in the transformation and how? (e.g. Intra-SCO Navigation)

  7. DocBook Semantic Markup • Numerous XSL style sheets for transforming into XHTML, PDF, etc. I.e. quite flexible in terms of tranformation • Suitability for e-Learning? Primarily used for documentation • No provision for interactive content such as Forms

  8. DAM Markup Includes • Method for transforming SCO into XHTML • Method for defining transformation based on type of SCO • Way of specifying auxiliary services • Way of specifying a logo; and • Way of defining layout

  9. Metadata Attributes • technicalFormat • Used to define the format of the input to the XSLT process • learningResourceType • Used to further constrain the transformation based on type of SCO

  10. Binding Technique for DAM Markup • Option 1 - Internal to Content Package • Option 2 - External to Content Package with reference in the CP; and • Option 3 – DAM Markup itself references the CP (I.e. Option 2 reversed)

  11. Conclusion • It can be done; but will require • a consensus on issues such as: • Use of Metadata to obtain style • Standardization of content semantic markup • Binding technique for DAM markup • Best practices

More Related