LRE Metadata Application Profile v4.0
David Massart, EUNBudapest, Hungary – Nov. 2, 2009
Outline
• LRE Overview• LRE Limitations• LRE Metadata Application Profile v4.0• Managing and Using Vocabularies• Identifying Resources• ASPECT Service Center
LRE Metadata Application Profile
• http://fire.eun.org/LREMAPv4p0.pdf
LRE Portal
LRE Vision
• It is NOT a centralised portal…
• But a framework that supports semantic and technical interoperability of content repositories
Learning Resource Exchange
An infrastructure for1. Federating applications that provide
learning resources (e.g., learning resource repositories, authoring tools)
2. Offering a seamless access to these resources to educational applications that consume them (e.g., educational portals, VLEs, IWBs)
A Metadata Problem
LREv3.0 Limitations (LOM)
LREv4.0 (ILOX + LOM)
Expression (version)
Description
Vocabulary Type
Expression Description Facets
VBE Vocabulary Identifier: LRE.expressionDescriptionFacetValues
Identifier Type
Manifestation (format)
Item (copy)
Item Location
• URI (resolvable location: e.g., a URL or a persistent identifier for a copy of the LO - handle, DOI, PURL)
• Description: Metadata (optional)
Item Sub-elements• “location.uri” should be resolvable
– Either it resolves to the location of the object (no location.metadata permitted)
– Or it resolves to the location of a service that gives access to the object (mandatory location.metadata to describe the access control service)
• Non-resolvable identifier should be put in item.identifier
• Other descriptions should be put in item.description
Describing Expressions with IEEE LOM
• No mandatory elements• Mandatory way to use elements
(controlled vocabularies)• Core elements• Recommended elements• Optional elements• Unused elements
Core Elements
1. General.Language – LOM 1.32. Educational.Learning Resource Type –
LOM 5.23. Rights – LOM 6
• CORE = Optional but necessary
Recommended Elements
1. General.Title - LOM 1.22. General.Description - LOM 1.43. General.Keyword - LOM 1.54. Life Cycle.Contribute – LOM 2.35. Meta-Metadata.Language - LOM 3.46. Educational.Intended End User Role - LOM 5.57. Educational.Learning Context - LOM 5.68. Educational.Typical Age Range – LOM 5.79. Classification – LOM 9
• Recommended = Optional but good to have
Unused Elements
1. Technical – LOM 42. Classification.Keyword – LOM 9.4
• Unused = Should not be used (conflict with other elements)
Optional Elements
• All the elements that do not belongs to the ‘core’, ‘recommended’ and ‘unused’ categories are optional
• Might be safely ignored but• When used, some usage rules might have
to be followed
LRE Controlled Vocabularies
• Key to deal with– Multilingualism– Processable semantics
• Managed in a Vocabulary Bank for Education (VBE) where– Each vocabulary and vocabulary term is
identified– Term translations are kept– Crosswalks are stored
http://aspect.vocman.com/
RIGHTS.COST – LOM 6.1
http://aspect.vocman.com/vbe/user/download/LOM/costValues.vdexhttp://aspect.vocman.com/vbe/user/download/LOM/costValues.zthes
Encoding Vocabulary Term
• Authorized values– Source: <VBE Vocabulary Identifier>– Value: <VBE Vocabulary Term Identifier>
• Example: – Source = “costValues”– Value = “yes”
Identifiers
What to Identify?
Expression Identifier
• Content providers are strongly encouraged– To identify at least LO expressions– To consistently use identifiers
• It is possible to use more than one identifier
Metadata Travels
Metadata Travels
>25 Content Providers
LRE Identity Service
Trusted Identifier
Trusted Identifier
Trusted Identifier
Trusted Identifier
Trusted Identifier
Trusted Identifier
Trusted Identifier
Trusted Identifier
Trusted Identifier
Trusted Identifier
Handle System
• “Persistent” identifier for LO expression• Stamp (quality label) trusted between LRE
members• Can be resolved
– Content providers– LRE version of the metadata– Signature verification
Service Center
1. LOR Registry2. Vocabulary Bank3. App Profile Registry4. Automatic metadata language translation5. Automatic metadata format transformation6. Automatic content format transcoding7. Compliance testing8. Identifier service – handle9. Access to known interoperability issues