IMS Logo IMS Learning Resource Meta-Data XML Binding
Version 1.2.1 Final Specification
Copyright © 2001 IMS Global Learning Consortium, Inc. All Rights Reserved.
The IMS Logo is a trademark of IMS Global Learning Consortium, Inc.
Document Name: IMS Learning Resource Meta-Data XML Binding
Revision: 28 September 2001

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 © IMS Global Learning Consortium 2006. All Rights Reserved.

If you wish to distribute this document or use this document to implement a product or service, you must complete a valid license registration with IMS and receive an email from IMS granting the license. To register, follow the instructions on the IMS website: http://www.imsglobal.org/specificationdownload.cfm.

This document may be copied and furnished to others by Licensee organizations registered on the IMS website provided that the above copyright notice and this paragraph are included on all such copies. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to IMS, except as needed for the purpose of developing IMS specifications, under the auspices of a chartered IMS work group.

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/metadata/imsmdv1p2p1/imsmdv1p2p1speclicense.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
     1.1 XML Basics
           1.1.1 Elements
           1.1.2 Document Type Definitions
           1.1.3 XML Schemas
           1.1.4 Valid Character Sets
           1.1.5 Use of Attributes
           1.1.6 Lists
           1.1.7 Namespaces

2. Narrative Description of XML Binding
     2.1 <lom> Element
     2.2 <general> Element
           2.2.1 <identifier> Element
           2.2.2 <title> Element
           2.2.3 <catalogentry> Element
           2.2.4 <language> Element
           2.2.5 <description> Element
           2.2.6 <keyword> Element
           2.2.7 <coverage> Element
           2.2.8 <structure> Element
           2.2.9 <aggregationlevel> Element
     2.3 <lifecycle> Element
           2.3.1 <version> Element
           2.3.2 <status> Element
           2.3.3 <contribute> Element
     2.4 <metametadata> Element
           2.4.1 <identifier> Element
           2.4.2 <catalogentry> Element
           2.4.3 <contribute> Element
           2.4.4 <metadatascheme> Element
           2.4.5 <language> Element
     2.5 <technical> Element
           2.5.1 <format> element
           2.5.2 <size> element
           2.5.3 <location> element
           2.5.4 <requirement> element
           2.5.5 <installationremarks> Element
           2.5.6 <otherplatformrequirements> Element
           2.5.7 <duration> Element
     2.6 <educational> Element
           2.6.1 <interactivitytype> Element
           2.6.2 <learningresourcetype> Element
           2.6.3 <interactivitylevel> Element
           2.6.4 <semanticdensity> Element
           2.6.5 <intendedenduserrole> Element
           2.6.6 <context> Element
           2.6.7 <typicalagerange> Element
           2.6.8 <difficulty> Element
           2.6.9 <typicallearningtime> Element
           2.6.10 <description> Element
           2.6.11 <language> Element
     2.7 <rights> Element
           2.7.1 <cost> Element
           2.7.2 <copyrightandotherrestrictions> Element
           2.7.3 <description> Element
     2.8 <relation> Element
           2.8.1 <kind> Element
           2.8.2 <resource> Element
     2.9 <annotation> Element
           2.9.1 <person> Element
           2.9.2 <date> Element
           2.9.3 <description> Element
     2.10 <classification> Element
           2.10.1 <purpose> Element
           2.10.2 <taxonpath> Element
           2.10.3 <description> Element
           2.10.4 <keyword> Element

3. Elements Used Globally
     3.1 LangString Binding
     3.2 Date Binding
           3.2.1 <datetime> Element
           3.2.2 <description> Element
     3.3 Vocabulary Binding
           3.3.1 <source> Element
           3.3.2 <value> Element
     3.4 Vcard Binding

4. Special Handling Requirements for Meta-Data Elements
     4.1 Type Structures
           4.1.1 LangStringType
           4.1.2 DateType
           4.1.3 VocabularyType
     4.2 Language Elements
     4.3 TaxonPath Elements
     4.4 vCard Elements
     4.5 Keyword Elements

5. Extensibility
     5.1 Extensions with DTDs
     5.2 Extensions with XML Schema Definition Language

6. Using the vCard Specification

Appendix A - IMS Meta-Data RDF Binding
     A.1  Using RDF for Meta-Data as Compared to Pure XML
     A.2  Design Criteria for RDF Binding
     A.3  Relationship to Other Standards
           A.3.1   Dublin Core
           A.3.2   LOM/IMS XML
           A.3.3   vCard
     A.4  Guidelines to Specific Constructs
           A.4.1.   Namespaces
           A.4.2   rdf:value and Other Constructs
           A.4.3.   Language-Specific Strings
           A.4.4   Ordered and Unordered Lists
           A.4.5   Pre-Defined Classes
           A.4.6   Vocabularies
           A.4.7   Using Metameta-data
           A.4.8   Classifications
     A.5  Acknowledgements
     A.6  The Binding Table
           1.   General Category
           2.   Lifecycle Category
           3.   Metametadata Category
           4. Technical Category
           5. Educational Category
           6. Rights Category
           7. Relation Category
           8. Annotation Category
           9. Classification Category
     A.7  LangString Definition
     A.8  Taxonomies

Appendix B - Additional Resources

Appendix C - List of Contributors

About This Document

Revision History

Index

1. Introduction

This document describes the XML binding for the IMS Learning Resource Meta-Data Information Model. The model is based on the IEEE Learning Technology Standards Committee (LTSC) Learning Object Meta-Data (LOM) Draft Standard, plus modifications approved by the IMS Technical Board and submitted to IEEE. For links to the related IEEE documents, please see http://www.imsglobal.org/metadata/imsmdv1p2p1/imsmd_infov1p2p1.html.

1.1 XML Basics

The LOM conceptual model for meta-data definitions is a hierarchy. Hierarchical models are convenient for representing data consisting of many elements and sub-elements. XML is perfectly suited for representing hierarchical models. An XML document is a hierarchy comprised of elements that have contents and attributes.

1.1.1 Elements

An element is a component of a document that has been identified in a way a computer can understand. Each element has a tag name. When a tag name is shown as "<TAGNAME>", with less-than and greater-than symbols before and after the tag name, it serves as the start-tag to mark the beginning of an element. When that same tag name has a forward slash "/" added, it serves as an end-tag such as "</TAGNAME>". An element may have contents between its start and end-tags, and may have one or more attributes. When an XML element has a start and end-tag (also called an opening and closing tag) with a common name, it is considered to be "well-formed" XML. The contents of an element are placed between the start and end-tags as shown below:

<TAGNAME>contents</TAGNAME>

1.1.1.1 Element Contents

An element may contain other elements, Parsed Character Data (PCDATA), Character Data (CDATA), or a mixture of PCDATA and elements. The allowable contents of an element are its content model. XML parsers treat PCDATA with their special or reserved meaning unless they are specifically marked (or "escaped"). In contrast, CDATA can use special or reserved characters without having to escape them, as CDATA is not read by XML parsers.

1.1.1.2 Element Attributes

An attribute provides additional information about an element. Attributes are a way of attaching characteristics or properties to the elements of a document. An element may have more than one attribute. Attributes are contained within the start tag of an element. Attributes are represented by an attribute name followed by an equal sign and the attribute value in quotation marks:

<timeframe>
  <begin restrict="1"> 1999-07-23 </begin>
</timeframe>

In this example, the timeframe element contains another element: the begin element. The begin element has one attribute "restrict", with the value "1". The value for the element BEGIN is "1999-07-23". These two elements then make up a timeframe begin date.

1.1.1.3 Element Names

Each element has a unique name, referred to as the tag name. XML is case-sensitive in its processing of tag names. The IMS Learning Resource Meta-Data XML Binding Specification adheres to the following tag name rules:

DOCTYPE
ELEMENT
ATTLIST
ENTITY

1.1.2 Document Type Definitions

The tag name, content model, and attributes of elements are defined in a Document Type Definition (DTD) statement. This may exist as an external file or a block of text internal to an XML document. Internal DTDs are used to override elements defined in external DTD files, so an internal DTD should be used with care. The DTD defines the elements that may be used and may define the contents of the elements.

This specification defines a DTD (imsmd_rootv1p2.dtd) as a non-normative reference. Some XML editors may make use of a DTD to help guide the developer in creating the proper elements at the proper locations in an XML file. Other developers will make use of DTDs to validate their XML documents to ensure their document is consistent with all of the element names and locations defined in the DTD. Details of the construction of DTDs are outside the scope of this document, but links to the XML 1.0 Specification are included in the Appendix.

1.1.3 XML Schemas

A schema is a formal specification of element names that indicates which elements are allowed in an XML instance, and in which combinations. New schema languages, such as those defined in the XML-Schemas Working Group, provide the same baseline functionality as a DTD. However, because these schema languages are extensible, developers can augment them with additional information, such as data types, inheritance, and presentation rules. This makes schema languages far more powerful than DTDs. For more information about XML schemas, there is a link to the W3C XML Schema Recommendation in the Appendix.

This specification defines a W3C XML Schema (imsmd_rootv1p2p1.xsd), and a Microsoft XML-Data Schema (XDR) as non-normative references. Some XML editors may make use of these schemas to help guide the developer in creating the proper elements at the proper locations in an XML file. Other developers will make use of the schemas to validate their XML instances and/or to define extensions to the IMS Meta-Data Binding. Details of the construction of schemas are outside the scope of this document.

1.1.4 Valid Character Sets

An IMS meta-data instance must use UTF-8 or UTF-16 encoding of the character sets as defined in ISO 10646. See the XML Version 1.0 for more details on the specification of well-formed XML.

1.1.5 Use of Attributes

Within the IMS Meta-Data Binding specification, the use of attributes is reserved for information about the structure of and source of terms in the meta-data instance. It is recommended that attributes not be used for information about the resource. This Binding specification uses only two element attributes (the "xml:lang" attribute and the "type" attribute) in particular ways and for particular purposes.

xml:lang:

This attribute specifies the human language of the contents of the element. It is only used as an attribute of the <langstring> element. The "xml:lang" attribute may contain a two-character language code followed by a two-character country code. For example:

<otherplatformrequirements>
  <langstring xml:lang="en-US">Will not run in browser.</langstring>
</otherplatformrequirements>

The codes for languages and countries are enumerated in the W3C XML Specification.

Note: When using the <langstring> element's "xml:lang" attribute in the VocabularyType (within <source> and <value>), the xml:lang attribute shall have a value of "x-none".

<role>
  <source>
    <langstring xml:lang="x-none">LOMv1.0</langstring>
  </source>
  <value>
    <langstring xml:lang="x-none">Author</langstring>
  </value>
</role>

type:

This attribute specifies the type of string that may be used to identify the location of a learning resource as used in the <location> element. The type attribute may be assigned the value of either "URI" or "TEXT". These values indicate whether the string used will be a simple textual description of where a resource is located or whether the string represents a resource available on the Internet with a specific address such as a URL. For example:

<technical>
  <format/>
  <size>1032353</size>
  <location type="URI">http://www.brookscole.com</location>
</technical>

1.1.6 Lists

The meta-data specification uses listing at multiple levels in the hierarchy. A list is a repetition of the contents of an element. In XML this is accomplished by repeating the containing element:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE record [
  <!ELEMENT general (language*)>
  <!ELEMENT language (#PCDATA)>
  ]>
<lom>
  <language>en_US</language>
  <language>fr_FR</language>
</lom>

In this example, the <language> element is repeated. Thus, <language> is the containing element for the repeated contents of "en_US" and "fr_FR". The notation for repetitions of an element in a content model follows the W3C XML Specification. An asterisk (*) specifies that none or more repetitions of the <language> element may be included in the XML instantiation. There are two main types of lists: ordered and unordered.

1.1.6.1 Ordered Lists

Repeating the listed element at its specific location in the XML structure creates an ordered list of contents. The order of the elements has significance as their placement in the XML file determines this. The following is an example of an XML fragment in which the <educational> element contains an ordered list of <learningresourcetype> elements:

<educational>
  <learningresourcetype>
    <source>
      <langstring xml:lang="x-none">LOMv1.0</langstring>
    </source>
    <value>
      <langstring xml:lang="x-none">Simulation</langstring>
    </value>
  </learningresourcetype>
  <learningresourcetype>
    <source>
      <langstring xml:lang="x-none">LOMv1.0</langstring>
    </source>
    <value>
      <langstring xml:lang="x-none">Assessment</langstring>
    </value>
  </learningresourcetype>
</educational>

1.1.6.2 Unordered Lists

Repeating the containing element at its specific location in the XML structure creates an unordered list of contents. The order of the repetitions has no significance. For example:

<general>
  <language>en_US</language>
  <language>fr_FR</language>
</general>

In this example, each new instance of a definition of a language requires that the <language> element be repeated. Whether an element list should be treated as ordered or unordered is specified by the IEEE LOM Draft Standard.

1.1.7 Namespaces

XML is designed to allow individuals to create their own element tag names. It soon became apparent that there could be problems if different DTDs were used in the same document and those DTDs had elements using the same name. The W3C XML Namespace Recommendation specifies a way to ensure that names from different DTDs can be identified in a single document.

The XML Namespace document provides more information about the flexible capabilities of namespaces. The W3C Recommendation for Namespaces (http://www.w3.org/TR/1999/REC-xml-names-19990114) does not specify how namespaces are to be used. The introductory abstract states the following:

"XML namespaces provide a simple method for qualifying element and attribute names used in Extensible Markup Language documents by associating them with namespaces identified by URI references."

The W3C XML 1.0 Specification does not specify how namespaces are to be processed. Currently there are two general approaches to namespaces:

  1. Use to point to a specific encoding schema for machine interpretation, and
  2. Use as a reference for uniqueness and possibly definition (semantics).

These two approaches are not mutually exclusive. A namespace is applied as a prefix to an element or attribute name:

<dc:subject>

The prefix of dc: is the qualifier, and must be defined elsewhere in the document. The user is directed to the W3C Namespace Recommendation for more details on application. IMS does not specify how namespaces are to be resolved (semantically or for machine interpretation). Namespaces should point to schema files for validation. To point to a schema file locally, the schema and the XML instance must reside in the same directory and would look similar to the following:

<lom xmlns="http://www.imsproject.org/xsd/imsmd_rootv1p2p1" xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance" xsi:schemaLocation="http://www.imsproject.org/xsd/imsmd_rootv1p2p1 imsmd_rootv1p2p1.xsd">

To validate your XML instance online your namespace reference would look similar to the following:

<lom xmlns="http://www.imsproject.org/xsd/imsmd_rootv1p2p1" xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance" xsi:schemaLocation="http://www.imsproject.org/xsd/imsmd_rootv1p2p1 http://www.imsproject.org/xsd/imsmd_rootv1p2p1.xsd">

2. Narrative Description of XML Binding

This section of the specification uses a simple narrative to describe the XML format. DTDs and XSDs that implement this abstract format are referenced as non-normative parts of this specification.

The reader's attention is called to LOM's "smallest permitted maximum" concept. Implementations are not guaranteed to handle more than a smallest permitted maximum declared for a given element or string length.

2.1 <lom> Element

Description. General information that describes the learning object as a whole.

Multiplicity. The <lom> element is the root element of the XML instance. This element should occur 1 and only 1 time in an IMS XML Meta-Data instance.

Attributes

Elements

2.2 <general> Element

Description. General information that describes the learning object as a whole.

<general> elements

Figure 2.1 <general> elements.

Multiplicity. The <general> element occurs 0 or 1 time within the top-level <lom> element.

Attributes

Elements

2.2.1 <identifier> Element

Description. A globally unique label that identifies this learning object. This element is no longer reserved and authors may use their own ID method or the IMS Persistent, Location-Independent Resource Identifiers Best Practice Guide, which at the time of this writing was being considered as an IMS wide base specification.

Multiplicity. The <identifier> element occurs 0 or 1 time within the <general> element.

Attributes

Elements

2.2.2 <title> Element

Description. Name given to the learning object.

Multiplicity. The <title> element occurs 0 or 1 time within the <general> element.

Attributes

Elements

Example

<general>
  <title>
    <langstring xml:lang="en">Title 1 in English</language>
    <langstring xml:lang="fr">Titre 1 en francais</language>
  </title>
</general>

2.2.3 <catalogentry> Element

Description. This data element defines an entry within a catalog (i.e. a listing identification system) assigned to this learning object. This sub-category shall describe this learning object according to some known cataloging system so that it may be externally searched for and located according to the methodology of the specified system.

Multiplicity. The <catalogentry> element occurs 0 or more times within the <general> element. The smallest permitted maximum is 10 instances within the <general> element.

Attributes

Elements

Example

<general>
  <catalogentry>
    <catalog>ISBN</catalog>
    <entry>
      <langstring>0-226-10389-7</langstring>
    </entry>
  </catalogentry>
</general>

2.2.3.1 <catalog> Element

Description. The name of the catalog (i.e. listing identification system).

Multiplicity. The <catalog> element must occur 1 and only 1 time within the <catalogentry> element.

Attributes

Elements

2.2.3.2 <entry> Element

Description. Actual string value of the entry within the catalog (i.e. listing identification system).

Multiplicity. The <entry> element occurs 1 and only 1 time with the <catalogentry> element. If the <catalogentry> element is used, the <entry> elment must occur 1 and only 1 time within the <catalogentry> element.

Attributes

Elements

2.2.4 <language> Element

Description. The primary human language or languages used within this learning object to communicate to the intended user.

Multiplicity. The <language> element occurs 0 or more times within the <general> element. The smallest permitted maximum is 10 instances within the <general> element.

Attributes

Elements

Example

<general>
  <language>en</language>
  <language>fr</language>
</general>

2.2.5 <description> Element

Description. A textual description of the content of this learning object.

Multiplicity. The <description> element occurs 0 or more times within the <general> element. The smallest permitted maximum is 10 instances within the <general> element.

Attributes

Elements

Example

<general>
  <description>
    <langstring xml:lang="en">English description</langstring>
    <langstring xml:lang="fr">French description</langstring>
  </description>
</general>

2.2.6 <keyword> Element

Description.  A collection of keywords or phrases describing this learning object. This data element should not be used for characteristics that can be described by other data elements.

Multiplicity. The <keyword> element occurs 0 or more times within the <general> element. The smallest permitted maximum is 10 instances within the <general> element.

Attributes

Elements

Example

<general>
  <keyword>
    <langstring xml:lang="en">metadata</langstring>
    <langstring xml:lang="nl">metadata</langstring>
    <langstring xml:lang="fr">metadonnees</langstring>
  </keyword>
  <keyword>
    <langstring xml:lang="en">learning object</langstring>
    <langstring xml:lang="nl">leerobject</langstring>
    <langstring xml:lang="fr">objet d'apprentissage</langstring>
  </keyword>
  <keyword>
    <langstring xml:lang="en">education</langstring>
  </keyword>
<general>

2.2.7 <coverage> Element

Description. The span or extent of such things as time, culture, geography or region that applies to this learning object.

Multiplicity. The <coverage> element occurs 0 or more times within the <general> element. The smallest permitted maximum is 10 instances within the <general> element.

Attributes

Elements

Example

<general>
  <coverage>
    <langstring xml:lang="en">Circa, 16th century France</langstring>
  </coverage>
<general>

2.2.8 <structure> Element

Description. Underlying organizational structure of this learning object.

Multiplicity. The <structure> element occur 0 or 1 time within the <general> element.

Attributes

Elements

LOM Defined Vocabularies (<source> element set to LOMv1.0)

Example

<general>
  <structure>
    <source>
      <langstring xml:lang="x-none">LOMv1.0</langstring>
    </source>
    <value>
      <langstring xml:lang="x-none">Collection</langstring>
    </value>
  </structure>
</general>

2.2.9 <aggregationlevel> Element

Description. The functional granularity of this learning object.

Multiplicity. The <aggregationlevel> element occurs 0 or 1 time within the <general> element.

Attributes

Elements

LOM Defined Vocabularies (<source> element set to LOMv1.0)

Example

<general>
  <aggregationlevel>
    <source>
      <langstring xml:lang="x-none">LOMv1.0</langstring>
    </source>
    <value>
      <langstring xml:lang="x-none">1</langstring>
    </value>
  </aggregationlevel>
</general>

2.3 <lifecycle> Element

Description. Features related to the history and current state of this learning object and those who have affected this learning object during its evolution.

<lifecycle> elements

Figure 2.2 <lifecycle> elements.

Multiplicity. The <lifecycle> element occurs 0 or 1 time within the top-level <lom> element.

Attributes

Elements

2.3.1 <version> Element

Description. The edition of this learning object.

Multiplicity. The <version> element occurs 0 or 1 time within the <lifecycle> element.

Attributes

Elements

Example

<lifecycle>
  <version>
    <langstring xml:lang="en">1.0.alpha</langstring>
  </version>
</lifecycle>

2.3.2 <status> Element

Description. The state or condition of this learning object.

Multiplicity. The <status> element occurs 0 or 1 time within the <lifecycle> element.

Attributes

Elements

LOM Defined Vocabularies (<source> element set to LOMv1.0)

Example

<lifecycle>
  <status>
    <source>
      <langstring xml:lang="x-none">LOMv1.0</langstring>
    </source>
    <value>
      <langstring xml:lang="x-none">Final</langstring>
    </value>
  </status>
</lifecycle>

2.3.3 <contribute> Element

Description. This data element describes those people or organizations that have affected the state of this learning object during its evolution.

Multiplicity. The <contribute> element occurs 0 or more times within the <lifecycle> element. The smallest permitted maximum is 30 instances within the <lifecycle> element.

Attributes

Elements

Example

<lifecycle>
  <contribute>
    <role>
      <source>
        <langstring xml:lang="x-none">LOMv1.0</langstring>
      </source>
      <value>
        <langstring xml:lang="x-none">Author</langstring>
      </value>
    </role>
    <centity>
      <vcard>
        begin:vcard
        fn: Joe Author
        end:vcard
      </vcard>
    </centity>
    <date>
      <datetime>2000-12-12</datetime>
      <description>
        <langstring>Date Description</langstring>
      </description>
    </date>
  </contribute>
</lifecycle>

2.3.3.1 <role> Element

Description. This data element describes the kind of contribution. It is recommended that at least the Author(s) of the learning object should be described.

Multiplicity. The <role> element occurs 1 and only 1 time within the <contribute> element. If the <contribute> element is used, the <role> element must occur 1 and only 1 time within the <contribute> element. If there are multiple contributors (different roles), then the <contribute> element should be repeated.

Attributes

Elements

LOM Defined Vocabularies (<source> element set to LOMv1.0)

2.3.3.2 <centity> Element

Description. This data element is the identification of and information about people or organizations contributing to this learning object, most relevant first.

Multiplicity. The <centity> element occurs 0 or more times within the <contribute> element. The smallest permitted maximum is 40 instances within the <contribute> element.

Attributes

Elements

2.3.3.3 <date> Element

Description. This data element describes date of the contribution.

Multiplicity. The <date> element occurs 0 or 1 time within the <contribute> element.

Attributes

Elements

2.4 <metametadata> Element

Description. Groups information about the meta-data instance itself (rather than the learning object that this instance describes).

<metametadata> elements

Figure 2.3 <metametadata> elements.

Multiplicity. The <metametadata> element occurs 0 or 1 time within the top-level <lom> element.

Attributes

Elements

2.4.1 <identifier> Element

Description. A globally unique label that identifies this meta-data instance. This element is no longer reserved and authors may use their own ID method or the IMS Persistent, Location-Independent Resource Identifiers Best Practice Guide, which at the time of this writing was being considered as an IMS wide base specification.

Multiplicity. The <identifier> element occurs 0 or 1 time within the <metametadata> element.

Attributes

Elements

2.4.2 <catalogentry> Element

Description. This data element defines an entry within a catalog (i.e. a listing identification system) given to the meta-data instance. This sub-category should describe this meta-data instance according to some known cataloging system so that it may be externally searched for and located according to the methodology of the specified system.

Multiplicity. The <catalogentry> element occurs 0 or more times within the <metametadata> element. The smallest permitted maximum is 10 instances within the <metametadata> element.

Attributes

Elements

Example

<metametadata>
  <catalogentry>
    <catalog>ISBN</catalog>
    <entry>
      <langstring>0-226-10389-7</langstring>
    </entry>
  </catalogentry>
</metametadata>

2.4.2.1 <catalog> Element

Description. The name of the catalog (i.e. listing identification system).

Multiplicity.  The <catalog> element must occur 1 and only 1 time within the <catalogentry> element.

Attributes

Elements

2.4.2.2 <entry> Element

Description. Actual string value of the entry within the catalog (i.e. listing identification system).

Multiplicity.  The <entry> element must occur 1 and only 1 time within the <catalogentry> element.

Attributes

Elements

2.4.3 <contribute> Element

Description. This data element describes those people or organizations that have affected the state of this meta-data instance during its evolution.

Multiplicity. The <contribute> element occurs 0 or more times within the <metametadata> element. The smallest permitted maximum is 10 instances within the <metametadata> element.

Attributes

Elements

Example

<metametadata>
  <contribute>
    <role>
      <source>
        <langstring xml:lang="x-none">LOMv1.0</langstring>
      </source>
      <value>
        <langstring xml:lang="x-none">Creator</langstring>
      </value>
    </role>
    <centity>
      <vcard>
        begin:vcard
        fn: Joe Creator
        end:vcard
      </vcard>
    </centity>
    <date>
      <datetime>2000-12-12</datetime>
      <description>
        <langstring>Date Description</langstring>
      </description>
    </date>
  </contribute>
</metametadata>

2.4.3.1 <role> Element

Description. This data element describes the kind of contribution. It is recommended that at least the Creator(s) of the meta-data instance should be described.

Multiplicity. If the <contribute> element is used, the <role> element must occur 1 and only 1 time within the <contribute> element. If there are multiple contributors (different roles), then the <contribute> element should be repeated.

Attributes

Elements

LOM Defined Vocabularies (<source> element set to LOMv1.0)

2.4.3.2 <centity> Element

Description. This data element is the identification of and information about people or organizations contributing to this meta-data instance, most relevant first.

Multiplicity. The <centity> element occurs 0 or more times within the <contribute> element. The smallest permitted maximum is 10 instances within the <contribute> element.

Attributes

Elements

2.4.3.3 <date> Element

Description. This data element describes date of the contribution.

Multiplicity. The <date> element occurs 0 or 1 time within the <contribute> element.

Attributes

Elements

2.4.4 <metadatascheme> Element

Description. This data element represents the name and version of the authoritative specification used to create this meta-data instance. If multiple values are provided, then the meta-data instances shall conform to multiple meta-data schemes.

Multiplicity. The <metadatascheme> element occurs 0 or more times within the <metametadata> element. The smallest permitted maximum is 10 instances within the <metametadata> element.

Attributes

Elements

Example

<metametadata>
  <metadatascheme>LOMv1.0</metadatascheme>
</metametadata>

2.4.5 <language> Element

Description. This data element describes the language of this meta-data instance. This is the default language for all LangString values in this meta-data instance.

Multiplicity. The <language> element occurs 0 or 1 time within the <metametadata> element.

Attributes

Elements

Example

<metametadata>
  <language>en</language>
</metametadata>

2.5 <technical> Element

Description. Groups the technical requirements and characteristics of the learning object.

<technical> elements

Figure 2.4 <technical> elements.

Multiplicity. The <technical> element occurs 0 or 1 time within the top-level <lom> element.

Attributes

Elements

2.5.1 <format> element

Description. This data element describes the technical data type(s) of (all the components of) this learning object. This data element shall be used to identify the software needed to access the learning object.

Multiplicity. The <format> element occurs 0 or more times within the <technical> element. The smallest permitted maximum is 40 instances within the <technical> element.

Attributes

Elements

Example

<technical>
  <format>video/mpeg</format>
  <format>text/html</format>
</technical>

2.5.2 <size> element

Description. This data element describes the size of the digital learning object in bytes. Only digits '0' through '9' should be used; the unit is bytes, not Mbytes, GB, etc. This date element shall refer to the actual size of this learning object. If the learning object is compressed, then this data element shall refer to the uncompressed size.

Multiplicity. The <size> element occurs 0 or 1 time within the <technical> element.

Attributes

Elements

Example

<technical>
  <size>568</size>
</technical>

2.5.3 <location> element

Description. This data element is a string that is used to access this learning object. It may be a location (e.g. Universal Resource Locator), or a method that resolves to a location (e.g. Universal Resource Identifier). The preferable location first. This is where the learning object described by this meta-data instance is physically located.

Multiplicity. The <location> element occurs 0 or more times within the <technical> element. The smallest permitted maximum is 10 instances within the <technical> element.

Attributes

Elements

Example

<technical>
  <location type="URI">http://host/id</location>
</technical>

2.5.4 <requirement> element

Description. This data element describes the technical capabilities required in order to use this learning object. If there are multiple requirements, then all are required, i.e. the logical connector is AND.

Multiplicity. The <requirement> element occurs 0 or more times within the <technical> element. The smallest permitted maximum is 40 instances within the <technical> element.

Attributes

Elements

Example

<technical>
  <requirement>
    <type>
      <source>
        <langstring xml:lang="x-none">LOMv1.0</langstring>
      </source>
      <value>
        <langstring xml:lang="x-none">Browser</langstring>
      </value>
    </type>
    <name>
      <source>
        <langstring xml:lang="x-none">LOMv1.0</langstring>
      </source>
      <value>
        <langstring xml:lang="x-none">Microsoft Internet Explorer>/langstring>
      </value>
    </name>
    <minimumversion>4.0</minimumversion>
    <maximimversion>5.0</maximumversion>
  </requirement>
</technical>

2.5.4.1 <type> Element

Description. This data element describes the technology required to use this learning object, i.e. hardware, software, network, etc.

Multiplicity. The <type> element occurs 0 or 1 time within the <requirement> element.

Attributes

Elements

LOM Defined Vocabularies (<source> element set to LOMv1.0)

2.5.4.2 <name> Element

Description. This data element describes name of the required technology to use this learning object. The value for this data element may be derived from the 4.4.1 Technical.Format automatically, e.g., "video/mpeg" implies "Multi-OS".

Multiplicity. The <name> element occurs 0 or 1 time within the <requirement> element.

Attributes

Elements

LOM Defined Vocabularies (<source> element set to LOMv1.0)

If Technical.Requirement.Type="Operating System"

If Technical.Requirement.Type="Browser"

2.5.4.3 <minimumversion> Element

Description. This data element describes the lowest possible version of the required technology to use this learning object.

Multiplicity. The <minimumversion> element occurs 0 or 1 time within the <requirement> element.

Attributes

Elements

2.5.4.4 <maximumversion> Element

Description. This data element describes the highest version of the technology known to support the use of this learning object.

Multiplicity. The <maximumversion> element occurs 0 or 1 time within the <requirement> element.

Attributes

Elements

2.5.5 <installationremarks> Element

Description. This data element contains the description of how to install this learning object.

Multiplicity. The <installationremarks> element occurs 0 or 1 time within the <technical> element.

Attributes

Elements

Example

<technical>
  <installationremarks>
    <langstring>Installation remakes placed here</langstring>
  </installationremarks>
</technical>

2.5.6 <otherplatformrequirements> Element

Description. This data element contains information about other software and hardware requirements.

Multiplicity. The <otherplatformrequirements> element occurs 0 or 1 time within the <technical> element.

Attributes

Elements

Example

<technical>
  <otherplatformrequirements>
    <langstring>Other platform requirements placed here</langstring>
  </otherplatformrequirements>
</technical>

2.5.7 <duration> Element

Description. This data element the time a continuous learning object takes when played at the intended speed. This data element is especially useful for sounds, movies or animations.

Multiplicity. The <duration> element occurs 0 or 1 time within the <technical> element.

Attributes

Elements

Example

<technical>
  <duration>
    <datetime>00:00:15</datetime>
    <description>
      <langstring>Length of time to play the simulation</langstring>
    </description>
  </duration>
</technical>

2.6 <educational> Element

Description. Conditions of use of the resource.

<educational> elements

Figure 2.5 <educational> elements.

Multiplicity. The <educational> element occurs 0 or 1 time within the top-level <lom> element.

Attributes

Elements

2.6.1 <interactivitytype> Element

Description. The type of interactivity supported by the learning object.

Multiplicity. The <interactivitytype> element occurs 0 or 1 time within the <educational> element.

Attributes

Elements

LOM Defined Vocabularies (<source> element set to LOMv1.0)

Example

<educational>
  <interactivitytype>
    <source>
      <langstring xml:lang="x-none">LOMv1.0</langstring>
    </source>
    <value>
      <langstring xml:lang="x-none">Active</langstring>
    </value>
  </interactivitytype>
</educational>

2.6.2 <learningresourcetype> Element

Description. Specific kind of resource, most dominant kind first.

Multiplicity. The <learningresourcetype> element occurs 0 or more times within the <educational> element. The smallest permitted maximum is 10 instances within the <educational> element.

Attributes

Elements

LOM Defined Vocabularies (<source> element set to LOMv1.0)

Example

<educational>
  <learningresourcetype>
    <source>
      <langstring xml:lang="x-none">LOMv1.0</langstring>
    </source>
    <value>
      <langstring xml:lang="x-none">Simulation</langstring>
    </value>
  </learningresourcetype>
</educational>

2.6.3 <interactivitylevel> Element

Description. Level of interactivity between an end user and the learning object.

Multiplicity. The <interactivitylevel> element occurs 0 or 1 time within the <educational> element.

Attributes

Elements

LOM Defined Vocabularies (<source> element set to LOMv1.0)

Example

<educational>
  <interactivitylevel>
    <source>
      <langstring xml:lang="x-none">LOMv1.0</langstring>
    </source>
    <value>
      <langstring xml:lang="x-none">very high</langstring>
    </value>
  </interactivitylevel>
</educational>

2.6.4 <semanticdensity> Element

Description. Subjective measure of the learning object's usefulness as.compared to its size or duration.

Multiplicity. The <semanticdensity> element occurs 0 or 1 time within the <educational> element.

Attributes

Elements

LOM Defined Vocabularies (<source> element set to LOMv1.0)

Example

<educational>
  <semanticdensity>
    <source>
      <langstring xml:lang="x-none">LOMv1.0</langstring>
    </source>
    <value>
      <langstring xml:lang="x-none">very high</langstring>
    </value>
  </semanticdensity>
</educational>

2.6.5 <intendedenduserrole> Element

Description. Normal user of the learning object, most dominant first.

Multiplicity. The <intendedenduserrole> element occurs 0 or more times within the <educational> element. The smallest permitted maximum is 10 instances within the <educational> element.

Attributes

Elements

LOM Defined Vocabularies (<source> element set to LOMv1.0)

Example

<educational>
  <intendedenduserrole>
    <source>
      <langstring xml:lang="x-none">LOMv1.0</langstring>
    </source>
    <value>
      <langstring xml:lang="x-none">Learner</langstring>
    </value>
  </intendedenduserrole>
</educational>

2.6.6 <context> Element

Description. The typical learning environment where use of learning object is intended to take place.

Multiplicity. The <context> element occurs 0 or more times within the <educational> element. The smallest permitted maximum is 10 instances within the <educational> element.

Attributes

Elements

LOM Defined Vocabularies (<source> element set to LOMv1.0)

Example

<educational>
  <context>
    <source>
      <langstring xml:lang="x-none">LOMv1.0</langstring>
    </source>
    <value>
      <langstring xml:lang="x-none">University Postgrade</langstring>
    </value>
  </context>
</educational>

2.6.7 <typicalagerange> Element

Description. Age of the typical intended user.

Multiplicity. The <typicalagerange> element occurs 0 or more times within the <educational> element. The smallest permitted maximum is 5 instances within the <educational> element.

Attributes

Elements

Example

<educational>
  <typicalagerange>
    <langstring xml:lang="en">adult pilot with 3 years experience</langstring>
  </typicalagerange>
</educational>

2.6.8 <difficulty> Element

Description. How hard it is to work through the learning object for the typical target audience.

Multiplicity. The <difficulty> element occurs 0 or 1 time within the <educational> element.

Attributes

Elements

LOM Defined Vocabularies (<source> element set to LOMv1.0)

Example

<educational>
  <difficulty>
    <source>
      <langstring xml:lang="x-none">LOMv1.0</langstring>
    </source>
    <value>
      <langstring xml:lang="x-none">medium</langstring>
    </value>
  </difficulty>
</educational>

2.6.9 <typicallearningtime> Element

Description. Approximate or typical time it takes to work with the resource.

Multiplicity. The <typicallearningtime> element occurs 0 or 1 time within the <educational> element.

Attributes

Elements

Example

<educational>
  <typicallearningtime>
    <datetime>01:30:00</datetime>
  </typicallearningtime>
</educational>

2.6.10 <description> Element

Description. Comments on how the learning object is to be used.

Multiplicity. The <description> element occurs 0 or 1 time within the <educational> element.

Attributes

Elements

Example

<educational>
  <description>
    <langstring>Used for training on in-flight refueling</langstring>
  </description>
</educational>

2.6.11 <language> Element

Description. User's natural language.

Multiplicity. The <language> element occurs 0 or more times within the <educational> element. The smallest permitted maximum is 10 instances within the <educational> element.

Attributes

Elements

Example

<educational>
  <language>en</language>
</educational>

2.7 <rights> Element

Description. Conditions of use of the resource.

<rights> elements

Figure 2.6 <rights> elements.

Multiplicity. The <rights> element occurs 0 or 1 time within the top-level <lom> element.

Attributes

Elements

2.7.1 <cost> Element

Description. Whether use of the resource requires payment.

Multiplicity. The <cost> element occurs 0 or 1 time within the <rights> element.

Attributes

Elements

LOM Defined Vocabularies (<source> element set to LOMv1.0)

Example

<rights>
  <cost>
    <source>
      <langstring xml:lang="x-none">LOMv1.0</langstring>
    </source>
    <value>
      <langstring xml:lang="x-none">no</langstring>
    </value>
  </cost>
</rights

2.7.2 <copyrightandotherrestrictions> Element

Description. Whether copyright or other restrictions apply.

Multiplicity. The <copyrightandotherrestrictions> element occurs 0 or 1 time within the <rights> element.

Attributes

Elements

LOM Defined Vocabularies (<source> element set to LOMv1.0)

Example

<rights>
  <copyrightandotherrestrictions>
    <source>
      <langstring xml:lang="x-none">LOMv1.0</langstring>
    </source>
    <value>
      <langstring xml:lang="x-none">no</langstring>
    </value>
  </copyrightandotherrestrictions>
</rights>

2.7.3 <description> Element

Description. Comments on the conditions of use of the resource.

Multiplicity. The <description> element occurs 0 or 1 time within the <rights> element.

Attributes

Elements

Example

<rights>
  <description>
    <langstring xml:lang="en">LOMv1.0</langstring>
  </description>
</rights

2.8 <relation> Element

Description. Features of the resource in relationship to other learning objects.

<relation> elements

Figure 2.7 <relation> elements.

Multiplicity. The <relation> element occurs 0 or more times within the top-level <lom> element. The smallest permitted maximum is 100 instances.

Attributes

Elements

2.8.1 <kind> Element

Description. Nature of the relationship between the resource being described and the one identified by 7.2 relation/resource.

Multiplicity. The <kind> element occurs 0 or 1 time within the <resource> element.

Attributes

Elements

LOM Defined Vocabularies (<source> element set to LOMv1.0)

Example

<relation>
  <kind>
    <source>
      <langstring xml:lang="x-none">LOMv1.0</langstring>
    </source>
    <value>
      <langstring xml:lang="x-none">Requires</langstring>
    </value>
  </kind>
  <resource>
    <description>
      <langstring>Description of resource</langstring>
    </description>
  </resource>
  <catalogentry>
    <catalog>ISBN</catalog>
      <entry>
        <langstring>0-226-10389-7</langstring>
      </entry>
    </catalog>
  </catalogentry>
</relation>

2.8.2 <resource> Element

Description. The target learning object that this relationship references.

Multiplicity. The <resource> element occurs 0 or 1 time within the <relation> element.

Attributes

Elements

2.8.2.1 <identifier> Element

Description. Unique identifier of the other resource.

Multiplicity. The <identifier> element occurs 0 or 1 time within the <resource> element.

Attributes

Elements

2.8.2.2 <description> Element

Description. Description of the other resource.

Multiplicity. The <description> element occurs 0 or 1 time within the <resource> element.

Attributes

Elements

2.8.2.3 <catalogentry> Element

Description. Reference to the other resource.

Multiplicity. The <catalogentry> element occurs 0 or more times within the <resource> element. The smallest permitted maximum is 10 instances within the <resource> element.

Attributes

Elements

2.8.2.3.1 <catalog> Element

Description. Source of the following string value.

Multiplicity. The <catalog> element occurs 1 and only 1 time within the <catalogentry> element.

Attributes

Elements

2.8.2.3.2 <entry> Element

Description. Actual catalog value.

Multiplicity. The <entry> element occurs 1 and only 1 time within the <catalogentry> element.

Attributes

Elements

2.9 <annotation> Element

Description. Comments on the educational use of the learning object.

<annotation> elements

Figure 2.8 <annotation> elements.

Multiplicity. The <annotation> element occurs 0 or more times within the top-level <lom> element. The smallest permitted maximum is 30 instances.

Attributes

Elements

2.9.1 <person> Element

Description. Comments on the educational use of the learning object

Multiplicity. The <person> element occurs 0 or 1 time within the <annotation> element.

Attributes

Elements

Example

<annotation>
  <person>
    <vcard>
      begin:vcard
      org: IMS
      end:vcard
    </vcard>
  </person>
</annotation>

2.9.2 <date> Element

Description. Date that this annotation was created.

Multiplicity. The <date> element occurs 0 or 1 time within the <annotation> element.

Attributes

Elements

Example

<annotation>
  <date>
    <datetime>2001-04-17</datetime>
  </date>
</annotation>

2.9.3 <description> Element

Description. The content of the annotation.

Multiplicity. The <description> element occurs 0 or 1 time within the <annotation> element. The <description> element is required if the parent <annotation> element is used.

Attributes

Elements

Example

<annotation>
  <description>
    <langstring xml:lang="en">
      This simulation can be used in conjunction with the in-flight refueling course
    </langstring>
  </description>
</annotation>

2.10 <classification> Element

Description. Description of a characteristic of the resource by entries in classifications.

<classification> elements

Figure 2.9 <classification> elements.

Multiplicity. The <classification> element occurs 0 or more times within the top-level <lom> element. The smallest permitted maximum is 40 instances.

Attributes

Elements

2.10.1 <purpose> Element

Description. Characteristics of