IMS AccessForAll Meta-data XML Binding Version 1.0 Final Specification

Copyright © 2004 IMS Global Learning Consortium, Inc. All Rights Reserved.
The IMS Logo is a trademark of IMS Global Learning Consortium, Inc.
Document Name: IMS AccessForAll Meta-data XML Binding
Revision: 12 July 2004

IPR and Distribution Notices

Recipients of this document are requested to submit, with their comments, notification of any relevant patent claims or other intellectual property rights of which they may be aware that might be infringed by any implementation of the specification set forth in this document, and to provide supporting documentation.

IMS takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on IMS's procedures with respect to rights in IMS specifications can be found at the IMS Intellectual Property Rights web page: http://www.imsglobal.org/ipr/imsipr_policyFinal.pdf.

Copyright © 2004 IMS Global Learning Consortium. All Rights Reserved.

Permission is granted to all parties to use excerpts from this document as needed in producing requests for proposals.

Use of this specification to develop products or services is governed by the license with IMS found on the IMS website: http://www.imsglobal.org/license.html.

The limited permissions granted above are perpetual and will not be revoked by IMS or its successors or assigns.

THIS SPECIFICATION IS BEING OFFERED WITHOUT ANY WARRANTY WHATSOEVER, AND IN PARTICULAR, ANY WARRANTY OF NONINFRINGEMENT IS EXPRESSLY DISCLAIMED. ANY USE OF THIS SPECIFICATION SHALL BE MADE ENTIRELY AT THE IMPLEMENTER'S OWN RISK, AND NEITHER THE CONSORTIUM, NOR ANY OF ITS MEMBERS OR SUBMITTERS, SHALL HAVE ANY LIABILITY WHATSOEVER TO ANY IMPLEMENTER OR THIRD PARTY FOR ANY DAMAGES OF ANY NATURE WHATSOEVER, DIRECTLY OR INDIRECTLY, ARISING FROM THE USE OF THIS SPECIFICATION.

Table of Contents

1. Introduction

This document is the XML Binding of the UML information model described in the AccessForAll Information Model document [ACCMD, 04a]. For more background and context information see the Accessibility Meta-Data Overview document [ACCMD, 04d].

1.1 Structure of this Document

The structure of this document is:

1.2 Nomenclature

1.3 References

2. XML Binding

This binding document describes the binding of the AccessForAll Meta-data (ACCMD) Information Model to XML version 1.0 and is normative for any XML instance that claims to use this binding, whether by reference to the specification or by declaration of the namespace reserved by the specification. In cases of error or omission, the Information Model takes precedence. The ACCMD XML Binding includes an XSD control document using W3C Schema Language that should be used in implementations.

This section also contains several tables. The tables map the elements by number and name as listed in the ACCMD Information Model specification to the XML Schema entity used to represent it in the XML Schema binding. The Schema entity's name, kind of structure, and type are provided. Note that all "usage" attributes are of type "usageType"; this is not explicitly noted in the table.

The ACCMD Information Model identifies data elements in a dot-delimited enumeration and by name. The dot-delimited enumeration typifies the relationship of elements to each other, where elements with a numeral following a 'dot' are subordinate to elements that share the same numeric value to the left of a dot. The enumeration typically does not imply a strict sequence or order of occurrence. It merely implies a group relationship.

The tables also include references to additional XML Schema structures used to properly express the relationships or controlled lists of <accessibility> element values. These additional XML Schema structures are inserted into the tables in proximity to the <accessibility> elements they describe.

XSD elements of type complexType and simpleType may be nested. All the tables do not show this nesting. Separate tables in this section provide the further details for nested elements defined as complexType or simpleType. In those tables, the element number from the Accessibility model and the XML Schema element name are used to associate a nested Schema structuring entity with the appropriate element from the Accessibility model.

2.1 Overview

The following sections break down the XML binding in a manner designed to be as understandable and readable as possible. The core classes are primary, equivalent, and the separate compliance class.

2.2 Primary

2.3 Equivalent

2.4 Content

Many of the sub-sections of the content element are namespaced in from the Access for All Learner Information Package (ACCLIP) specification version 1.0 [ACCLIP, 03].

captionType and acclip:alternativesToVisual are broken out separately as they are sufficiently complex and/or deep to warrant their own section.

2.5 captionType

This element is namespaced into the specification from the IMS ACCLIP version 1.0 specification. For more details see that specification [ACCLIP, 03]. In this section we are only detailing where the ACCMD Information Model intersects with the XML Binding.

2.6 alternativesToVisual

This element is namespaced into the specification from the IMS ACCLIP version 1.0 specification. For more details see that specification [ACCLIP, 03]. In this section we are only detailing where the ACCMD Information Model intersects with the XML Binding.

2.7 Attributes of Complex Types

3. Extensibility and Related Issues

This section is not normative.

Extensibility and related issues deal with the concept of modularity, reusability etc.

3.1 Extension of the ACCMD model

If ACCMD does not provide the expressiveness required, then the recommended approach is to use ACC with extensions, preferably agreed in a community of practice. This approach:

• Avoids proliferation of exchange models with a great deal of similarity at a semantic level;
• May allow a user of a system that is ignorant of the extensions to gain some benefit from a degraded but non-zero performance.

The manner of extension is binding-dependent. The ACCMD XML Binding ex plains how XML 1.0 documents using W3C XML Schema Data Language can be extended such that graceful degradation of performance is enabled.

3.2 Extension Statements

Vendors making use of extensions to ACCMD should clearly identify the function and form of the extensions in order for users of data and software to understand the likely degradation of behavior in systems not supporting the extensions.

4. ACCMD Conformance

A Conformance document for Data Portability and Interoperability. This conformance specification addresses accessibility meta-data requirements, such as mandatory and optional items. Conformance for continuity of meta-data during import/export cycles will be augmented if conformance associated with IEEE LOM and DC does not meet requirements. It is anticipated that conformance for interoperability (i.e., runtime exchange of meta-data instances) will reference the IMS DRI specification [DRI, 03], as it appears that the characteristics of the data in this scope are not unique with respect to exchange. See Figure 4.1.

An Intra-Application Conformance document for Behaviors within Applications supporting both ACCLIP and Learning Object accessibility meta-data. This document will describe the behavior of an application that provides a user interface to the user based on the presence of both ACCLIP and accessibility meta-data. For example, if a user is hearing-impaired and caption text is available for a video resource, then the application must display the caption text. See Figure 4.2.

Important note: The scope of this deliverable has been evaluated and the scope is limited to approximately ten specific behaviors based on specific combinations of ACCLIP and learning object meta-data combinations. The effort will be time-limited with subsequent versions, as needed, driven by subsequent charters based on requirements from implementation.

Note: "Applicable" is defined as relevant within the functional design of an application or content.

4.1 Conformance Specification for Portability and Interoperability

A 'tool' is defined as an application designed to work with one or more instances of content that support this specification. A conforming tool will:

• Conform to the applicable semantics of the information models (IEEE LOM or DC);
• Maintain all mandatory elements in the profile during import/export cycles;
• Support all of the mandatory elements in the profile that are applicable to the subset of content instances for which the tool is designed to manipulate;
• Support all applicable behaviors as described in the IMS DRI specification;
• Support one or more mappings as described from IEEE and DC;
• Support one or more non-mandatory elements as described in the Information Model, profile, and Binding(s).

4.2 Content Instances

A content instance is defined as an object (such as an instructional module), or asset (such as an MPEG file), that supports this specification. A conforming content instance will:

• Conform to the applicable semantics of the information model in the IEEE LOM or DC;
• Support the applicable mandatory elements in the profile;
• Support all applicable behaviors as described in the IMS DRI specification;
• Support one or more bindings;
• Support one or more non-mandatory elements as described in the Information Model, profile, and Binding(s).

4.3 Conformance Specification for Behaviors within Applications Supporting Both AccessForAll Profile

A conforming application or content will:

• Conform to accessibility meta-data conformance requirements;
• Conform to ACCLIP;
• Support all applicable behaviors described in the "Intra-Application Conformance".

About This Document

List of Contributors

The following individuals contributed to the development of this document:

Revision History

Index

A
AccessForAll 1, 2, 3, 4
Accessibility 1, 2, 3

B
Behavior 1, 2, 3
Binding 1, 2

C
Conformance 1, 2

D
Dublin Core 1, 2, 3

E
Extension 1

I
IEEE 1, 2, 3
IMS International Conformance Program 1
IMS Specifications
     AccessForAll Meta-data 1, 2, 3, 4
     Content Packaging 1
     Digital Repositories Interoperability 1, 2, 3
     Learner Information Package 1
     Learner Information Package Accessibility for LIP 1, 2, 3, 4, 5, 6
     Vocabulary Definition Exchange 1
Interoperability 1

L
Learning Object 1
LOM 1, 2, 3
LTSC 1

M
Meta-data 1, 2

N
Namespace 1
Normative 1, 2

P
Profile 1, 2

R
Resource 1
RFC 1, 2

S
Structure 1

U
URI 1

V
Vocabulary 1

W
W3C 1, 2, 3

X
XML 1, 2, 3, 4, 5, 6, 7, 8
     XSD 1, 2, 3, 4, 5