< Previous | Contents | Next >

4.2. LOM Metadata Creation

The following sections outline the LOM XML metadata elements. According to the IEEE, every LOM metadata element is optional. This implies that when building an XML metadata instance, the developer can optionally pick and choose which elements to use.

The IEEE LOM Information Model describes the set of data elements that are available to build metadata. The LOM Information Model is broken up into nine categories.

These categories are based on the definitions found in the LOM Information Model. The nine categories of metadata elements are:

1. The General category can be used to describe general information about the SCORM Content Model Component as a whole.

2. The Life Cycle category can be used to describe features related to the history and current state of the SCORM Content Model Component and those who have affected the component during its evolution.


3. The Meta-metadata category can be used to describe information about the metadata record itself (rather than the SCORM Content Model Component that the record describes).

4. The Technical category can be used to describe technical requirements and characteristics of the SCORM Content Model Components.

5. The Educational category can be used to describe the educational and pedagogic characteristics of the SCORM Content Model Component.

6. The Rights category can be used to describe the intellectual property rights and conditions of use for the SCORM Content Model Component.

7. The Relation category can be used to describe features that define the relationship between this SCORM Content Model Component and other targeted components.

8. The Annotation category can be used to provide comments on the educational use of the SCORM Content Model Component and information on when and by whom the comments were created.

9. The Classification category can be used to describe where the SCORM Content Model Component falls within a particular classification system.

Some elements use the term smallest permitted maximum (SPM) in describing the multiplicity and/or data types. The SPM indicates that applications that process metadata shall process at least that number of elements or number of characters, but are free to support and exceed the limit.


Table 4.2a: Explanation of Multiplicity Requirements


Multiplicity Requirement

Explanation

1 and only 1

The element must exist 1 and only 1 time within the parent element

0 or More

The element can exist 0 or More times within the parent element.

1 or More

The element must exist 1 or More times within the parent element.

0 or 1

The element can exist 0 or 1 time within the parent element.


Table 4.2a defines the types of multiplicities that are used in this section. Each type is accompanied by a brief explanation. The table also has definitions for SPMs for those elements that have a multiplicity of more than 1. The SPM indicates the smallest number of elements that must be supported by a processing system.


 

4.2.1. <lom> ElementXML Namespace Prefix: lom4.2.2. <general> ElementExample:4.2.2.1. <identifier> Element4.2.2.1.1. <catalog> ElementExample:4.2.2.1.2. <entry> ElementXML Binding Representation: <entry>Example:4.2.2.2. <title> ElementXML Binding Representation: <title>Example:4.2.2.3. <language> ElementExample:4.2.2.4. <description> ElementExample:4.2.2.5. <keyword> ElementExample:4.2.2.6. <coverage> ElementExample:4.2.2.7. <structure> ElementExample:4.2.2.8. <aggregationLevel> ElementExample:4.2.3. <lifeCycle> ElementExample:4.2.3.1. <version> ElementExample:4.2.3.2. <status> ElementExample:4.2.3.3. <contribute> ElementExample:4.2.3.3.1. <role> ElementXML Binding Representation: <role>Example:4.2.3.3.2. <entity> Element4.2.3.3.3. <date> ElementXML Binding Representation: <date>4.2.4. <metaMetadata> Element4.2.4.1. <identifier> Element4.2.4.1.1. <catalog> ElementExample:4.2.4.1.2. <entry> ElementXML Binding Representation: <entry>Example:4.2.4.2. <contribute> ElementExample:4.2.4.2.1. <role> ElementXML Binding Representation: <role>4.2.4.2.2. <entity> Element4.2.4.2.3. <date> ElementXML Binding Representation: <date>4.2.4.3. <metadataSchema> ElementExample:4.2.4.4. <language> ElementExample:4.2.5. <technical> ElementExample:4.2.5.1. <format> Element4.2.5.2. <size> ElementXML Binding Representation: <size>Example:4.2.5.3. <location> ElementExample:4.2.5.4. <requirement> Element4.2.5.4.1. <orComposite> Element4.2.5.4.1.1. <type> ElementXML Binding Representation: <type>4.2.5.4.1.2. <name> ElementXML Binding Representation: <name>Example:4.2.5.4.1.3. <minimumVersion> Element4.2.5.4.1.4. <maximumVersion> Element4.2.5.5. <installationRemarks> ElementExample:4.2.5.6. <otherPlatformRequirements> ElementExample:4.2.5.7. <duration> Element4.2.6. <educational> ElementExample:4.2.6.1. <interactivityType> ElementExample:4.2.6.2. <learningResourceType> ElementExample:4.2.6.3. <interactivityLevel> ElementExample:4.2.6.4. <semanticDensity> ElementExample:4.2.6.5. <intendedEndUserRole> ElementExample:4.2.6.6. <context> ElementExample:4.2.6.7. <typicalAgeRange> ElementExample:4.2.6.8. <difficulty> ElementExample:4.2.6.9. <typicalLearningTime> Element4.2.6.10. <description> ElementExample:4.2.6.11. <language> ElementExample:4.2.7. <rights> Element4.2.7.1. <cost> ElementXML Binding Representation: <cost>Example:4.2.7.2. <copyrightAndOtherRestrictions> Element4.2.7.3. <description> ElementExample:4.2.8. <relation> ElementExample:4.2.8.1. <kind> ElementXML Binding Representation: <kind>Example:4.2.8.2. <resource> ElementExample:4.2.8.2.1. <identifier> Element4.2.8.2.1.1. <catalog> ElementExample:4.2.8.2.1.2. <entry> ElementXML Binding Representation: <entry>4.2.8.2.2. <description> ElementExample:4.2.9. <annotation> ElementExample:4.2.9.1. <entity> ElementExample:4.2.9.2. <date> ElementXML Binding Representation: <date>4.2.9.3. <description> ElementExample:4.2.10. <classification> Element4.2.10.1. <purpose> ElementExample:4.2.10.2. <taxonPath> Element4.2.10.2.1. <source> ElementExample:4.2.10.2.2. <taxon> ElementXML Binding Representation: <taxon>4.2.10.2.2.1. <id> ElementXML Binding Representation: <id>Example:4.2.10.2.2.2. <entry> ElementXML Binding Representation: <entry>Example:4.2.10.3. <description> Element4.2.10.4. <keyword>Example:4.2.11. Common Data Types4.2.11.1. CharacterString Data Type4.2.11.2. LangString Data TypeXML Namespace Prefix: lomAttribute:Example:4.2.11.3. Vocabulary Data TypeExample:4.2.11.4. DateTime Data TypeExample:4.2.11.5. Duration Data TypeExample:4.2.11.6. VCard Data TypeExample: