ISO IEC 12785-2:2011 pdf – lnformation technology -Learning,education, and training-Content packaging一 Part 2:xML binding.
This part of ISO/IEC 12785 specifIes how to represent the ISOIIEC 12785-1 information model in XML, and details each element binding of the content packaging XML schema
2 Normative references
The following referenced documents are indispensable for the application of this document. For dated references, Only the edition cited applies. For undated references, the latest edition of the referenced document (Induding any amendments) applies.
ISO1IEC 12785-1:2009. Infotmotion technoiogy — Learning. education, end framing — Content packaging — Pail 1: Information model
3 Terms and definitions
For the purposes of this document, the following terms and definitions appty.
3.1
binding
XML data binding
means of representing the information in an XML document
NOTE See XML data b(idwig of Wik,edia: http.,’enwikipedia.orwikidXML data bàndin (retrieved November 18. 2009)
3.2
control fit.
single computer file that governs the binding of the Content Packaging Information Model to make it suitable for machine processing
NOTE A software component can refer to a control fde when asseesrig the validity of a bound instance of the riormahon modal or to guide the ueabon of a bound instance of the informabon model.
EXAMPLE A tile containing an XML schema can be used as a control rile for an XML binding of a manifest,
3.3
content
individual file or multiple files usable in learning, education and training
NOTE 1 A logical unit of usable (and reusable) information can be descnbed by a logical pecicage. NOTE 2 logical package can contain one or more units of content.
3.4
logIcal package
representation of one or more units of usable (and reusable) content
NOTE A logical padage encompasses the ui set of components described by the manifest and its child manifests. including the local components and the remote components included by reference.
IISOEC 12785-1:20091
3.5
namespace
XML narnespace identified by a URI reference
NOTE Namespace in Content Packaging follows W3C recommendation Nemespaces An XML. 1.0 (Second Edeion). IISO/IEC 12785-1:2009)
3.6
manifest
description of files and any logical relationships between them, contained or referenced in a content package
3.7
metadata
(content packaging) descriptive information about logical packages, logical organizations, content and files
NOTE I Metadata can be assigned to any of the core structures lelh.n the logical package, including U’ie manliest. NOTE 2 Any bending of a metadata object permitted. Each object of metadata can be local or remote.
IISO11EC 12785-1:2009)
3.8
organization
logical relationships, such as a hierarchical tree, among urwt of content
NOTE More than one logical organization can be described In a manifest.
3.9
package
unit of usable (and reusable) content
NOTE I This can be part of a learning course that has instruciional relevance outside of a content aggregation and can be delivered Independently, as an ente learning course or as a collection of learning courses.
NOTE 2 A package Is able to stand.alone, that Is, it contains all the Inlormatlon needed to use the contents for learning, education, and training when it has been unpacked.
3.10
resource
(content packaging) one URL entry point and zero or more references to files that are required before the content is launched
NOTE The files described by a resource can be local or remote.
3.11schema
XML Schema
description of a class of XML documents, expressed in terms of constraints on the structure and content ofthose documents
NOTE1 For more information see http-lwww.w3c.orgXMLISchema,
NOTE2 XML Schema in Content Packaging follaws w3C recommendation XML Schema.
NOTE3 The definition refers to the concept of a schema in an XML context, as well as a specific language for creatingsuch schemas: the W3C XML Schema. The “IMS Content Packaging XML XSD” is an application of the W3C XMLSchema language.
3.12
unit of content
file or grouping of files which can be represented within a manifest
3.13
XML validation
process whereby documents written in XML(eXtensible Markup Language) are verified against the definedstructure
NOTE
Strict validation in XML means that it must follow the rules dictated by an XML schema.