IMS Resource List Interoperability
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 Resource List Interoperability Conformance Requirements
Revision: 8 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.
This section is not normative.
This document is the IMS Resource List Interoperability (RLI) Specification version 1.0. As such, it forms one of the set that comprises the specification, each with distinct scope.
Describes the core aspects of the specification and contains parts that are normative for any binding claiming to use this Information Model. It contains details of: semantics, structure, data types, value spaces, multiplicity, and obligation (i.e., whatever mandatory or optional).
Describes a binding of the Information Model to XML version 1.0, as well as binding of the abstract service interface to web services expressed as WSDL. These bindings are normative for any XML instance that claims to use these bindings, 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 IMS RLI Binding is released with a control document using W3C XML Schema 1.0 that should be used in implementation.
Provides non-normative guidance on application of the Information Model and Binding. This includes reference to existing practice in handling information that this specification seeks to support and guidance on practices that will promote interoperability and durability. It also includes examples to illustrate how the conceptual framework maps to practical uses, and to identify the relationship between this specification and related IMS specifications. Implementers are encouraged, but not required, to follow guidance in this part of the specification.
Provides a set of testable statements that may be used in relation to applications of the Information Model and Binding. These statements may form a basis of formal conformance testing and certification or informal assertions. This document makes no statement about the formal processes or methods of certification, it only deals with criteria.
The terms defined in the RFC 2119 (IETF RFC 2119 - Key words for use in RFCs to Indicate Requirement Levels) are used with the meaning there defined in any section of this document stated to be "normative".
||IMS Resource List
Interoperability Information Model v1.0,
A.Jackl, IMS Global Learning Consortium, Inc., July
||IMS Resource List
Interoperability Binding v1.0, A.Jackl, IMS
Global Learning Consortium, Inc., July 2004
||IMS Resource List
Interoperability Best Practice and Implementation Guide
v1.0, A.Jackl, IMS Global Learning
Consortium, Inc., July 2004
Standard for Learning Object Metadata, http://ltsc.ieee.org
||Using IMS Content
Packaging to Package Instances of LIP and Other IMS
Specifications, v1.0, B.Olivier, M.McKell,
IMS Global Learning Consortium, Inc., August 2001.
Location-Independent, Resource Identifier Implementation Handbook
v1.0, IMS Global Learning Consortium, Inc., April
||Tags for the
Identification of Languages, http://www.ietf.org/rfc/rfc1766.txt
||Key words for use in
RFCs to Indicate Requirement Levels, http://www.ietf.org/rfc/rfc2119.txt
Identifiers (URI): Generic Syntax, http://www.ietf.org/rfc/rfc2396.txt
||Format for Literal
IPv6 Addresses in URLs, http://www.ietf.org/rfc/rfc2732.txt
||W3C XML 1.0
Whereas the Information Model used plain formatted English terms for element names, since the language of the specification is English, the Binding uses tokens for elements names. These are derived from the Information Model element names. Translators of the Information Model may change the names used in that document but they must map to XML Binding element names exactly as presented in the specification; translation of XML element names is not permitted. This restriction will ensure machine-level interoperability of data.
Annotations and comment strings in the official IMS RLI XSD files appear in at least US English. Annotations and comments in other languages may be added as deemed necessary by IMS stakeholders and such a revision must only be published by IMS. Since interoperability depends on trustworthy binding instances, only exact copies of the official IMS binding instance should be publicly circulated. Any entity other than IMS that needs localized annotations or comments should create a separate document with such annotations and comments, and reference the official IMS binding instance rather than circulating a binding instance that is different to, but could be believed to be identical to, the official IMS version.
The Binding document may be translated except for the representations of:
The essence of this section is that XML instance expressing the same information should not differ if created by readers of different localized versions of this specification.
Localization of this document shall not cause any change in specification version numbering or binding revision instance numbering.
This section is normative.
Conformance statements are divided into sections for the Information Model and for the Binding. It is conceptually cleaner to identify statements that are binding independent. Statements are broken out into those that apply to the Information Model and those that apply to the Binding.
Conformances statements are made at a syntactic level only - i.e., no statement attempts to provide criteria for the data being meaningful.
If data is relayed without change of content then the processor may be described as a transmitter of data. The content is not dependent upon the binding.
This section is not normative and should not be interpreted to guide any formal certification or testing process; it provides some outline recommendations for making unverified assertions.
Claims of conformance should provide a statement, detailing the level of conformance, substantially similar to the information outlined below.
Conformance would typically be presented in two parts:
The "conformance summary" should include clear indications of the classes of vocabulary that are supported and include comment on semantic issues (i.e., meaningfulness of data).
The form of an interoperability statement will probably vary but should at least attempt to identify all of the conformance statements in this document and for identifying:
Specific applications are expected to define more detailed application profiles, especially in relation to use of meta-data.
||IMS Resource List
Interoperability Conformance Requirements
||Oliver Heyer (UC
Berkeley), Mladen Maljkovic (WebCT)
||08 July 2004
describes the Conformance Statements applicable to the Resource
List Interoperability specification.
||This document has been
approved by the IMS Technical Board and is made available for
|To register any
comments or questions about this specification please visit:
The following individuals contributed to the development of this document:
||IMS Global Learning
|Version No.||Release Date||Comments|
|Base Document 1.0
||11 November 2003
||Initial version of the
Resource List Interoperability specification.
|Public Draft 1.0
||31 May 2004
||Public Draft version
of the Resource List Interoperability Conformance
||08 July 2004
||This is the formal
Final version of the IMS Resource List Interoperability
Binding 1, 2, 3
Conformance 1, 2
Learner Information Package 1
Resource List Interoperability 1, 2, 3, 4
Resources List Interoperability 1
Interoperability 1, 2, 3
Meta-data 1, 2, 3
Namespace 1, 2, 3
Normative 1, 2, 3
Resource list 1, 2
Resources list 1
RFC 1, 2, 3
Structure 1, 2
W3C 1, 2, 3
XML 1, 2, 3, 4
IMS Global Learning Consortium, Inc.
("IMS") is publishing the information contained in this IMS
Resource List Interoperability Conformance Requirements
("Specification") for purposes of scientific, experimental,
and scholarly collaboration only.
IMS makes no warranty or representation regarding the accuracy or completeness of the Specification.
This material is provided on an "As Is" and "As Available" basis.
The Specification is at all times subject to change and revision without notice.
It is your sole responsibility to evaluate the usefulness, accuracy, and completeness of the Specification as it relates to you.
IMS would appreciate receiving your comments and suggestions.
Please contact IMS through our website at http://www.imsglobal.org
Please refer to Document Name: IMS Resource List Interoperability Conformance Requirements Revision: 08 July 2004