GNU Edu and SCORM
SCORM uses LOM metadata and defines 3 validation approaches:
1. the Strict Schema Validation Approach supports uniqueness constraints,
uses LOM vocabulary only, and admits no extensions
2. the Custom Schema Validation Approach supports uniqueness constraints,
but admits custom vocabularies and extensions
3. the Loose Schema Validation Approach
In the following tables, we show how compliant GNU Edu is to LOM metadata,
and how far we go in the validation approach.
Our conclusion is that GNU Edu conforms to SCORM Custom
Schema Validation Approach and is close to the strict validation
approach.
LOM.general
| LOM Attribute |
mandatory (assets) |
mandatory (SCOs) |
GNU Edu equivalent |
conforms to constraints (uniqueness ..) |
conforms to LOM vocabularies (when any) |
notes |
| Identifier |
Y |
Y |
url_document |
Y |
- |
|
| Title |
Y |
Y |
title |
Y |
- |
|
| Language |
N |
N |
lang |
Y |
Y |
conforms to RFC 4646, RFC 4647 and ISO 639-2 |
| Description |
Y |
Y |
description |
Y |
- |
|
| Keyword |
Y |
N |
keyword |
Y |
- |
own vocabulary |
| Coverage |
N |
N |
subject |
Y |
- |
own vocabulary, organized in a tree structure |
| Structure |
N |
N |
``atomic'' |
Y |
Y |
|
| Aggregation Level |
N |
N |
``1'' |
Y |
Y |
|
LOM.lifeCycle
| LOM Attribute |
mandatory (assets) |
mandatory (SCOs) |
GNU Edu equivalent |
conforms to constraints (uniqueness ..) |
conforms to LOM vocabularies (when any) |
notes |
| version |
N |
Y |
version |
Y |
Y |
|
| status |
N |
Y |
status |
Y |
Y |
|
| contribute |
N |
N |
author(s) |
Y |
Y |
role=''author'', entity, does not implement date |
| LOM Attribute |
mandatory (assets) |
mandatory (SCOs) |
GNU Edu equivalent |
conforms to constraints (uniqueness ..) |
conforms to LOM vocabularies (when any) |
notes |
| identifier |
Y |
Y |
id |
Y |
- |
|
| contribute |
N |
N |
last editor |
Y |
Y |
role=''validator'' + entity + date |
| metadata schema |
Y |
Y |
LOMv1.0 |
Y |
- |
|
| language |
N |
N |
``en'' |
Y |
Y |
|
| (missing) |
- |
- |
license |
- |
- |
|
LOM.technical
| LOM Attribute |
mandatory (assets) |
mandatory (SCOs) |
GNU Edu equivalent |
conforms to constraints (uniqueness ..) |
conforms to LOM vocabularies (when any) |
notes |
| format |
Y |
Y |
format |
Y |
Y |
for text files, 'charset' is missing from the LOM standard |
| size |
N |
N |
filesize |
Y |
Y |
|
| location |
N |
N |
- |
- |
- |
|
| requirement |
N |
N |
software |
Y |
N |
correspondance implemented in GNU Edu LOM export(*) |
| installation remarks |
N |
N |
- |
- |
- |
could be automated from information about every IG software |
| other platform requirements |
N |
N |
- |
- |
- |
could be automated from information about every IG software |
| duration |
N |
N |
- |
- |
- |
|
(*) IEEE LOM has only 2 types (operating system or browser) and most educational
documents will not require either an operating system or a specific browser,
but they might require a specific software; so GNU Edu 'software' element
relies on a tree-like custom vocabulary for required software; GNU Edu
implements its multiplicity ("and"); does not implement logical "or"; the
tree structure can be seen in my document/meta/software.xml
LOM.educational
| LOM Attribute |
mandatory (assets) |
mandatory (SCOs) |
GNU Edu equivalent |
conforms to constraints (uniqueness ..) |
conforms to LOM vocabularies (when any) |
notes |
| Interactivity Type |
N |
N |
interactivity type |
Y |
Y |
|
| Learning Resource Type |
N |
N |
learning resource type |
Y |
N |
vocabulary correspondance implemented in GNU Edu LOM export |
| Interactivity Level |
N |
N |
interactivity level |
Y |
Y |
|
| Semantic Density |
N |
N |
- |
- |
- |
|
| Intended End User Role |
N |
N |
``teacher'' |
Y |
Y |
|
| Context |
N |
N |
audience |
Y |
Y |
GNU Edu 'audience' contains information for both Context and Typical Age Range |
| Typical Age Range |
N |
N |
audience |
Y |
- |
|
| Difficulty |
N |
N |
difficulty |
Y |
Y |
|
| Typical Learning Time |
N |
N |
- |
- |
- |
|
| Description |
N |
N |
annotation |
Y |
- |
|
| Language |
N |
N |
- |
- |
- |
|
LOM.rights
| LOM Attribute |
mandatory (assets) |
mandatory (SCOs) |
GNU Edu equivalent |
conforms to constraints (uniqueness ..) |
conforms to LOM vocabularies (when any) |
notes |
| Cost |
Y |
Y |
``no'' |
Y |
Y |
|
| Copyright and Other Restrictions |
Y |
Y |
license |
Y |
- |
our information 'license' contains LOM attributes |
| Description |
N |
N |
license |
Y |
- |
Copyright and Description |
LOM.Relation
| LOM Attribute |
mandatory (assets) |
mandatory (SCOs) |
GNU Edu equivalent |
conforms to constraints (uniqueness ..) |
conforms to LOM vocabularies (when any) |
notes |
| kind |
N |
N |
- |
- |
- |
|
| resource |
N |
N |
- |
- |
- |
|
LOM.Annotation
| LOM Attribute |
mandatory (assets) |
mandatory (SCOs) |
GNU Edu equivalent |
conforms to constraints (uniqueness ..) |
conforms to LOM vocabularies (when any) |
notes |
| Entity |
N |
N |
- |
- |
- |
|
| Date |
N |
N |
- |
- |
- |
|
| Description |
N |
N |
- |
- |
- |
|
LOM.Classification
| LOM Attribute |
mandatory (assets) |
mandatory (SCOs) |
GNU Edu equivalent |
conforms to constraints (uniqueness ..) |
conforms to LOM vocabularies (when any) |
notes |
| Purpose |
N |
N |
``educational purpose'' |
Y |
Y |
|
| Taxon Path |
N |
N |
source=''GNU Edu'', taxon.id=item id, entry=item label |
Y |
Y |
|
| Description |
N |
N |
description |
Y |
- |
|
| Keyword |
N |
N |
keyword |
Y |
- |
|
Conclusion
- GNU Edu conforms Custom Schema Validation Approach, with very little difference with the Strict Validation Approach
- for assets, GNU Edu implements every mandatory LOM attribute + 22 optional LOM attributes
- for SCOs, GNU Edu implements every mandatory LOM attribute + 21 optional LOM attributes
- in LOM "rights" part, the attribute "license" is severely missing from the LOM standard
- in LOM "metadata" part, the attribute "license" is severely missing from the LOM standard
