Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
BS ISO IEC 12785 — Learning Education and Training Content Packaging Standard Series (Information Model and XML Binding)
Information Technology — Learning, Education, and Training — Content Packaging: Information Model and XML Binding
🎓 BS ISO/IEC 12785 is a content packaging standard for learning, education, and training (LET) developed by ISO/IEC JTC 1/SC 36 and adopted by the British Standards Institution (BSI) as a UK national standard. This batch includes ISO/IEC 12785-1:2009 (Information model) and ISO/IEC 12785-2:2011 (XML binding), providing a standardised framework for packaging, exchanging, and interoperating learning content.
💡 The core value of content packaging is “package once, use anywhere”: encapsulating learning resources, organisational structure, and metadata into a standardised content package, enabling interchange of learning content between different LMSs (learning management systems) and content vendors.
1. Series Overview and Positioning 📌
Content packaging describes how to organise learning objects (resource files) into distributable, importable content packages. The series comprises several parts: Part 1 defines the information model, Part 2 defines the XML binding, and later parts cover interoperability, registration, and mixed media. The two parts in this batch cover the “model + encoding” core layers.
| Standard | Title | Year | Core Content |
|---|---|---|---|
| BS ISO/IEC 12785-1:2009 | Information model | 2009 | Content package structure, manifest, resources, and metadata model |
| BS ISO/IEC 12785-2:2011 | XML binding | 2011 | XML schema documents and global declarations for the core content packaging binding |
⚠️ Content packaging shares the same philosophy as the widely used SCORM standard: SCORM’s Content Aggregation Model (CAM) is essentially built on the content-packaging concepts of ISO/IEC 12785 — understanding this series helps master the SCORM foundations.
2. Information Model (Part 1) 📦
Part 1 defines the information model of learning content packages. Core elements include:
- Content package: composed of a manifest and physical resource files.
- Manifest: the manifest file describing package organisation, containing metadata, organisational structure (tree), and resource references.
- Resource: entries pointing to actual learning assets (e.g. HTML, PDF, video).
- Metadata: descriptive attributes of the package, organisation, and resources.
The information model defines the relationships and constraints among elements, forming the semantic basis of the XML binding.
| Model Element | Role | Example |
|---|---|---|
| Manifest | The package “table of contents” | imsmanifest.xml |
| Meta-data | Descriptive attributes | Title, language, author |
| Organizations | Learning content navigation structure | Chapter/unit tree |
| Resources | Physical file references | PDF courseware, video |
3. XML Binding (Part 2) 🧩
Part 2 binds the information model to XML representations, defining:
- Core content packaging binding description: mapping information model elements to XML elements and attributes.
- Schema document properties: version, namespace, and other properties of the XML Schema (XSD).
- Global declarations: e.g. the global definition of the manifest element for reuse in package documents.
- Global definitions: definitions and constraints of the complex types in the content package.
💡 The XML binding makes a content package a “machine-readable” interchange unit: an LMS parses the manifest to import the course structure and locate resource files, enabling cross-platform content distribution.
4. Key Technical Requirements ⚙️
- A content package shall contain a manifest file that correctly describes metadata, organisational structure, and resource references.
- Resource references shall point to physical files actually present in the package, with path resolution per the binding specification.
- XML binding documents shall conform to the defined schema, meeting XML namespace and schema-validation requirements.
- Internal resources and organisational structure shall remain consistent so that navigation and access work correctly after import.
⚠️ Common pitfalls: incorrect resource reference paths, mismatched manifest namespaces, and missing resource files all cause package import failures. Validate the manifest against the XML Schema and check all resource references during packaging and testing.
5. Engineering Practice 🛠️
- LMS content import/export: migrate courses between LMSs using standard content packages.
- Content library management: manage, retrieve, and reuse learning objects as package units.
- Cross-vendor interoperability: vendors package to the standard, platforms import per the standard, reducing lock-in.
- Offline distribution: package content for installation in offline environments (branch campuses, mobile terminals).
6. Frequently Asked Questions ❓
❓ Q: What is “content packaging”?
A: Content packaging is the method of encapsulating learning resources, organisational structure, and metadata into a standardised content package so that content can be exchanged and reused across learning platforms.
A: Content packaging is the method of encapsulating learning resources, organisational structure, and metadata into a standardised content package so that content can be exchanged and reused across learning platforms.
❓ Q: How do the information model and the XML binding relate?
A: The information model defines the semantic structure and elements of the content package; the XML binding defines their XML representation, making the package a machine-readable, validatable interchange unit.
A: The information model defines the semantic structure and elements of the content package; the XML binding defines their XML representation, making the package a machine-readable, validatable interchange unit.
❓ Q: Which element acts as the package “table of contents”?
A: The manifest plays the role of table of contents: it describes metadata, organisational structure (navigation tree), and resource references, which the LMS uses to import the course.
A: The manifest plays the role of table of contents: it describes metadata, organisational structure (navigation tree), and resource references, which the LMS uses to import the course.
🔍 Q: How does this relate to SCORM?
A: SCORM’s Content Aggregation Model (CAM) builds on content-packaging concepts closely related to the ISO/IEC 12785 information model; understanding this series helps master SCORM’s foundations.
A: SCORM’s Content Aggregation Model (CAM) builds on content-packaging concepts closely related to the ISO/IEC 12785 information model; understanding this series helps master SCORM’s foundations.