Information For Learning  Object eXchange (ILOX) David Massart, EUN
Licensed under IMS LODE License <ul><li>Creative Commons Attribution-Share Alike 3.0 United States License </li></ul><ul><...
Disclaimer <ul><li>The work described in this presentation is partially supported by the European Community eContent plus ...
Outline <ul><li>Materialization </li></ul><ul><li>Functional Requirements for Bibliographic Records (FRBR) </li></ul><ul><...
<ul><li>An abstraction mechanism (conceptual modeling)  </li></ul><ul><li>The relationship between a class of categories (...
Materialization (cont.) <ul><li>Supports some sort of attribute-propagation mechanism </li></ul><ul><li>I.e., many attribu...
Functional Requirements for Bibliographic Records – FRBR [fɝbɚ]
 
FRBR Is an Example of Materialization
 
Learning Object Copies
FRBR and LOM <ul><li>Some LOM data elements are typical of one FRBR aspect of learning objects </li></ul><ul><li>Some LOM ...
FRBR and LOM
Describing LOs at Different FRBR Levels <ul><li>General Principle </li></ul><ul><li>Describing a learning object as a </li...
General Principle <ul><li>Describe each FRBR level with </li></ul><ul><ul><li>Optional Identifier </li></ul></ul><ul><ul><...
Describing an LO as a FRBR Work
Describing with Metadata
Work-Level Metadata <ul><li>Metadata elements typical of a work </li></ul><ul><li>LOM examples: </li></ul><ul><ul><li>Gene...
Description Facets <ul><li>Content Provider Metadata </li></ul><ul><li>Folksonomies </li></ul><ul><li>Translation </li></u...
License as a Facet <ul><li>Identifier: A URI (e.g.,  http://creativecommons.org/licenses/by-sa/2.0/be/ ) </li></ul><ul><li...
License Facet <ul><li>Can be  present at any FRBR-level </li></ul><ul><li>License applied to an object at one level </li><...
Describing an LO as a FRBR Expression
Expression-Level Metadata <ul><li>Metadata elements typical of an Expression </li></ul><ul><li>LOM examples: </li></ul><ul...
Describing an LO as a FRBR Manifestation
Manifestation Names & <Parameters> <ul><li>Preview (will require best practice) </li></ul><ul><li>Thumbnail  of <Mime Type...
Package in <format> <ul><li>Vocabulary:  http://imsglobal.org/vdex/imscp_terms_resource.xml </li></ul><ul><li>Note: Look a...
Manifestation-Level Metadata <ul><li>Metadata elements typical of a Manifestation </li></ul><ul><li>LOM examples: All the ...
Describing an LO as a FRBR Item
Item Location <ul><li>URI (resolvable location: e.g., a URL or a persistent identifier for  a copy of the LO - handle, DOI...
Item-Level Metadata <ul><li>Metadata elements typical of an Item </li></ul><ul><li>LOM example: Technical.location  </li><...
Digital Right Management @ LRE
Digital Right Management @ LRE
LRE DRM and Item Location <ul><li>How does the Requestor find the LRE DRM Service?  item.location.URI </li></ul><ul><li>Ho...
Metadata Description In Practice <ul><li>Best practice rather than strict rules </li></ul><ul><li>Selecting the right leve...
Selecting The Right Level <ul><li>Work: One result entry by learning object (LO): No immediate distinction between the LO ...
What Goes In A Description:   Context <ul><li>Harvesting: Full metadata record(s) attached to the selected level  </li></u...
What Goes In A Description: FRBR Level
What Goes In A Description: FRBR Level
What Goes In A Description: FRBR Level
What Goes In A Description: FRBR Level
What Goes In A Description: FRBR Level  (cont.) Selected Level /Description Work Expression Manifestation Item Work Work E...
What Goes In A Description:  Informational Needs
Handling LOM (instead of LOs) <ul><li>Work </li></ul><ul><ul><li>Meta-metadata.identifier </li></ul></ul><ul><ul><li>Meta-...
ILOX versus OAI-ORE <ul><li>OAI-ORE and ILOX are orthogonal </li></ul><ul><li>Conceptually,  </li></ul><ul><ul><li>OAI-ORE...
Kill (more than) Two Birds With One Stone <ul><li>ILOX is a conceptually clean solution for </li></ul><ul><li>Selecting fr...
Upcoming SlideShare
Loading in …5
×

Information for learning object exchange

1,906 views

Published on

0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,906
On SlideShare
0
From Embeds
0
Number of Embeds
15
Actions
Shares
0
Downloads
0
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide
  • Information for learning object exchange

    1. 1. Information For Learning Object eXchange (ILOX) David Massart, EUN
    2. 2. Licensed under IMS LODE License <ul><li>Creative Commons Attribution-Share Alike 3.0 United States License </li></ul><ul><li>Notification of patent claims </li></ul><ul><li>Sharing of derivative works with the IMS LODE Community </li></ul><ul><li>http://www.imsglobal.org/lode/lode_license.html </li></ul>
    3. 3. Disclaimer <ul><li>The work described in this presentation is partially supported by the European Community eContent plus programme - project ASPECT: Adopting Standards and Specifications for Educational Content (Grant agreement number ECP-2007-EDU-417008). The author is solely responsible for the content of this presentation. It does not represent the opinion of the European Community and the European Community is not responsible for any use that might be made of information contained therein. </li></ul>
    4. 4. Outline <ul><li>Materialization </li></ul><ul><li>Functional Requirements for Bibliographic Records (FRBR) </li></ul><ul><li>FRBR & LOM </li></ul><ul><li>Describing LOs at Different FRBR Levels </li></ul><ul><li>Metadata description in practice </li></ul><ul><li>Handling LOM (instead of LOs) </li></ul><ul><li>Discussion: ILOX versus OAI-ORE </li></ul>
    5. 5. <ul><li>An abstraction mechanism (conceptual modeling) </li></ul><ul><li>The relationship between a class of categories (e.g., a book) and a class of more concrete objects (e.g., a book copy) </li></ul>
    6. 6. Materialization (cont.) <ul><li>Supports some sort of attribute-propagation mechanism </li></ul><ul><li>I.e., many attributes of the more abstract class are naturally applicable to the more concrete class </li></ul><ul><li>E.g., the title of a book applies to all its copies </li></ul>
    7. 7. Functional Requirements for Bibliographic Records – FRBR [fɝbɚ]
    8. 9. FRBR Is an Example of Materialization
    9. 11. Learning Object Copies
    10. 12. FRBR and LOM <ul><li>Some LOM data elements are typical of one FRBR aspect of learning objects </li></ul><ul><li>Some LOM data elements are potentially relevant to describe more than one FRBR aspect </li></ul><ul><li>Other LOM elements do not describe any FRBR aspect of learning objects </li></ul><ul><li>In principle, all LOM data elements being optional, a LOM instance can be used to describe any of the 4 FRBR aspects of a learning object </li></ul>
    11. 13. FRBR and LOM
    12. 14. Describing LOs at Different FRBR Levels <ul><li>General Principle </li></ul><ul><li>Describing a learning object as a </li></ul><ul><ul><li>FRBR Work </li></ul></ul><ul><ul><li>FRBR Expression </li></ul></ul><ul><ul><li>FRBR Manifestation </li></ul></ul><ul><ul><li>FRBR Item </li></ul></ul>
    13. 15. General Principle <ul><li>Describe each FRBR level with </li></ul><ul><ul><li>Optional Identifier </li></ul></ul><ul><ul><li>Level-specific metadata (e.g., LOM, DC, …) </li></ul></ul><ul><ul><li>Additional level specific information (when needed) </li></ul></ul><ul><ul><li>Information about the direct lower FRBR level </li></ul></ul>
    14. 16. Describing an LO as a FRBR Work
    15. 17. Describing with Metadata
    16. 18. Work-Level Metadata <ul><li>Metadata elements typical of a work </li></ul><ul><li>LOM examples: </li></ul><ul><ul><li>General.Title </li></ul></ul><ul><ul><li>General.Description </li></ul></ul><ul><ul><li>Educational </li></ul></ul><ul><ul><li>Classification </li></ul></ul>
    17. 19. Description Facets <ul><li>Content Provider Metadata </li></ul><ul><li>Folksonomies </li></ul><ul><li>Translation </li></ul><ul><li>NOTE: Will require a controlled vocabulary </li></ul>
    18. 20. License as a Facet <ul><li>Identifier: A URI (e.g., http://creativecommons.org/licenses/by-sa/2.0/be/ ) </li></ul><ul><li>Description: Metadata (e.g., lom.rights or a DREL expression) </li></ul>
    19. 21. License Facet <ul><li>Can be present at any FRBR-level </li></ul><ul><li>License applied to an object at one level </li></ul><ul><ul><li>Applies to all its materialization at the lowest levels </li></ul></ul><ul><ul><li>Unless it is overridden at a lower level </li></ul></ul><ul><li>Note that more than one license can apply to the same object (i.e., a facet is not a key – It is possible to have more than one license facet) </li></ul>
    20. 22. Describing an LO as a FRBR Expression
    21. 23. Expression-Level Metadata <ul><li>Metadata elements typical of an Expression </li></ul><ul><li>LOM examples: </li></ul><ul><ul><li>General.language </li></ul></ul><ul><ul><li>Life-cycle </li></ul></ul>
    22. 24. Describing an LO as a FRBR Manifestation
    23. 25. Manifestation Names & <Parameters> <ul><li>Preview (will require best practice) </li></ul><ul><li>Thumbnail of <Mime Type image/xxxx> </li></ul><ul><li>Metadata in <URI of the schema> </li></ul><ul><li>Experience (as rendered in my user interface – “remote play”) </li></ul><ul><li>Package in <format> </li></ul>
    24. 26. Package in <format> <ul><li>Vocabulary: http://imsglobal.org/vdex/imscp_terms_resource.xml </li></ul><ul><li>Note: Look at W3C HTTP Content Negotiation for compression, encodings </li></ul>
    25. 27. Manifestation-Level Metadata <ul><li>Metadata elements typical of a Manifestation </li></ul><ul><li>LOM examples: All the technical elements but location </li></ul>
    26. 28. Describing an LO as a FRBR Item
    27. 29. Item Location <ul><li>URI (resolvable location: e.g., a URL or a persistent identifier for a copy of the LO - handle, DOI, PURL) </li></ul><ul><li>Description: Metadata (optional) </li></ul>
    28. 30. Item-Level Metadata <ul><li>Metadata elements typical of an Item </li></ul><ul><li>LOM example: Technical.location </li></ul>
    29. 31. Digital Right Management @ LRE
    30. 32. Digital Right Management @ LRE
    31. 33. LRE DRM and Item Location <ul><li>How does the Requestor find the LRE DRM Service? item.location.URI </li></ul><ul><li>How does it select the relevant context? item.location.description </li></ul>
    32. 34. Metadata Description In Practice <ul><li>Best practice rather than strict rules </li></ul><ul><li>Selecting the right level </li></ul><ul><li>What goes in a description depends on: </li></ul><ul><ul><li>The context: Harvesting, search, publishing </li></ul></ul><ul><ul><li>The selected FRBR level: Work, expression, manifestation, item </li></ul></ul><ul><ul><li>The informational needs </li></ul></ul>
    33. 35. Selecting The Right Level <ul><li>Work: One result entry by learning object (LO): No immediate distinction between the LO versions </li></ul><ul><li>Expression: One result entry by LO version: No immediate distinction between the different formats of a given LO version </li></ul><ul><li>Manifestation: One result entry by LO format: No immediate distinction between the different copies of an LO. </li></ul><ul><li>Item: One result entry by LO copy </li></ul>
    34. 36. What Goes In A Description: Context <ul><li>Harvesting: Full metadata record(s) attached to the selected level </li></ul><ul><li>Publishing: Full metadata record(s) attached to the selected level </li></ul><ul><li>Search: Metadata elements relevant to the selected levels </li></ul>
    35. 37. What Goes In A Description: FRBR Level
    36. 38. What Goes In A Description: FRBR Level
    37. 39. What Goes In A Description: FRBR Level
    38. 40. What Goes In A Description: FRBR Level
    39. 41. What Goes In A Description: FRBR Level (cont.) Selected Level /Description Work Expression Manifestation Item Work Work Expression Manifestation Item Expression N/A Work + Expression Manifestation Item Manifestation N/A N/A Work + Expression + Manifestation Item Item N/A N/A N/A Work + Expression + Manifestation + Item
    40. 42. What Goes In A Description: Informational Needs
    41. 43. Handling LOM (instead of LOs) <ul><li>Work </li></ul><ul><ul><li>Meta-metadata.identifier </li></ul></ul><ul><ul><li>Meta-metadata.contribute </li></ul></ul><ul><li>Expression </li></ul><ul><ul><li>Meta-metadata.language </li></ul></ul><ul><li>Manifestation </li></ul><ul><ul><li>Meta-metadata.schema </li></ul></ul>
    42. 44. ILOX versus OAI-ORE <ul><li>OAI-ORE and ILOX are orthogonal </li></ul><ul><li>Conceptually, </li></ul><ul><ul><li>OAI-ORE implements the “Aggregation” abstraction mechanism </li></ul></ul><ul><ul><li>ILOX implements the “Materialization” abstraction mechanism </li></ul></ul><ul><li>They can be combined: E.g., materialization of aggregation </li></ul>
    43. 45. Kill (more than) Two Birds With One Stone <ul><li>ILOX is a conceptually clean solution for </li></ul><ul><li>Selecting from several LO versions </li></ul><ul><li>Selecting from several package formats </li></ul><ul><li>Attaching licenses to the right level </li></ul><ul><li>Handling an LO description split into several metadata instances </li></ul><ul><li>Providing the appropriate amount of information in search results </li></ul><ul><li>Supporting DRM approaches </li></ul>

    ×