Information about http://ltsc.ieee.org/wg12/files/LOMChangesSummary_2.pdf
19 July 2002 Summary of Changes v6.1 to Final Draft…
Tags: 19 july, draft document, draft version, final draft, learning technology, ltsc, metadata specifications, object metadata, revcom, side comparison, specifi, standard ieee, technology standards committee, v1, version 6, working group,Pages: 11
Language: english
Created: Sat Aug 31 00:10:25 2002
Display cached document
Page 1
Page 2
Page 3
Page 4
Page 5
Page 6
Page 7
Page 8
Page 9
Page 10
Page 11
19 July 2002 Summary of Changes v6.1 to Final Draft Standard IEEE 1484.12.1-2002
IEEE Standard for Learning Object Metadata
1484.12.1
Sponsored by the
Learning Technology Standards Committee of the IEEE (http://ltsc.ieee.org)
Summary of Changes
from
Working Group Draft v6.1, 6.2, 6.3, & 6.4
to
Final Draft* LOM Standard v1.0
The full and final 1484.12.LOM specification is available at http://ltsc.ieee.org/wg12/
* as approved by IEEE RevCom on June 12, 2002
Page 1 of 11
19 July 2002 Summary of Changes v6.1 to Final Draft Standard IEEE 1484.12.1-2002
Introduction
On June 12, 2002 the IEEE Review Committee approved the 1484.12.1 Learning Object Metadata draft making this the
first fully approved IEEE standard to emerge from the Learning Technology Standards Committee (LTSC).
In the course of developing this standard over the past few years, the LOM Working Group created many versions of the
draft document which were subsequently used by those wanting to understand, test and implement these initial metadata
specifications. With the completion of the balloting and approval process there is now a final standard document.
The following summary of changes has been created to assist those wanting to know how the final specification has
changed from the most previous drafts, specifically from Working Group draft version 6.1 to the final specifi cation which
represents the approved LOM 1484.12.1 standard v1.0
There is a single table which provides a side by side comparison between these two drafts with the changes highlighted in
color. This is then followed by a detailed list of each change.
The full and final 1484.12.LOM specification is available at http://ltsc.ieee.org/wg12/
Acknowledgements
Thanks from the Chair and Technical Editor of the IEEE 1484.12.1 Learning Object Metadata standard go to An drew
Johnson and Judy Brown from the University of Wisconsin, USA ADL Academic Co -Lab for their significant contribution
to create the initial summary and subsequent reviews of this document.
Page 2 of 11
19 July 2002 Summary of Changes
Previous Working Draft v6.1 v6.1 to Final Draft Standard IEEE 1484.12.1-2002
Final Draft LOMv1.0
1. General 1. General
1.1. Identifier 1.1. Identifier
1.2. Title 1.1.1. Catalog
1.3. CatalogEntry 1.1.2. Entry
1.3.1. Catalog 1.2. Title
1.3.2. Entry 1.3. Language
1.4. Language 1.4. Description
1.5. Description 1.5. Keyword
1.6. Keywords 1.6. Coverage
1.7. Coverage 1.7. Structure
1.8. Structure 1.8. Aggregation Level
1.9. Aggregation Level
2. Life Cycle 2. Life Cycle
2.1. Version 2.1. Version
2.2. Status 2.2. Status
2.3. Contribute 2.3. Contribute
2.3.1. Role 2.3.1. Role
2.3.2. Entity 2.3.2. Entity
2.3.3. Date 2.3.3. Date
3. Meta-MetaData 3. Meta-MetaData
3.1. Identifier 3.1. Identifier
3.2. CatalogEntry 3.1.1. Catalog
3.2.1. Catalog 3.1.2. Entry
3.2.2. Entry 3.2. Contribute
3.3. Contribute 3.2.1. Role
3.3.1. Role 3.2.2. Entity
3.3.2. Entity 3.2.3. Date
3.3.3. Date 3.3. Metadata Scheme
3.4. Metadata Scheme 3.4. Language
3.5. Language
4. Technical 4. Technical
4.1. Format 4.1. Format
4.2. Size 4.2. Size
4.3. Location 4.3. Location
4.4. Requirements 4.4. Requirement
4.4.1. Type 4.4.1. OrComponent
4.4.2. Name 4.4.1.1. Type
4.4.3. Minimum Version 4.4.1.2. Name
4.4.4. Maximum Version 4.4.1.3. Minimum Version
4.5. Installation Remarks 4.4.1.4. Maximum Version
4.6. Other Platform Requirements 4.5. Installation Remarks
4.7. Duration 4.6. Other Platform Requirements
5. Educational 4.7. Duration
5.1. Interactivity Type 5. Educational
5.2. Learning Resource Type 5.1. Interactivity Type
5.3. Interactivity Level 5.2. Learning Resource Type
5.4. Semantic Density 5.3. Interactivity Level
5.5. Intended End User Role 5.4. Semantic Density
5.6. Context 5.5. Intended End User Role
5.7. Typical Age Range 5.6. Context
5.8. Difficulty 5.7. Typical Age Range
5.9. Typical Learning Time 5.8. Difficulty
5.10. Description 5.9. Typical Learning Time
5.11. Language 5.10. Description
5.11. Language
6. Rights 6. Rights
6.1. Cost 6.1. Cost
6.2. Copyright and Other Restrictions 6.2. Copyright and Other Restrictions
6.3. Description 6.3. Description
7. Relation 7. Relation
7.1. Kind 7.1. Kind
7.2. Resource 7.2. Resource
7.2.1. Identifier 7.2.1. Identifier
7.2.2. Description 7.2.1.1. Catalog
7.2.3. CatalogEntry 7.2.1.2. Entry
7.2.3.1. Catalog 7.2.2. Description
7.2.3.2. Entry
8. Annotation 8. Annotation
8.1. Person 8.1. Entity
8.2. Date 8.2. Date
8.3. Description 8.3. Description
9. Classification 9. Classification
9.1. Purpose 9.1. Purpose
9.2. Taxon Path 9.2. Taxon Path
9.2.1. Source 9.2.1. Source
9.2.2. Taxon 9.2.2. Taxon
9.2.2.1. Id 9.2.2.1. Id Page 3 of 11
9.2.2.2. Entry 9.2.2.2. Entry
9.3. Description 9.3. Description
9.4. Keywords 9.4. Keyword
19 July 2002 Summary of Changes v6.1 to Final Draft Standard IEEE 1484.12.1-2002
Changes from version 6.1 to Final Draft of IEEE LTSC Learning Object Metadata
Previous Working Draft v6.1 Final Draft LOM v1.0
p. ii Added extra Participants.
p. iii Updated URL for Dublin Core
p. 5 Update Scope and Purpose, as per revised PAR
p. 5 Completed References
p. 6 Definition
Extended data element: An element of a data structure that is
Definition defined outside a standard and is permitted within an instance of
Extended data element: Not defined the data structure.
p. 6 Definition
Learning Object: For this standard, a learning object is defined as
Definition any entity, digital or non-digital, that may be used for learning,
Learning Object: Not defined education, or training.
p. 7, clause 4.2 Added:
The LOM data model is a hierarchy of data elements, including
aggregate data elements and simple data elements (leaf nodes of the
hierarchy). In the LOMv1.0 Base Schema, only leaf nodes have
individual values defined through their associated value space and
datatype. Aggregates in the LOMv1.0 Base Schema do not have
individual values. Consequently, they have no value space or
datatype
p.7, clause 4.2: Changed To:
data type: a set of distinct values; datatype: indicates whether the values are LangString (clause 7),
DateTime (clause 8), Duration (clause 9), Vocabulary (clause 10),
CharacterString or Undefined.
Page 4 of 11
19 July 2002 Summary of Changes v6.1 to Final Draft Standard IEEE 1484.12.1-2002
Previous Working Draft v6.1 Final Draft LOM v1.0
p.7, clause 4.2: Changed To:
Some data elements contain sub-elements. Data elements with sub- Extensions to the LOMv1.0 Base Schema shall retain the value
elements shall not have values directly; only data elements with no space and datatype of data elements from the LOMv1.0 Base
sub-elements shall have values directly. Data elements with sub- Schema. Extensions shall not define datatypes or value spaces for
elements shall have values indirectly only, through their sub- aggregate data elements in the LOMv1.0 Base Schem a.
elements. As an example, 7:2:Relation.Resource has a value
indirectly only, through 7.2.1:Relation.Resource.Identifier, The numbering schema of the data elements represents an
7.2.2:Relation.Resource.Description and aggregation hierarchy of data elements and their components. As
7.2.3:Relation.Resource.CatalogEntry. The latter data element in an example, the aggregate data element 7:2:Relation.Resource has
turn contains sub-elements, and thus has a value indirectly only, two components, 7.2.1:Relation.Resource.Identifier and
through 7.2.3.1:Relation.Resource.CatalogEntry.Catalog and 7.2.2:Relation.Resource.Description. The former data element is in
7.2.3.2:Relation.Resource.CatalogEntry.Entry only. (See clause 4.3 turn an aggregate, as it contains components:
for the interpretation of data elements with sub-elements that have 7.2.1.1:Relation.Resource.Identifier.Catalog and
list values. 7.2.1.2:Relation.Resource.Identifier.Entry. (See clause 4.3 for the
interpretation of aggregate data elements that have list values.)
All data elements are optional: this means that a conforming LOM
instance may include values for any data element defined in clause
6. As the LOMv1.0 Base Schema in clause 6 imposes an
aggregation relationship, components can by definition only be
present in a LOM instance as a component of the aggregate
element to which they belong. As an example,
7.2.1:Relation.Resource.Identifier appears by definition as a
component of 7.2:Relation.Resource. In that sense, the presence of
the component implies automatically the presence of the aggregate
element to which the component belongs.
p.8, clause 4.3 Removed
A list of values shall contain at least one value. Implementations
may use a list of zero length for internal operations, but a zero
length list value shall not be distinguishable from no value. Where a
value is intended to be present in an implementation, a zero-length
list shall not be valid as a final value.
p.8, clause 4.4 Changed to:
The value of data elements with associated vocabularies shall be If the source is "LOMv1.0", then the value space is described by
represented as a (source, value) pair. this edition of this Standard.
q If the source is "LOMv1.0", then the value shall be
contained in the vocabulary.
q If the source is not "LOMv1.0", then the value should not
be contained in the vocabulary.
Page 5 of 11
19 July 2002 Summary of Changes v6.1 to Final Draft Standard IEEE 1484.12.1-2002
Previous Working Draft v6.1 Final Draft LOM v1.0
p.9, clause 4.7 Changed to:
For each of the data elements, the specification includes the data For each data element, the specification includes the datatype (e.g.,
type from which it derives its values, such as LangString or Date, LangString, DateTime, etc.) of its values.
etc. These will be defined separately, and will be implemented in a
particular way in a particular system. In order to maximize This Standard does not define tokens for element names or
interoperability, future work may define a common representation vocabulary values. It is expected that such tokens will be defined in
for these data types. In the absence of such a common bindings of this Standard.
representation, an exchange format, such as XML, would allow
systems with different representations to achieve interoperability Within the LOMv1.0 Base Schema, the ordering of the categories
through a conversion process. and the data elements within the categories and subcategories is
informational. An instance of the LOMv1.0 Base Schema shall
preserve the nesting of categories and subcategories, but the
instance need not order the categories or the subitems within a
category or subcategory. For example, category 5:Educational may
appear before category 1:General, and within category General,
Item 1.3:General.Language may appear before item
1.2:General.Title.
p.9 clause 5 Changed to:
A strictly conforming LOM metadata instance shall consist solely · A strictly conforming LOM metadata instance shall consist
of LOM data elements. A conforming LOM metadata instance may solely of LOM data elements.
contain extension data elements. Extension data elements shall not · A conforming LOM metadata instance may contain extended
replace data elements in the LOM structure. NOTE--All data data elements.
elements in the metadata instance should describe characteristics as · A LOM instance that contains no value for any of the LOM
defined by this standard. data elements is a conforming instance.
(For example, the user shall not abuse the title data element to In order to maximize semantic interoperability, extended data
describe the fonts used in the document.) Abusing data elements elements should not replace data elements in the LOM structure.
would compromise semantic interoperability. This means that an organization should not introduce new data
NOTE--An organization/application can allow extensions and refer elements of its own that replace LOM data elements. As an
to LOM conformance in addition to conformance to something else. example, an organization should not introduce a new data element
"name" that would replace 1.2:General.Title.
NOTE:--In order to maximize semantic interoperability, users of
this Standard are encouraged to carefully map their metadata
information to the data elements of this Standard. For example, the
user should not map an element to describe the fonts used in the
document to the data element 1.2:General.Title
Page 6 of 11
19 July 2002 Summary of Changes v6.1 to Final Draft Standard IEEE 1484.12.1-2002
Previous Working Draft v6.1 Final Draft LOM v1.0
Tagging Practice Tagging Practice
DateTime: Exists, only format shown is YYYY-MM-DD, any DateTime: Exists, format based on ISO 8601:2000. Old format is
practice allowed in ISO 8601 is allowed. also allowed.
Use:
[YYYY][-MM[-DD[Thh[:mm[:ss[.s[TZD]]]]]]]
Where:
YYYY = four digit year ( >= 0001)
MM = two-digit month (01 12 where 01 is January , etc)
DD = two-digit day(01 31 depending on value of month and
year)
hh = two digits of hour (00 through 23)(am/pm NOT allowed)
mm = two digits of minute (00 through 59)
ss = two digits of second (00 through 59)
s = one or more digits representing a decimal fraction of a second
TZD = time zone designator ("Z" for UTC +hh:mm or hh:mm)
Tagging Practice Tagging Practice
Duration: Does not exist. Duration: Exists, format based on ISO 8601:2000.
Use:
P[yY][mM][dD][T[hH][nM][s[.s]S]]
Where:
y = number of years (integer, >0, not restricted)
m = number of months (integer, >0, not restricted, e.g., > 11 is
acceptable)
d = number of days (integer, >0, not restricted, e.g., > 31 is
acceptable)
h = number of hours (integer, >0, not restricted, e.g., > 23 is
acceptable)
n = number of minutes (integer, >0, not restricted, e.g., > 59 is
acceptable)
s = number of seconds (integer, >0, not restricted, e.g., > 59 is
acceptable)
The character literal designators "Y", "M", "D", "H", "M", and
"S" must appear if the corresponding non-zero value is present.
Otherwise, if the corresponding value is zero, it may be omitted
"P" must always appear, and "T" can only be eliminated if h, n, and
s are all = 0(time is in years, months, and days only).
Meta-data Information Model Element: Meta-data Information Model Element:
1.1 Identifier: RESERVED 1.1 Identifier: Now has a smallest permitted maximum of 10.
Now contains sub-elements
1.1.1 Catalog and 1.1.2 Entry
Meta-data Information Model Element: Meta-data Information Model Element:
1.3 CatalogEntry: Existed 1.3 CatalogEntry: Eliminated. Its sub-elements
have been moved into 1.1 Identifier.
Page 7 of 11
19 July 2002 Summary of Changes v6.1 to Final Draft Standard IEEE 1484.12.1-2002
Previous Working Draft v6.1 Final Draft LOM v1.0
Meta-data Information Model Element: Meta-data Information Model Element:
1.3.1 Catalog: Described as "The name of the catalog (i.e. listing 1.3.1 Catalog: Moved to 1.1.1 Catalog. New Description is "The
identification system)." name or designator of the identification or cataloging scheme for
this entry.
A namespace scheme."
Meta-data Information Model Element: Meta-data Information Model Element:
1.3.2 Entry: Described as "Actual string value 1.3.2 Entry: Moved to 1.1.2 Entry. New Description is "The
of the entry within the catalog (i.e. listing identification system)." value of the identifier within the identification or cataloging
scheme that designates or identifies this learning object. A
namespace specific string."
Meta-data Information Model Element: Meta-data Information Model Element:
1.4 Language: Existed 1.4 Language: Moved. It is now 1.3 Language.
If all structural changes are done, it will not effect metadata
structure or ordering, only the numbering scheme.
Meta-data Information Model Element: Meta-data Information Model Element:
1.5 Description: Existed 1.5 Description: Moved. It is now 1.4 Description.
If all structural changes are done, it will not effect metadata
structure or ordering, only the numbering scheme.
Meta-data Information Model Element: Meta-data Information Model Element:
1.6 Keywords: Existed 1.6 Keywords: Moved. It is now 1.5 Keyword.
If all structural changes are done, it will not effect metadata
structure or ordering, only the numbering scheme.
Meta-data Information Model Element: Meta-data Information Model Element:
1.7 Coverage: Existed 1.7 Coverage: Moved. It is now 1.6 Coverage.
If all structural changes are done, it will not effect metadata
structure or ordering, only the numbering scheme.
Meta-data Information Model Element: Meta-data Information Model Element:
1.8 Structure: Existed 1.8 Structure: Moved. It is now 1.7 Structure.
If all structural changes are done, it will not effect metadata
structure or ordering, only the numbering scheme.
Changed vocabulary to atomic, collection, networked, hierarchical,
linear
Meta-data Information Model Element: Meta-data Information Model Element:
1.9 AggregationLevel: Existed 1.9 AggregationLevel: Moved. It is now 1.8 AggregationLevel.
If all structural changes are done, it will not effect metadata
structure or ordering, only the numbering scheme. Comment: The entries on 1.3-1.9 are
all basically the same comment. Maybe
better to regroup as one comment?
Meta-data Information Model Element: Meta-data Information Model Element: (Might look rather worrying at first sight
2.3.2 Entity: Existed. Vcard not specific. 2.3.2 Entity: Vcard becomes more specific. if one doesn't realize this is just the
consequence of subsuming CatalogEntry
Link for information: http://www.ietf.org/rfc/rfc2426.txt under Identifier.)
Page 8 of 11
19 July 2002 Summary of Changes v6.1 to Final Draft Standard IEEE 1484.12.1-2002
Previous Working Draft v6.1 Final Draft LOM v1.0
Meta-data Information Model Element: Meta-data Information Model Element:
2.3.3 Date: Existed. 2.3.3 Date: DataType Change, Observe DateTime change above.
Meta-data Information Model Element: Meta-data Information Model Element:
3.1 Identifier: RESERVED 3.1 Identifier: Now has a smallest permitted maximum of 10.
Now contains sub-elements
3.1.1 Catalog and 3.1.2 Entry
Meta-data Information Model Element: Meta-data Information Model Element:
3.2 CatalogEntry: Existed 3.2 CatalogEntry: Eliminated. Its sub-elements
have been moved into 3.1 Identifier.
Meta-data Information Model Element: Meta-data Information Model Element:
3.2.1 Catalog: Described as "The name of the catalog (i.e. listing 3.2.1 Catalog: Moved to 3.1.1 Catalog. New Description is "The
identification system)." name or designator of the identification or cataloging scheme for
this entry.
A namespace scheme."
Meta-data Information Model Element: Meta-data Information Model Element:
3.2.2 Entry: Described as "Actual string value 3.2.2 Entry: Moved to 3.1.2 Entry. New Description is "The
of the entry within the catalog (i.e. listing identification system)." value of the identifier within the identification or cataloging
scheme that designates or identifies this learning object. A
namespace specific string."
Meta-data Information Model Element: Meta-data Information Model Element:
3.2.3 Date: Existed. 3.2.3 Date: DataType Change, Observe DateTime change above.
Meta-data Information Model Element: Meta-data Information Model Element:
3.3 Contribute (and all of its sub-elements): Existed 3.3 Contribute (and all of its sub-elements): Moved. It is now 3.2
Contribute (sub-elements follow as before).
If all structural changes are done, it will not effect metadata
structure or ordering, only the numbering scheme.
Meta-data Information Model Element: Meta-data Information Model Element:
3.3.2 Contribute Existed. Vcard not specific. 3.3.2 Entity: Vcard becomes more specific.
Link for information: http://www.ietf.org/rfc/rfc2426.txt
Meta-data Information Model Element: Meta-data Information Model Element:
3.4 Metadatascheme: Existed 3.4 Metadatascheme: Moved. It is now 3.3 Metadatascheme
If all structural changes are done, it will not effect metadata
structure or ordering, only the numbering scheme.
Meta-data Information Model Element: Meta-data Information Model Element:
3.5 Language: Existed 3.5 Language: Moved. It is now 3.4 Language
If all structural changes are done, it will not effect metadata
structure or ordering, only the numbering scheme.
Page 9 of 11
19 July 2002 Summary of Changes v6.1 to Final Draft Standard IEEE 1484.12.1-2002
Previous Working Draft v6.1 Final Draft LOM v1.0
Meta-data Information Model Element: Meta-data Information Model Element:
OrComposite: Did Not Exist OrComposite: Created. It is now 4.4.1 OrComposite. All
children of 4.4 Requirements are moved inside of 4.4.1
OrComposite.
Description: Grouping of multiple requirements. The composite
requirement is satisfied when one of the component requirements is
satisfied, e.g., the logical connector is OR.
Smallest Permitted Maximum: 40
Meta-data Information Model Element: Meta-data Information Model Element:
4.4.1 Type: Existed 4.4.1 Type: Moved. It is now 4.4.1.1 Type
Meta-data Information Model Element: Meta-data Information Model Element:
4.4.2 Name: Existed 4.4.2 Name: Moved. It is now 4.4.1.2 Name
Meta-data Information Model Element: Meta-data Information Model Element:
4.4.3 MinimumVersion: Existed 4.4.3 MinimumVersion: Moved. It is now 4.4.1.3
MinimumVersion
Meta-data Information Model Element: Meta-data Information Model Element:
4.4.4 MaximumVersion: Existed 4.4.4 MaximumVersion: Moved. It is now 4.4.1.4
MaximumVersion
Meta-data Information Model Element: Meta-data Information Model Element:
4.7 Duration: DataType is Date 4.7 Duration: DataType Change. Type is now Duration. Observe
Duration change above
Meta-data Information Model Element: Removed Undefined from Value Space
5.1 Interactivity Type
Meta-data Information Model Element: Added lecture to Value Space
5.2 Learning Resource Type
Meta-data Information Model Element: Added elaborate examples
5.4 Semantic Density
Meta-data Information Model Element: Restricted vocabulary to school, higher education, training, other.
5.6 Context
Meta-data Information Model Element: Meta-data Information Model Element:
5.9 TypicalLearningTime: DataType is Date 5.9 TypicalLearningTime: DataType Change. Type is now
Duration. Observe Duration change above
Meta-data Information Model Element: Meta-data Information Model Element:
7.2.1 Identifier: RESERVED 7.2.1 Identifier: Now has a smallest permitted maximum of 10.
Now contains sub-elements
7.2.1.1 Catalog and 7.2.1.2 Entry
Meta-data Information Model Element: Meta-data Information Model Element:
7.2.3 CatalogEntry: Existed 7.2.3 CatalogEntry: Eliminated. Its sub-elements
have been moved into 7.2.1 Identifier.
Page 10 of 11
19 July 2002 Summary of Changes v6.1 to Final Draft Standard IEEE 1484.12.1-2002
Previous Working Draft v6.1 Final Draft LOM v1.0
Meta-data Information Model Element: Meta-data Information Model Element:
7.2.3.1 Catalog: Described as "The name of the catalog (i.e. listing 7.2.3.1 Catalog: Moved to 7.2.1.1 Catalog. New Description is
identification system)." "The name or designator of the identification or cataloging scheme
for this entry.
A namespace scheme."
Meta-data Information Model Element: Meta-data Information Model Element:
7.2.3.2 Entry: Described as "Actual string value 7.2.3.2 Entry: Moved to 7.2.1.2 Entry. New Description is "The
of the entry within the catalog (i.e. listing identification system)." value of the identifier within the identification or cataloging
scheme that designates or identifies this learning object. A
namespace specific string."
Meta-data Information Model Element: Meta-data Information Model Element:
8.1 Person: Existed. Vcard not specific. 8.1 Entity: Vcard becomes more specific.
Link for information: http://www.ietf.org/rfc/rfc2426.txt
Meta-data Information Model Element: Meta-data Information Model Element:
8.2 Date: Existed 8.2. Date: DataType Change, Observe DateTime change above.
Meta-data Information Model Element: Added competency to vocabulary
9. 1 Purpose: Existed
Page 11 of 11