470 likes | 655 Views
LRE Metadata Application Profile v4.0. David Massart, EUN Budapest, 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.
E N D
LRE Metadata Application Profile v4.0 David Massart, EUN Budapest, 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
It isNOT a centralised portal… But a frameworkthat supports semantic and technical interoperability of content repositories LRE Vision
Learning Resource Exchange An infrastructure for • Federating applications that provide learning resources (e.g., learning resource repositories, authoring tools) • Offering a seamless access to these resources to educational applications that consume them (e.g., educational portals, VLEs, IWBs)
Expression Description Facets VBE Vocabulary Identifier: LRE.expressionDescriptionFacetValues
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 • General.Language – LOM 1.3 • Educational.Learning Resource Type – LOM 5.2 • Rights – LOM 6 • CORE = Optional but necessary
Recommended Elements • General.Title - LOM 1.2 • General.Description - LOM 1.4 • General.Keyword - LOM 1.5 • Life Cycle.Contribute – LOM 2.3 • Meta-Metadata.Language - LOM 3.4 • Educational.Intended End User Role - LOM 5.5 • Educational.Learning Context - LOM 5.6 • Educational.Typical Age Range – LOM 5.7 • Classification – LOM 9 • Recommended = Optional but good to have
Unused Elements • Technical – LOM 4 • 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
Rights.Cost – LOM 6.1 http://aspect.vocman.com/vbe/user/download/LOM/costValues.vdex http://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”
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
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 • LOR Registry • Vocabulary Bank • App Profile Registry • Automatic metadata language translation • Automatic metadata format transformation • Automatic content format transcoding • Compliance testing • Identifier service – handle • Access to known interoperability issues