Esta tabla fue tomada de forma parcial del documento IMS Meta-Data Information Model Versión 1.2.1, y se utilizó como guía para la asignación de valores de los elementos analizados en los apartados 7.2.4 y 7.2.5.
|
Name |
Domain |
Type |
Note |
1 |
general |
- |
- |
- |
1.1 |
identifier |
- |
String |
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.
|
1.2 |
title |
- |
LangStringType (1000 char) |
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. |
1.3 |
catalogentry |
- |
- |
One of the catalog entries can be generated automatically by the tool. |
1.3.1 |
catalog |
- |
String (1000 char) |
Generally the name of the catalog. |
1.3.2 |
entry |
- |
LangStringType (1000 char) |
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. |
String (100 char) |
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. |
1.5 |
description |
- |
LangStringType (2000 char) |
This element corresponds to the Dublin Core element DC.Description. |
1.6 |
keyword |
- |
LangStringType (1000 char) |
It is strongly recommended not to use this element for characteristics that can be described by other elements. |
1.7 |
coverage |
- |
LangStringType (1000 char) |
This element corresponds with the Dublin Core element DC.Coverage. |
1.8 |
structure |
vocabulary: {Collection, Mixed, Linear, Hierarchical, Networked, Branched, Parceled, Atomic} |
Vocabulary |
- |
1.9 |
aggregationlevel |
restricted range: 1 - 4 |
Vocabulary |
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. |
2 |
lifecycle |
- |
- |
- |
2.1 |
version |
- |
LangStringType (50 char) |
- |
2.2 |
status |
vocabulary: {Draft, Final, Revised, Unavailable} |
Vocabulary |
- |
2.3 |
contribute |
- |
- |
- |
2.3.1 |
role |
vocabulary: {Author, Publisher, Unknown, Initiator, Terminator, Validator, Editor, Graphical Designer, Technical Implementer, Content Provider, Technical Validator, Educational Validator, Script Writer, Instructional Designer} |
Vocabulary |
It is recommended that exactly one instance of Author exists. |
2.3.2 |
entity |
vCard <http://www.imc.org/pdi/> |
String (1000 chars) |
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.
2. If Role equals Publisher, then the entity is typically an organization and this element corresponds with the Dublin Core element DC.Publisher.
3. If Role is not equal to Author or Publisher, then this element corresponds with the Dublin Core element DC.Contributor.
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. |
2.3.3 |
date |
- |
DateType |
- |
3 |
metametadata |
- |
- |
- |
3.1 |
identifier |
- |
String |
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 |
- |
String (1000 char) |
Generally system generated. |
3.2.2 |
entry |
- |
LangStringType (1000 char) |
Generally system generated. |
3.3 |
contribute |
- |
- |
- |
3.3.1 |
role |
vocabulary: {Creator, Validator} |
Vocabulary |
It is recommended that exactly one instance of creator exists. |
3.3.2 |
entity |
vCard <http://www.imc.org/pdi/> |
String (1000 char) |
- |
3.3.3 |
date |
- |
DateType |
- |
3.4 |
metadatascheme |
- |
String (30 char) |
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 |
String (100 char) |
"none" is an acceptable value. |
4 |
technical |
- |
- |
- |
4.1 |
format |
restricted: MIME type or 'non-digital' |
String (500 char) |
1. Can be used to identify the software needed to access the resource.
2. This element corresponds with the Dublin Core element DC.Format. |
4.2 |
size |
- |
String (30 char) |
This refers to the actual size of the resource, and not to the size of a compressed version of the resource. |
4.3 |
location |
- |
String (1000 char) |
- |
4.4 |
requirement |
- |
- |
- |
4.4.1 |
type |
vocabulary: {Operating System, Browser} |
Vocabulary |
- |
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 |
Vocabulary |
May be derived from Format (4.1) automatically, e.g., HTML implies "Multi-OS" |
4.4.3 |
minimumversion |
- |
String (30 char) |
- |
4.4.4 |
maximumversion |
- |
String (30 char) |
- |
4.5 |
installationremarks |
- |
LangStringType (1000 char) |
- |
4.6 |
otherplatformrequirements |
- |
LangStringType (1000 char) |
- |
4.7 |
duration |
ISO8601 |
DateType |
This is especially useful for sounds, movies, or animations. |
5 |
educational |
- |
- |
- |
5.1 |
interactivitytype |
vocabulary: {Active, Expositive, Mixed, Undefined} |
Vocabulary |
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 |
learningresourcetype |
vocabulary: {Exercise, Simulation, Questionnaire, Diagram, Figure, Graph, Index, Slide, Table, Narrative Text, Exam, Experiment, ProblemStatement, SelfAssesment} |
Vocabulary |
This element corresponds with the Dublin Core element 'Resource Type'. The vocabulary is adapted for the specific purpose of learning objects. |
5.3 |
interactivitylevel |
vocabulary: {very low, low, medium, high, very high} |
Vocabulary |
- |
5.4 |
semanticdensity |
vocabulary: {very low, low, medium, high, very high} |
Vocabulary |
- |
5.5 |
intendedenduserrole |
vocabulary: {Teacher, Author, Learner, Manager} |
Vocabulary |
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. |
5.6 |
context |
vocabulary: {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} |
Vocabulary |
- |
5.7 |
typicalagerange |
- |
LangStringType (1000 chars) |
- |
5.8 |
difficulty |
vocabulary: {very easy, easy, medium, difficult, very difficult} |
Vocabulary |
- |
5.9 |
typicallearningtime |
ISO8601 |
DateType |
- |
5.10 |
description |
- |
LangStringType (1000 char) |
- |
5.11 |
language |
- |
String (100 char) |
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 |
vocabulary: {yes, no} |
Vocabulary |
- |
6.2 |
copyrightandotherrestrictions |
vocabulary: {yes, no} |
Vocabulary |
- |
6.3 |
description |
- |
LangStringType (1000 char) |
- |
7 |
relation |
- |
- |
- |
7.1 |
kind |
ocabulary list from Dublin Core: {IsPartOf, HasPart, IsVersionOf, HasVersion, IsFormatOf, HasFormat, References, IsReferencedBy, IsBasedOn, IsBasisFor, Requires, IsRequiredBy} |
Vocabulary |
This element corresponds with the Dublin Core element DC.Relation. |
7.2 |
resource |
- |
- |
- |
7.2.1 |
identifier |
- |
String |
- |
7.2.2 |
description |
- |
LangStringType (1000 char) |
- |
7.2.3 |
catalogentry |
- |
- |
See general.catalogentry. |
7.2.3.1 |
catalog |
- |
String (1000 char) |
Generally the name of the catalog. |
7.2.3.2 |
entry |
- |
LangStringType (1000 char) |
Generally the number in the catalog named in Catalog (7.2.3.1). |
8 |
annotation |
- |
- |
- |
8.1 |
person |
vCard <http://www.imc.org/pdi/> |
String (1000 char) |
- |
8.2 |
date |
- |
DateType |
- |
8.3 |
description |
- |
LangStringType (1000 char) |
- |
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. |
9.1 |
purpose |
vocabulary: {Discipline, Idea, Prerequisite, Educational Objective, Accessibility Restrictions, Educational Level, Skill Level, Security Level} |
Vocabulary |
- |
9.2 |
taxonpath |
- |
- |
There may be different paths, in the same or different classifications, that describe the same characteristic. |
9.2.1 |
source |
- |
LangStringType (1000 char) |
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.). |
9.2.2 |
taxon |
- |
- |
A TaxonPath can have a depth from 1 to 9. Normal values ae between 2 and 4. |
9.2.2.1 |
id |
- |
String (100 char) |
Repertoire of ISO/IEC 10646-1 |
9.2.2.2 |
entry |
- |
LangStringType (500 char) |
- |
9.3 |
description |
- |
LangStringType (2000 char) |
- |
9.4 |
keyword |
- |
LangStringType (1000 char) |
- |