MetadataTheory: Metadata Standards (6th of 10)
1 like826 views
This document discusses metadata specifications and standards for learning objects. It describes definitions for standards, specifications, application profiles, and interoperability. It then outlines key metadata specifications like Dublin Core, IMS, IEEE LOM, ADL SCORM, and ISO, providing details on their purpose and development. The document emphasizes that metadata specifications aim to facilitate interoperability through crosswalks, open search protocols, and resolving semantic differences.
MetadataTheory: Metadata Standards (6th of 10)
- 2. Structure • Definitions • Specifications • Standards • Application Profiles • Interoperability
- 3. Definitions
- 4. Standard • Definitions or formats that have been approved by a recognised standards organization, or are accepted as de facto standards by the industry. Standards serve a regulatory function and have been created for programming languages, operating systems, data formats, communications protocols, and electrical interfaces
- 5. Specification • Less evolved than standards and attempt to capture a rough consensus in the user or implementer community. Specifications enable people to get on with the job of system and content development. It can take a long time before specifications are finally approved as standards
- 6. Application Profile • Is a simplified and interpreted version of a standard or specification that is created to serve the needs of a particular community of users or implementers. • Application profiles can combine elements from more than one specification or standard into a single profile, but should not modify these in such a way that would impact interoperability negatively
- 7. Interoperability • Interoperability is the ability of systems or components to work together, without unnecessary human intervention. In the case of metadata, interoperability refers specifically to the ability to exchange information and to process information that has been exchanged. True interoperability would allow users to search and otherwise make use of systems in a seamless manner – despite their location, origin, or internal operation.
- 9. Which ones? The principal metadata specifications for learning objects are the following: – Dublin Core http://purl.oclc.org/dc/ – IMS http://imsproject.com – IEEE LTSC LOM http://ltsc.ieee.org/index.html – ADL SCORM http://www.adlnet.org/Scorm/ – ISO http://jtc1sc36.org/#terms_of_reference
- 10. Dublin Core • Dublin Core is named for Dublin, Ohio, not Dublin, Ireland, and has been described as the most broadly based metadata specification. It coexists comfortably with the other metadata sets and is intended to facilitate interoperability between the semantics of metadata specifications
- 11. Dublin Core • Dublin Core metadata is syntax-independent, and can be encoded in a number of ways – in metatags in the header of an HTML document, in XML documents or in RDF/XML markup. Dublin Core consists of only fifteen optional elements such as Title, Description, Creator, Subject, etc
- 13. IMS • IMS (http://imsproject.com), the acronym for Instructional Management Systems, was established byEduCom (now EduCause) in 1994. The mandate of IMS is to serve as a catalyst for the development of instructional software, the creation of an online management infrastructure for learning, the facilitation of collaborative learning activities and certification
- 14. IMS • The IMS has been developing a number of specifications for the community of e-learning developers: i.e., content packaging, digital repository interoperability, and learning design. • Bindings or encodings are available for IMS metadata in both XML and RDF/XML. Although the IMS metadata schema represents an important activity, the IMS is not just a metadata schema. The IMS is involved in the development of other learning application specifications
- 15. ARIADNE • ARIADNE (http://ariadne.unil.ch/), the acronym for The Alliance of Remote Instructional Authoring and Distribution Networks for Europe, has fostered the sharing and reuse of electronic pedagogical material by universities and corporations. It attempted to create a European-wide repository for pedagogical documents called the Knowledge Pool System. It has also acted as a co-author of the IMS metadata structure
- 16. ADL SCORM • ADL SCORM (http://www.adlnet.org/Scorm/) is the Advanced Distributed Learning Network Sharable Courseware Object Reference Model, supported by the US Department of Defence and the US government. It combines and interprets a number of interrelated technical specifications built upon the work of the AICC, IMS and IEEE to create a unified content model
- 17. ADL SCORM • This model specifies the behaviour and aggregation of modular, interactive learning components, and makes extensive use of XML. Like IMS, SCORM is not simply concerned with metadata, but combines metadata with a number of other specifications that deal with a variety of aspects of learning content and management.
- 18. Standards
- 19. IEEE LOM • IEEE LTSC LOM (http://ltsc.ieee.org) is the acronym for The Institute for Electrical and Electronics Engineers Learning Technologies Standards Committee, which creates and supports standards and best practices related to the technical aspects of e-learning., and is compatible with Dublin Core metadata
- 20. IEEE LOM • The IEEE LTSC is releasing the Learning Object Metadata, referred to as IEEE LTSC LOM P1484.12, as an approved standard. This standard is almost identical to the IMS metadata specification
- 22. ISO • ISO (http://jtc1sc36.org/#terms_of_reference) is the acronym for the International Standards Organization, a network of the national standards institutes of some 130 countries responsible for coordinating the development of international standards of all sorts
- 23. ISO • The Information Technology for Learning, Education, and Training Committee of the ISO supports the standardization of information and communications technologies for learning. This sub-group works closely with the IEEE LTSC. The standard number being used for educational metadata is IECJTC1 SC36
- 24. Why have interoperability? • Metadata is supposed to be interoperable when it is necessary to make a unified retrieval, resource description and resource utilization among resource systems defined by different metadata models
- 25. Three parts of metadata Rules Syntax Semantics The meaning of the each element. A metadata system usually names and interprets each metadata’s element Descriptive rules specify the method to evaluate elements specifies how elements are encoded in a machine-readable way
- 26. Problems settled through interoperability • Metadata Crosswalk or Metadata Mapping is featured as transmittable, the essence of which is that the elements and qualifiers in one metadata format can find the elements and qualifiers with the same function or meaning in another metadata format
- 27. Problems settled through interoperability • Metadata Open Search: Metadata interoperation can be realized by defining an acknowledged, both followed protocol. OAI (Open Archive Initiative) is a protocol proposed internationally to manage metadata interoperation to realize an application- independent interoperability framework among different organizations’ web information through the metadata harvesting model
- 28. Problems settled through interoperability • Semantic Metadata Interoperation: The problem of semantic loss has not been satisfactorily solved. Metadata standards can be automatically interoperated without semantic loss as long as the structures of knowledge in the specific field are clearly described, because the ontology itself can describe conceptions and relationships through many properties
- 29. Layers of Interoperability No Type Medium 1 Protocol TCP/IP, HTTP 2 Binding HTML, XML, RDF 3 Metadata Scheme LOM, Dublin Core 4 Semantic Ontologies, Classifications, Vocabularies, Taxonomies Interoperability is not a “Yes” or “No” question but it involves levels…
- 30. Fifth Floor Metadata Specifications & Standards Next stop: 6th Floor – Metadata Tools 5