ISO/IEC 12785-2:2011

Information technology — Learning, education, and training — Content packaging — Part 2: XML binding

ISO/IEC 12785-2:2011 specifies how to express the ISO/IEC 12785-1 information model in XML.

Technologies de l'information — Apprentissage, éducation et formation — Paquetage du contenu — Partie 2: Liaison XML

General Information

• Status: Published
• Publication Date: 13-Nov-2011
• ICS: 35.240.90 - IT applications in education
• ICS: 35.240.99 - IT applications in other fields
• Technical Committee: ISO/IEC JTC 1/SC 36 - Information technology for learning, education and training
• Drafting Committee: ISO/IEC JTC 1/SC 36/WG 4 - Management and delivery
• Current Stage: 9093 - International Standard confirmed
• Completion Date: 04-Oct-2022

Standards Content (Sample)

INTERNATIONAL ISO/IEC
STANDARD 12785-2
First edition
2011-11-15


Information technology — Learning,
education, and training — Content
packaging —
Part 2:
XML binding
Technologies de l'information — Apprentissage, éducation et
formation — Paquetage du contenu —
Partie 2: Liaison XML





Reference number
ISO/IEC 12785-2:2011(E)
©
ISO/IEC 2011

---------------------- Page: 1 ----------------------
ISO/IEC 12785-2:2011(E)

COPYRIGHT PROTECTED DOCUMENT


©  ISO/IEC 2011
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or
ISO's member body in the country of the requester.
ISO copyright office
Case postale 56  CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail [e-mail]
Web www.iso.org
Published in Switzerland

ii © ISO/IEC 2011 – All rights reserved

---------------------- Page: 2 ----------------------
ISO/IEC 12785-2:2011(E)
Contents Page
Foreword . iv
Introduction . v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Abbreviated terms . 3
5 XML schema documentation . 4
5.1 Core content packaging binding description . 4
5.1.1 Schema document properties . 4
5.1.2 Global declarations . 5
5.1.2.1 Element: manifest . 5
5.1.3 Global definitions . 6
5.1.3.1 Complex Type: Dependency.Type . 6
5.1.3.2 Complex Type: File.Type . 7
5.1.3.3 Complex Type: Item.Type . 8
5.1.3.4 Complex Type: Manifest.Type . 10
5.1.3.5 Complex Type: ManifestMetadata.Type . 11
5.1.3.6 Complex Type: Metadata.Type . 12
5.1.3.7 Complex Type: Organization.Type . 13
5.1.3.8 Complex Type: Organizations.Type . 15
5.1.3.9 Complex Type: Resource.Type . 16
5.1.3.10 Complex Type: Resources.Type . 17
5.1.3.11 Model Group: grpStrict.any . 18
5.2 Content packaging extension binding description . 19
5.2.1 Schema document properties . 19
5.2.2 Global declarations . 20
5.2.2.1 Element: ipointer . 20
5.2.2.2 Element: lingualTitle . 21
5.2.2.3 Element: variant . 21
5.2.3 Global definitions . 22
5.2.3.1 Complex Type: IPointer.Type . 22
5.2.3.2 Complex Type: LingualTitle.Type . 24
5.2.3.3 Complex Type: Metadata.Type . 24
5.2.3.4 Complex Type: Variant.Type . 25
5.2.3.5 Model Group: grpStrict.any . 26
6 Using schematron . 27
Annex A (informative) Document Provenance . 28
Annex B (informative) Listing of the XSDs . 29
Bibliography . 30

© ISO/IEC 2011 – All rights reserved iii

---------------------- Page: 3 ----------------------
ISO/IEC 12785-2:2011(E)
Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that are members of
ISO or IEC participate in the development of International Standards through technical committees
established by the respective organization to deal with particular fields of technical activity. ISO and IEC
technical committees collaborate in fields of mutual interest. Other international organizations, governmental
and non-governmental, in liaison with ISO and IEC, also take part in the work. In the field of information
technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of the joint technical committee is to prepare International Standards. Draft International
Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as
an International Standard requires approval by at least 75 % of the national bodies casting a vote.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights.
ISO/IEC 12785-2 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology,
Subcommittee SC 36, Information technology for learning, education and training.
ISO/IEC 12785 consists of the following parts, under the general title Information technology — Learning,
education, and training — Content packaging:
— Part 1: Information model
— Part 2: XML binding
— Part 3: Best practice and implementation guide

iv © ISO/IEC 2011 – All rights reserved

---------------------- Page: 4 ----------------------
ISO/IEC 12785-2:2011(E)
Introduction
This part of ISO/IEC 12785 will be used as the basis for the production of the following documents:
• ISO/IEC 12785-3 (Best practice and implementation guide);

1)
• Content Packaging XML XSD.
This part of ISO/IEC 12785 details how the ISO/IEC 12785-1 information model should be represented using
XML schema. The content packaging binding is contained in two XML schemas and two vocabulary files. The
vocabulary files are instances of the IMS Vocabulary Definition Exchange specification. ISO/IEC 12785-3
provides non-normative guidance on how to use the binding and information model. For a conceptual
overview of ISO/IEC 12785, see ISO/IEC 12785-1. For a discussion of potential applications, see
ISO/IEC 12785-3. Conformance to ISO/IEC 12785 is addressed within ISO/IEC 12785-1.


1) This XML schema definition can be accessed from: http://www.imsglobal.org/content/packaging/index.html.
© ISO/IEC 2011 – All rights reserved v

---------------------- Page: 5 ----------------------
INTERNATIONAL STANDARD ISO/IEC 12785-2:2011(E)

Information technology — Learning, education, and training —
Content packaging —
Part 2:
XML binding
1 Scope
This part of ISO/IEC 12785 specifies how to represent the ISO/IEC 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 (including any amendments) applies.
ISO/IEC 12785-1:2009, Information technology — Learning, education, and training — Content packaging —
Part 1: Information model
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
3.1
binding
XML data binding
means of representing the information in an XML document
NOTE See XML data binding of Wikipedia: http://en.wikipedia.org/wiki/XML_data_binding (retrieved November 18,
2009).
3.2
control file
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 file when assessing the validity of a bound instance of the
information model or to guide the creation of a bound instance of the information model.
EXAMPLE A file containing an XML schema can be used as a control file for an XML binding of a manifest.
© ISO/IEC 2011 – All rights reserved 1

---------------------- Page: 6 ----------------------
ISO/IEC 12785-2:2011(E)
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 described by a logical package.
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 package encompasses the full set of components described by the manifest and its child manifests,
including the local components and the remote components included by reference.
[ISO/IEC 12785-1:2009]
3.5
namespace
XML namespace identified by a URI reference
NOTE Namespace in Content Packaging follows W3C recommendation Namespaces in XML 1.0 (Second Edition).
[ISO/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 1 Metadata can be assigned to any of the core structures within the logical package, including the manifest.
NOTE 2 Any binding of a metadata object is permitted. Each object of metadata can be local or remote.
[ISO/IEC 12785-1:2009]
3.8
organization
logical relationships, such as a hierarchical tree, among unit of content
NOTE More than one logical organization can be described in a manifest.
3.9
package
unit of usable (and reusable) content
NOTE 1 This can be part of a learning course that has instructional relevance outside of a content aggregation and can
be delivered independently, as an entire learning course or as a collection of learning courses.
NOTE 2 A package is able to stand-alone; that is, it contains all the information 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.
2 © ISO/IEC 2011 – All rights reserved

---------------------- Page: 7 ----------------------
ISO/IEC 12785-2:2011(E)
3.11
schema
XML Schema
description of a class of XML documents, expressed in terms of constraints on the structure and content of
those documents
NOTE 1 For more information see http://www.w3c.org/XML/Schema.
NOTE 2 XML Schema in Content Packaging follows W3C recommendation XML Schema.
NOTE 3 The definition refers to the concept of a schema in an XML context, as well as a specific language for creating
such schemas: the W3C XML Schema. The "IMS Content Packaging XML XSD" is an application of the W3C XML
Schema 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 defined
structure
NOTE Strict validation in XML means that it must follow the rules dictated by an XML schema.
4 Abbreviated terms
CPIM Content Packaging Information Model
I-BAT IMS Binding Auto-generation Tool-kit
LET Learning, Education, and Training
MDA Model Driven Architecture
PIM Protocol Independent Model
PSM Platform Specific Model
UML Unified Modeling Language
VDEX Vocabulary Definition Exchange
W3C World Wide Web Consortium
XMI XML Metadata Interchange
XML eXtensible Mark-up Language (W3C XML)
XSD XML Schema Definition
XSL Extensible Stylesheet Language
XSLT XSL Transformations
© ISO/IEC 2011 – All rights reserved 3

---------------------- Page: 8 ----------------------
ISO/IEC 12785-2:2011(E)
5 XML schema documentation
5.1 Core content packaging binding description
5.1.1 Schema document properties
The following subclauses outline the characteristics of each element of the content packaging XML schema
2)
binding for core elements in tabular form. The same information is also presented as an XSD in Annex B.1.
In accordance with the IMS Global Learning Consortium (GLC) Namespace Policy [IMS-NAMESPACE]
specified in IMS Content Packaging XML Binding, the “name” of an element is appended to a IMS GLC
namespace URI to construct a Uniform Resource Identifier as a globally unique identifier for that element. The
use of element names and URIs in the context of different implementation technologies is explained in
ISO/IEC 12785-2.
To describe XML instance representation of each element declared namespaces are as follows:
Prefix
Namespaces
Default namespace
http://www.imsglobal.org/xsd/imscp_v1p1
xml
http://www.w3.org/XML/1998/namespace
xs
http://www.w3.org/2001/XMLSchema
xsi
http://www.w3.org/2001/XMLSchema-instance

Schema component representation:
elementFormDefault="qualified" attributeFormDefault="unqualified">
schemaLocation="http://www.w3.org/2001/xml.xsd"/>
...

The following subclauses was created using the schema documentation tool provided as part of the Oxygen
product. To describe logical diagram used notations are as follows:
: xs:attribute
 @
: xs:sequence

: xs:anyAttribute

: xs:any namespace


2) The core refers to all those elements that were used in the IMS Content Packaging specification versions prior to
version 1.2 which is source of ISO/IEC 12785.
4 © ISO/IEC 2011 – All rights reserved

---------------------- Page: 9 ----------------------
ISO/IEC 12785-2:2011(E)
: xs:group

: property for zero to one
 0.1
: property for zero to unbounded
 0.∞
: xs:complexType


5.1.2 Global declarations
5.1.2.1 Element: manifest
manifest
Name
Type Manifest.Type
no
Nillable
Abstract no
Logical diagram of manifest:

© ISO/IEC 2011 – All rights reserved 5

---------------------- Page: 10 ----------------------
ISO/IEC 12785-2:2011(E)
XML instance representation:
identifier=" xs:ID [1]"
version=" xs:string [0.1]"
xml:base="[0.1]"
Allow any attributes from a namespace other than this schema's namespace (strict validation).
>
ManifestMetadata.Type [0.1]
Organizations.Type [1]
Resources.Type [1]
Manifest.Type [0.*]
Allow any elements from a namespace other than this schema's namespace (strict validation). [0.*]

Diagram:

Schema component representation:

5.1.3 Global definitions
5.1.3.1 Complex Type: Dependency.Type
Super-types: None
Sub-types: None

Dependency.Type
Name
Used by (from the
Complex Type Resource.Type
same schema
document)
no
Abstract
6 © ISO/IEC 2011 – All rights reserved

---------------------- Page: 11 ----------------------
ISO/IEC 12785-2:2011(E)
A dependency element provides a way to associate another collection of file
Documentation
references within the scope of the dependency element's parent resource
element.
Shared file references can be declared once and associated many times
through a Dependency element.
This element represents a binding of the kinds of child objects defined for
3)
Dependency.[ Extension ] (see subclause 6.6.4 of ISO/IEC 12785-1:2009).

XML instance representation:
<.
identifierref=" xs:string [1]"
Allow any attributes from a namespace other than this schema's namespace (strict validation).
>
Allow any elements from a namespace other than this schema's namespace (strict validation). [0.*]

Diagram:

Schema component representation:







5.1.3.2 Complex Type: File.Type
Super-types: None
Sub-types: None

File.Type
Name
Used by (from the
Complex Type Resource.Type
same schema
document)
no
Abstract

3) Symbol '[ ]' means children elements.
© ISO/IEC 2011 – All rights reserved 7

---------------------- Page: 12 ----------------------
ISO/IEC 12785-2:2011(E)
A file element declares a reference to a file. The reference may be relative to
Documentation
the Package containing the file element or absolute (external to the
Package).
A file element may contain child extensions declaring alternative references
4)
to the same asset as that referenced by the file element's href attribute.
This element represents a binding of the kinds of child objects defined for
File.[ Metadata, Extension ] (see subclause 6.6.3 of ISO/IEC 12785-1:2009).

XML instance representation:
<.
href=" xs:anyURI [1]"
Allow any attributes from a namespace other than this schema's namespace (strict validation).
>
Metadata.Type [0.1]
Allow any elements from a namespace other than this schema's namespace (strict validation). [0.*]

Diagram:

Schema component representation:








5.1.3.3 Complex Type: Item.Type
Super-types: None
Sub-types: None


4) 'Asset' and 'asset references' refer to a variety of content packaging components that refer directly or indirectly to the
files that a particular logical package aggregates.
8 © ISO/IEC 2011 – All rights reserved

---------------------- Page: 13 ----------------------
ISO/IEC 12785-2:2011(E)
Name Item.Type
Used by (from the
same schema Complex Type Organization.Type, Complex Type Item.Type
document)
Abstract no
An item element represents a structural node in a particular organization. An
Documentation
item element may be a parent or sibling of other Item elements, each one
representing a unique structural node.
An organization has no purpose unless it has at least one Item element.
This element represents a binding of the kinds of child objects of Item.[ Title,
Item, Metadata, Extension ] (see subclause 6.5.5 of ISO/IEC 12785-1:2009).

XML instance representation:
<.
identifier=" xs:ID [1]"
identifierref=" xs:string [0.1]"
isvisible=" xs:boolean [0.1]"
parameters=" xs:string [0.1]"
Allow any attributes from a namespace other than this schema's namespace (strict validation).
>
xs:string [0.1]
Item.Type [0.*]
Metadata.Type [0.1]
Allow any elements from a namespace other than this schema's namespace (strict validation). [0.*]

Diagram:


© ISO/IEC 2011 – All rights reserved 9

---------------------- Page: 14 ----------------------
ISO/IEC 12785-2:2011(E)
Schema component representation:













5.1.3.4 Complex Type: Manifest.Type
Super-types: None
Sub-types: None

Name Manifest.Type
Used by (from the
same schema Complex Type Manifest.Type, Element manifest
document)
Abstract no
A manifest element is a container for data structures whose contents
Documentation
describe a valid instance of ISO/IEC 12785-1.
A manifest element may contain and reference child manifest elements in
the same manifest document. The root manifest element defines an entire
content package. A child manifest element defines a semantically complete
subset of that Package.
This element represents a binding of the kinds of objects defined as
corresponding child manifests.[ ManifestMetadata, Organizations,
Resources, Manifest, Extension ] (see 6.4.1 of ISO/IEC 12785-1:2009).

XML instance representation:
<.
identifier=" xs:ID [1]"
version=" xs:string [0.1]"
xml:base="[0.1]"
Allow any attributes from a namespace other than this schema's namespace (strict validation).
>
ManifestMetadata.Type [0.1]
Organizations.Type [1]
Resources.Type [1]
Manifest.Type [0.*]
Allow any elements from a namespace other than this schema's namespace (strict validation). [0.*]


10 © ISO/IEC 2011 – All rights reserved

---------------------- Page: 15 ----------------------
ISO/IEC 12785-2:2011(E)
Diagram:


Schema component representation:













5.1.3.5 Complex Type: ManifestMetadata.Type
Super-types: None
Sub-types: None

Name ManifestMetadata.Type
Used by (from the
same schema Complex Type Manifest.Type
document)
Abstract no
© ISO/IEC 2011 – All rights reserved 11

---------------------- Page: 16 ----------------------
ISO/IEC 12785-2:2011(E)
This metadata element contains data structures that declare descriptive
Documentation
information about an entire Package.
One or more different metadata models may be declared as child extensions
of a metadata element.
The schema and schemaversion children define the kind or collection of
metadata models being used.
This element represents a binding of the kinds of child objects defined for
ManifestMetadata.[ Schema, SchemaVersion, MetadataModel ] (see
subclause 6.4.2 of ISO/IEC 12785-1:2009).

XML instance representation:
<.>
xs:string [0.1]
xs:string [0.1]
Allow any elements from a namespace other than this schema's namespace (strict validation). [0.*]

Diagram:


Schema component representation:







5.1.3.6 Complex Type: Metadata.Type
Super-types: None
Sub-types: None

Name Metadata.Type
Used by (from the
Complex Type Organization.Type, Complex Type Resource.Type, Complex
same schema
Type Item.Type, Complex Type File.Type
document)
Abstract no
12 © ISO/IEC 2011 – All rights reserved

---------------------- Page: 17 ----------------------
ISO/IEC 12785-2:2011(E)
An instance of the metadata element contains data structures that declare
Documentation
descriptive information about a metadata element's parent only.
One or more different metadata models may be declared as child extensions
of a metadata element.
This element represents a binding of the kinds of child objects defined for
Metadata.[ Extension ] (see subclause 6.7 of ISO/IEC 12785-1:2009).

XML instance representation:
<.>
xs:string [0.1]
xs:string [0.1]
Allow any elements from a namespace other than this schema's namespace (strict validation). [0.*]

Diagram:


Schema component representation:







5.1.3.7 Complex Type: Organization.Type
Super-types: None
Sub-types: None

Name Organization.Type
Used by (from the
same schema Complex Type Organizations.Type
document)
Abstract no
An organization element serves as a container for all those data structures
Documentation
that describe a particular view on all the information encapsulated by the
organization object's manifest grandparent object.
© ISO/IEC 2011 – All rights reserved 13

---------------------- Page: 18 ----------------------
ISO/IEC 12785-2:2011(E)
Multiple organization elements within the same parent organizations element
are equivalent in purpose: Each shows a different way for structuring the
same information declared within a grandparent manifest object.
This element represents a binding of the kinds of child objects defined for
Organization[ Title, Item, Metadata, Extension ] (see subclause 6.5.2 of
ISO/IEC 12785-1:2009).

XML instance representation:
<.
identifier=" xs:ID [1]"
structure=" xs:string [0.1]"
Allow any attributes from a namespace other than this schema's namespace (strict validation).
>
xs:string [0.1]
Item.Type [1.*]
Metadata.Type [0.1]
Allow any elements from a namespace other than this schema's namespace (strict validation). [0.*]

Diagram:


Schema component representation:

...