Sharable Content Object Reference Model. SCORM is a specification of the Advanced Distributed Learning (ADL) Initiative from the Office of the United States Secretary of Defense.
SCORM versions[edit] SCORM 1.1[edit] SCORM 1.1 is the first production version. It used a Course Structure Format XML file based on the AICC specifications to describe content structure, but lacked a robust packaging manifest and support for metadata. Quickly abandoned in favor of SCORM 1.2. SCORM 1.2[edit] This was the first version that was widely used. SCORM 2004[edit] This is the current version. SCORM 2004 editions[edit] 3rd Edition (October 2005) — clarification of various conformance requirements and of the interaction between content objects and the runtime environment for sequencing; some new conformance requirements to improve interoperability.4th Edition Released (March 31, 2009) — more stringent interoperability requirements, more flexible data persistence.[2] XML data binding. XML data binding refers to a means of representing information in an XML document as a business object in computer memory.
This allows applications to access the data in the XML from the object rather than using the DOM or SAX to retrieve the data from a direct representation of the XML itself. Similarly, since objects in computer memory are not inherently sequential, and may include links to other objects (including self-referential links), XML data binding mappings often have difficulty preserving all the information about an object when it is marshalled to XML. An alternative approach to automatic data binding relies instead on hand-crafted XPath expressions that extract the data from XML.
This approach has a number of benefits. First, the data binding code only needs proximate knowledge (e.g., topology, tag names, etc.) of the XML tree structure, which developers can determine by looking at the XML data; XML schemas are no longer mandatory. Content package. Application profile. In computer science, an application profile is a set of metadata elements, policies, and guidelines defined for a particular application.[1] The elements may be from one or more element sets, thus allowing a given application to meet its functional requirements by using metadata from several element sets including locally defined sets.
For example, a given application might choose a subset of the Dublin Core that meets its needs, or may include elements from the Dublin Core, another element set, and several locally defined elements, all combined in a single schema. An application profile is not complete without documentation that defines the policies and best practices appropriate to the application. Content Packaging. IMS Content Packaging v1.2 Public Draft v2.0 specification describes data structures that can be used to exchange data between systems that wish to import, export, aggregate, and disaggregate packages of content.
IMS content packages enable exporting content from one learning content management system or digital repository and importing it into another while retaining information describing the media in the content package and how it is structured, such as a table of contents or which web page to show first. The IMS Content Packaging Specification focuses on the packaging and transport of resources but doesn’t determine the nature of those resources. This is because the specification allows adopters to gather, structure, and aggregate content in an unlimited variety of formats. Content Packaging v1.2 is undergoing standardisation by ISO/IEC. We expect the ISO/IEC version to be voted on as a full standard in late November 2009. Please post comments or questions at. Dublin Core. Logo image of DCMI, which formulates Dublin Core The Dublin Core Schema is a small set of vocabulary terms that can be used to describe digital resources (video, images, web pages, etc.), as well as physical resources such as books or CDs, and objects like artworks.[1] The full set of Dublin Core metadata terms can be found on the Dublin Core Metadata Initiative (DCMI) website.[2] The original set of 15 classic[3] metadata terms, known as the Dublin Core Metadata Element Set (DCMES),[4] is endorsed in the following standards documents: IETF RFC 5013[5]ISO Standard 15836-1:2017[6]NISO Standard Z39.85[7] Dublin Core metadata may be used for multiple purposes, from simple resource description to combining metadata vocabularies of different metadata standards, to providing interoperability for metadata vocabularies in the linked data cloud and Semantic Web implementations.
ISO/IEC 19788. ISO/IEC 19788 Information technology – Learning, education and training – Metadata for learning resources[1] is a multi-part standard prepared by subcommittee SC36 of the Joint Technical Committee ISO/IEC JTC1, Information Technology for Learning, Education and Training.
This committee was created to deal with the consequences of substantial overlap in areas of standardization done at the International Organization for Standardization (ISO) and the International Electrotechnical Commission. Purpose[edit] The ISO 15836 Dublin Core (DC) and the IEEE 1484.12.1-2002 Learning Object Metadata (LOM) are widely used to describe learning resources. However, interoperability among DC data sets is challenging, as best practices are only recommended. Instead of using ISO 8601, a DC Date element can be written in plain language and not processed by queries.