Home | Back

Vocabulary Comparison Chart: IMS vs. iLumina

(All specifications have been included, regardless if they have associated vocabularies or not. Links lead to the definitions of the listed terms. Items 1.10-1, 1.11-1, and 4.8-1 are suggested additions.)

Nr

Name

IMS Vocabulary

Note

iLumina Vocabulary

BaseScheme

1

general

 

 

 

1.1

identifier

 

1. This element can be transparent to the meta-data creator. It can be created by the meta-data management system.

2. This element corresponds with the Dublin Core element DC.Identifier.

3. You can use your own ID method or the IMS best practice.

Implemented

1.2

title

 

1. The title can be an already existing one or it may be created by the indexer ad hoc.

2. Corresponds with Dublin Core element DC.Title.

Implemented

1.3

catalogentry

 

One of the catalog entries can be generated automatically by the tool.

 

1.3.1

catalog

 

Generally the name of the catalog.

 

1.3.2

entry

 

Generally the number in the catalog named in Catalog (1.3.1).

 

1.4

language

LanguageID = Langcode('-'Subcode)*, with Langcode a two-letter language code as defined by ISO639 and Subcode a country code from ISO3166.

1. The approach adopted is compatible with that of the xml:lang attribute and is defined by RFC1766.

2. ISO639 deals with 'ancient' languages, like Greek and Latin.

3. Tool should provide useful default.

4. It is customary to give the language code in lower case and the country code (if any) in upper case. However, the values are case insensitive.

5. This element corresponds with the Dublin Core element DC.Language.

Implementing two-letter language code, but not the country code.

1.5

description

 

This element corresponds to the Dublin Core element DC.Description.

Implemented

1.6

keyword

 

It is strongly recommended not to use this element for characteristics that can be described by other elements.

Implemented

1.7

coverage

 

This element corresponds with the Dublin Core element DC.Coverage.

 

1.8

structure

Collection, Mixed, Linear, Hierarchical, Networked, Branched, Parceled, Atomic

 

Collection, Individual Learning Resource, Not Specified

1.9

aggregationlevel

restricted range: 1 - 4

Level 1 means smallest level of aggregation, e.g. raw media data or fragments.

Level 2 refers to a collection of atoms, e.g. an HTML document with some embedded pictures or a lesson.

Level 3 indicates a collection of level 1 resources, e.g. a 'web' of HTML documents, with an index page that links the pages together or a unit.

Finally, level 4 refers to the largest level of granularity, e.g. a course.

 

1.10-1 thumbnail    

80 X 120 pixel image of the object.

1.11-1 character large object (CLOB)     XML encoding of the resource.

2

lifecycle

 

 

 

2.1

version

 

 

Implemented

2.2

status

Draft, Final, Revised, Unavailable

 

Submitted, In Review, Accepted, Unavailable

2.3

contribute

 

 

 

2.3.1

role

Author, Publisher, Unknown, Initiator, Terminator, Validator, Editor, Graphical Designer, Technical Implementer, Content Provider, Technical Validator, Educational Validator, Script Writer, Instructional Designer

It is recommended that exactly one instance of Author exists.

Author, Publisher, Editor, Submitter, Production Personnel

 

2.3.2

entity

vCard <http://www.imc.org/pdi/>

1. If Role (2.3.1) is Author, then the entity is typically a person and this element corresponds with the Dublin Core element DC.Creator. (Examples of a Creator include a person, an organisation, or a service. Typically, the name of a Creator should be used to indicate the entity.)

2. If Role equals Publisher, then the entity is typically an organization and this element corresponds with the Dublin Core element DC.Publisher. (Examples of a Publisher include a person, an organisation, or a service. Typically, the name of a Publisher should be used to indicate the entity.

3. If Role is not equal to Author or Publisher, then this element corresponds with the Dublin Core element DC.Contributor. (Examples of a Contributor include a person, an organisation, or a service. Typically, the name of a Contributor should be used to indicate the entity.)

4. If the entity is an organization, then it is typically a university department, company, agency, institute, etc. under whose responsibility the contribution was made.

Implemented

2.3.3

date

 

 

Implemented

3

metametadata

 

 

 

3.1

identifier

 

This element can be transparent to the meta-data creator. It can be created by the meta-data management system. You can use your own ID method or the IMS best practice

 

3.2

catalogentry

 

One of the catalog entries can be generated automatically by the tool.

 

3.2.1

catalog

 

Generally system generated.

 

3.2.2

entry

 

Generally system generated.

 

3.3

contribute

 

 

 

3.3.1

role

Creator, Validator

It is recommended that exactly one instance of creator exists.

 

3.3.2

entity

vCard <http://www.imc.org/pdi/>

 

 

3.3.3

date

 

 

 

3.4

metadatascheme

 

1. Generally user selectable or system generated.

2. If multiple values are provided, then the meta-data instance conforms to multiple meta-data schemes.

 

3.5

language

see general.language

"none" is an acceptable value.

 

4

technical

 

 

 

4.1

format

restricted: MIME type or 'non-digital'

1. Can be used to identify the software needed to access the resource.

2. This element corresponds with the Dublin Core element DC.Format. (Typically, Format may include the media-type or dimensions of the resource. Format may be used to determine the software, hardware or other equipment needed to display or operate the resource. Examples of dimensions include size and duration. Recommended best practice is to select a value from a controlled vocabulary (for example, the list of Internet Media Types [MIME] defining computer media formats)).

Mime Types 

4.2

size

 

This refers to the actual size of the resource, and not to the size of a compressed version of the resource.

Implemented as kBytes

4.3

location

 

 

Implemented

4.4

requirement

 

 

 

4.4.1

type

Operating System, Browser

 

None, Operating System, Browser, Application, Plugin, Programming Language

4.4.2

name

if Type='Operating System', then vocabulary: {PC-DOS, MS- Windows, MacOS, Unix, Multi-OS, Other, None}

if Type='Browser' then vocabulary: {Any, Netscape Communicator, Microsoft Internet Explorer, Opera}

if other type, then open vocabulary

May be derived from Format (4.1) automatically, e.g., HTML implies "Multi-OS"

None, Windows, Windows NT, Windows CE, MS-DOS, Mac OS, Unix, VMS, Internet Explorer, Netscape, RealPlayer, Toolbook, Unzip, Chime Plugin, Neuron Plugin, Shockwave Plugin, C, C++, Java, Visual Basic, Fortran, Perl, UNIX Shell Script, TK/TCL, Flash Plugin, Quicktime, MPEG.

4.4.3

minimumversion

 

 

Implemented

4.4.4

maximumversion

 

 

 

4.5

installationremarks

 

 

 

4.6

otherplatform

requirements

 

 

Implemented

4.7

duration

ISO8601

This is especially useful for sounds, movies, or animations.

 
4.8-1 mediatype     Audio, Animation, Chemical Structure, Database, Executable, Image, Java Applet, Math Application, Portable Document, Presentation, Software Source Code, Spreadsheet, Video, Web Page, Word Processing Document

 

5

educational

 

 

 

5.1

interactivitytype

Active, Expositive, Mixed, Undefined

In an expositive resource, the information flows mainly from the resource to the learner. Expositive documents are typically used for learning- by- reading.

In an active learning object, information also flows from the learner to the resource. Active documents are typically used for learning- by- doing.

note: Activating links to navigate in hypertext documents is not considered as an information flow. Thus, hypertext documents are expositive.

 

5.2

learning

resourcetype

Exercise, Simulation, Questionnaire, Diagram, Figure, Graph, Index, Slide, Table, Narrative Text, Exam, Experiment, ProblemStatement, SelfAssesment

This element corresponds with the Dublin Core element 'Resource Type'. The vocabulary is adapted for the specific purpose of learning objects. (Collection, Dataset, Event, Image, Interactive, Resource, Service, Software, Sound, Text).

Course, Lesson, Book, Presentation, Example, Demonstration, Simulation, Lab, Exercise, Assessment, Project, Dataset, Syllabus, Lesson Plan, Teacher Tool, Learner Tool, Manager Tool, None Specified

 

5.3

interactivitylevel

very low, low, medium, high, very high

 

Low, High, Not Specified

5.4

semanticdensity

very low, low, medium, high, very high

 

 

5.5

intended

enduserrole

Teacher, Author, Learner, Manager

A learner works with a resource in order to learn something.

An author creates or publishes a resource.

A manager manages the delivery of the resource, e.g., a university or college. The document for a manager is typically a curriculum.

Learner, Teacher, Manager, Not Specified

 

5.6

context

Primary Education, Secondary Education, Higher Education, University First Cycle, University Second Cycle, University Postgrade, Technical School First Cycle, Technical School Second Cycle, Professional Formation, Continuous Formation, Vocational Training

 

 

5.7

typicalagerange

 

 

 

5.8

difficulty

very easy, easy, medium, difficult, very difficult

 

Very Easy, Easy, Medium, Difficult, Very Difficult, Not Specified

5.9

typicallearningtime

ISO8601

 

 

5.10

description

 

 

 

5.11

language

 

See general.language.

 

6

rights

 

Intent is to reuse results of ongoing work in the Intellectual Property Right and e-commerce communities. This category currently provides the absolute minimum level of detail only.

 

6.1

cost

yes, no

 

Implemented

6.2

copyrightand

otherrestrictions

yes, no

 

Implemented

6.3

description

 

 

Implemented

7

relation

 

 

 

7.1

kind

Dublin Core: {IsPartOf, HasPart, IsVersionOf, HasVersion, IsFormatOf, HasFormat, References, IsReferencedBy, IsBasedOn, IsBasisFor, Requires, IsRequiredBy

This element corresponds with the Dublin Core element DC.Relation.(Recommended best practice is to reference the resource by means of a string or number conforming to a formal identification system.)

IsPartOf, IsBasedOn

 

7.2

resource

 

 

 

7.2.1

identifier

 

 

Implemented

7.2.2

description

 

 

 

7.2.3

catalogentry

 

See general.catalogentry.

 

8

annotation

 

 

 

8.1

person

vCard <http://www.imc.org/pdi/>

 

 

8.2

date

 

 

 

8.3

description

 

 

 

9

classification

 

1. End users can refer to their preferred classifications.

2. If Purpose (9.1) equals Discipline, then this category corresponds with the Dublin Core element DC.Subject. (Typically, a Subject will be expressed as keywords, key phrases or classification codes that describe a topic of the resource. Recommended best practice is to select a value from a controlled vocabulary or formal classification scheme.)

 

9.1

purpose

Discipline, Idea, Prerequisite, Educational Objective, Accessibility Restrictions, Educational Level, Skill Level, Security Level

 

Hardcoded as iLumina Discipline.

9.2

taxonpath

 

There may be different paths, in the same or different classifications, that describe the same characteristic.

 

9.2.1

source

 

Any recognized "official" taxonomy, any user-defined taxonomy. A tool may provide the top-level entries of a well-established classification (LOC, UDC, DDC, etc.).

Implemented in accordance with accepted taxonomy.

9.2.2

taxon

 

A TaxonPath can have a depth from 1 to 9. Normal values are between 2 and 4.

Implemented in accordance with accepted taxon path.

9.2.2.1

id

 

Repertoire of ISO/IEC 10646-1

 

9.2.2.2

entry

 

 

 

9.3

description

 

 

Hardcoded as iLumina Classification Structure.

9.4

keyword

 

 

 



Last modified:
About · Technical Documents · Policies
Copyright © 2001-2003 iLumina.org