Report on Work of Joint DCMI/IEEE LTSC Task Force


Published on

A brief report on the work of the DCMI/IEEE Task Force on interoperability between the IEEE Learning Object Metadata standard and Dublin Core.

Presentation given to meeting of CETIS Metadata & Digital Repositories Special Interest Group held in Bath on 28 June 2006.

Published in: Economy & Finance, Education
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Report on Work of Joint DCMI/IEEE LTSC Task Force

  1. 1. Update on work of Joint DCMI/IEEE LTSC Task Force CETIS Metadata & Digital Repositories SIG, UKOLN, Bath
  2. 2. Background <ul><li>Metadata standards typically developed to support requirements of some community or domain </li></ul><ul><li>Resources used across community/domain boundaries </li></ul><ul><li>Implementers want </li></ul><ul><ul><li>to use component parts of different standards in combination </li></ul></ul><ul><ul><li>to (re)use components of other implementers’ work </li></ul></ul><ul><li>Concept of “ metadata application profile ” (e.g. Heery/Patel, Duval et al) </li></ul><ul><ul><li>tailor standard to context </li></ul></ul><ul><ul><li>combine components from different standards (“mix & match”) </li></ul></ul>
  3. 3. Abstract Models for Metadata <ul><li>Abstract Model of metadata standard specifies </li></ul><ul><ul><li>Nature of components and constructs used in standard </li></ul></ul><ul><ul><li>Set of rules for building abstract information structure </li></ul></ul><ul><li>IEEE LOM Abstract Model </li></ul><ul><ul><li>AIS = LOM instance </li></ul></ul><ul><ul><li>Data elements containing other data elements </li></ul></ul><ul><ul><li>“ Leaf” data element values associated with datatypes (how value spaces interpreted) </li></ul></ul><ul><li>DCMI Abstract Model </li></ul><ul><ul><li>AIS = DC description set </li></ul></ul><ul><ul><li>Description = set of statements about resource </li></ul></ul><ul><ul><li>Statement </li></ul></ul><ul><ul><ul><li>references to property, value, vocabulary encoding scheme, syntax encoding scheme </li></ul></ul></ul><ul><ul><ul><li>value strings, value representations </li></ul></ul></ul>
  4. 4. Abstract Models & Application Profiles <ul><li>Both DC and LOM have notions of “metadata application profile”… </li></ul><ul><li>… but based on respective Abstract Model </li></ul><ul><li>DC Application Profile </li></ul><ul><ul><li>how to use a set of identified properties, vocabulary encoding schemes, syntax encoding schemes to construct a DC metadata description set </li></ul></ul><ul><li>LOM Application Profile </li></ul><ul><ul><li>how to use a set of identified LOM data elements, datatypes, vocabularies to construct a LOM instance </li></ul></ul><ul><ul><li>LOM conceptual data schema includes AM and a “base” application profile </li></ul></ul>
  5. 5. Abstract Models & Bindings for Metadata <ul><li>Abstract Models are syntax-independent </li></ul><ul><li>Bindings describe </li></ul><ul><ul><li>how abstract information structure is serialised/encoded in a metadata format </li></ul></ul><ul><ul><li>how instances of a metadata format are interpreted in terms of abstract information structure </li></ul></ul><ul><li>Both DC & LOM have bindings to XML formats </li></ul><ul><li>However, formats interpreted in terms of different Abstract Models </li></ul><ul><ul><li>e.g. XML element parent-child relationships have different interpretations in LOM-XML and DC-XML </li></ul></ul>
  6. 6. System A DC Description Set DC-XML Instance Encode using Binding Construct using DCAM & DCAP Decode using Binding DC Description Set Interpret using DCAM System B DC-XML Instance <?xml version=&quot;1.0&quot;?> <dcx:descriptionSet>
  7. 7. System A Encode using Binding Construct using LOM AM & LOM AP Decode using Binding Interpret using LOM AM System B <?xml version=&quot;1.0&quot;?> <lom:LOM> LOM Instance LOM Instance LOM-XML Instance LOM-XML Instance
  8. 8. The problem <ul><li>IEEE LOM standard and Dublin Core based on different Abstract Models </li></ul><ul><li>LOM data elements and DC properties/classes can not be used in combination in same information structure </li></ul><ul><li>Earlier work on DC-LOM interoperability focused on RDF </li></ul><ul><ul><li>mapping LOM to RDF </li></ul></ul><ul><ul><li>mapping DC to RDF </li></ul></ul><ul><li>Not generalisable to other DC formats </li></ul>
  9. 9. The proposed solution <ul><li>Develop a LOM-DCAM mapping </li></ul><ul><ul><li>“ LOM data elements” => “instances of DCAM components/constructs” </li></ul></ul><ul><ul><li>Interpretation of LOM semantics in terms of DCAM </li></ul></ul><ul><li>Not a binding for LOM, but a translation </li></ul><ul><ul><li>lossy in part </li></ul></ul><ul><ul><li>one-way translation </li></ul></ul><ul><li>Approach </li></ul><ul><ul><li>conceptualise LOM as Entity-Relationship model </li></ul></ul><ul><ul><ul><li>build on earlier work for LOM RDF binding </li></ul></ul></ul><ul><ul><li>represent E-R model in terms of DCAM constructs </li></ul></ul><ul><ul><li>specify required terms, assign URIs </li></ul></ul>
  10. 10. LOM Conceptual Data Schema Dublin Core Abstract Model DC-RDF Instance DC-XML Instance conforms to conforms to bound to translate (lossy) bound to LOM Instance DC Description Set LOM-XML Instance DC Description Set Combined DC Description Set
  11. 11. Outcomes <ul><li>View of LOM as a basic DC Application Profile </li></ul><ul><li>Availability of set of “LOM terms” which are usable in other DCAPs </li></ul><ul><li>Availability of RDF binding of LOM “for free” via DC RDF binding (mapping) </li></ul><ul><li>Separation of LOM-DCAM translation from RDF binding </li></ul><ul><li>First step towards better alignment of DC and LOM abstract models? </li></ul>
  12. 12. Joint DCMI/IEEE LTSC Task Force <ul><li>Initiated at DC2005 in Madrid, Sep 2005 </li></ul><ul><li>Reports to DC Education WG & IEEE LTSC </li></ul><ul><li>Chairs: Mikael Nilsson & Jon Mason </li></ul><ul><li>Participation open to all: </li></ul><ul><ul><li>mailing list (~20 subscribers), Wiki </li></ul></ul><ul><li>Joint: </li></ul><ul><ul><li>Collaborative work on drafts </li></ul></ul><ul><ul><li>Joint consensus </li></ul></ul><ul><ul><li>Co-publishing of results </li></ul></ul><ul><li>Aim: an IEEE “Recommended Practice” and a DCMI “Recommendation” </li></ul>
  13. 13. Joint DCMI/IEEE LTSC Task Force <ul><li>Charter approved by DCMI Advisory Board and IEEE LTSC SEC </li></ul><ul><li>Draft PAR Scope & Purpose presented to LOM WG (March 2006) </li></ul><ul><li>Three initial outputs available for discussion: </li></ul><ul><ul><li>Draft of LOM-DCAM mapping </li></ul></ul><ul><ul><ul><li>includes description of DCAP </li></ul></ul></ul><ul><ul><li>Example instance based on mapping </li></ul></ul><ul><ul><ul><li>LOM XML </li></ul></ul></ul><ul><ul><ul><li>DC Text </li></ul></ul></ul><ul><ul><li>Draft of required property/class/value definitions </li></ul></ul><ul><ul><ul><li>folllowing DC “Schema Model”/Usage Board conventions </li></ul></ul></ul>
  14. 14. <ul><li>LOM-XML </li></ul><ul><li>DescriptionSet ( </li></ul><ul><li>Description ( </li></ul><ul><li>ResourceURI ( <> ) </li></ul><ul><li>Statement ( </li></ul><ul><li>PropertyURI ( dc:title ) </li></ul><ul><li>ValueString ( “Wilfred Owen and Realism” </li></ul><ul><li>Language ( en-GB ) </li></ul><ul><li>) </li></ul><ul><li>) </li></ul><ul><li>Statement ( </li></ul><ul><li>PropertyURI ( dc:language ) </li></ul><ul><li>ValueString ( “en-GB” </li></ul><ul><li>SyntaxEncodingSchemeURI ( dcterms:RFC3066 ) </li></ul><ul><li>) </li></ul><ul><li>) </li></ul><ul><li>Statement ( </li></ul><ul><li>PropertyURI ( lom:keyword ) </li></ul><ul><li>VocabularyEncodingSchemeURI ( a:NLS ) </li></ul><ul><li>ValueString ( &quot;Owen, Wilfred&quot; </li></ul><ul><li>Language ( en-GB ) </li></ul><ul><li>) </li></ul><ul><li>) </li></ul><ul><li>) </li></ul><ul><li>) </li></ul><lom> <general> <identifier> <catalog>URI</catalog> <entry></entry> </identifier> <title> <string language=&quot;en-GB&quot;>Wilfred Owen and Realism</string> </title> <language>en-GB</language> <keyword> <string language=&quot;en-GB&quot;>Owen, Wilfred</string> </keyword> </general> </lom> DC-Text
  15. 15. Other related DCMI work <ul><li>Expressing DC metadata using XML </li></ul><ul><ul><li>Working Draft for public comment (June 2006) </li></ul></ul><ul><ul><li>Revised XML binding for DC </li></ul></ul><ul><li>Expressing DC metadata using RDF </li></ul><ul><ul><li>Working Draft for public comment (June 2006) </li></ul></ul><ul><ul><li>Mapping from DCAM to RDF </li></ul></ul><ul><li>DC-Text: A Text Syntax for DC metadata </li></ul><ul><ul><li>Under discussion by DC Architecture WG </li></ul></ul><ul><li>Updating of DCMI term definitions </li></ul><ul><ul><li>Under discussion by DC Usage Board </li></ul></ul>
  16. 16. Next steps <ul><li>Verify mapping through more examples </li></ul><ul><ul><li>Identify points of loss-iness </li></ul></ul><ul><li>Finalise mapping </li></ul><ul><li>Finalise terms, definitions, URIs </li></ul><ul><li>Finalise DCAP </li></ul><ul><li>Special Session at DC2006 (October, 2006, Colima, Mexico) </li></ul><ul><li>Prepare docs for formal review/publication </li></ul><ul><li>Feed into DC Education WG work on DC Ed AP </li></ul><ul><li>Feed into IEEE LTSC work on “next generation” LOM </li></ul>
  17. 17. Joint DCMI/IEEE LTSC Task Force <ul><li> </li></ul>
  18. 18. Update on work of Joint DCMI/IEEE LTSC Task Force CETIS Metadata & Digital Repositories SIG, UKOLN, Bath