Browse Prior Art Database

Automatic Derivation of "Technical Category" Metadata for Learning Objects Disclosure Number: IPCOM000021068D
Original Publication Date: 2003-Dec-19
Included in the Prior Art Database: 2003-Dec-19
Document File: 2 page(s) / 8K

Publishing Venue



This invention describes a technical information generation system, method, and apparatus. The method of the invention can include steps to automatically derive Technical requirements in a selected portion of content, where the technical details for using the content are specific to a particular domain. Consequently, technical requirements metadata can be bound to content objects according to learning standards, such as Advanced Distributed Learning (ADL) Sharable Content Object Reference Model (SCORM) and Institute for Electronic and Electric Engineers (IEEE) Learning Object Metadata (LOM), without manual intervention. This invention defines a preferred embodiment for automatically identifying the values for the format, size, location, type of location, type and name of the technical requirement, minimum and maximum versions of the technical requirement, installation remarks, and other platform requirements.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 1 of 2

Automatic Derivation of "Technical Category" Metadata for Learning Objects

This invention describes an embodiment that automatically derives and sets all of the following metadata entities for a learning object: 4.1 Technical.Format, 4.2 Technical.Size,
4.3 Technical.Location, 4.3.1 Technical.Location.Type, 4.4 Technical.Requirement, 4.4.1 Technical.Requirement.Type, 4.4.2 Technical.Requirement.Name, 4.4.3 Technical.Requirement.Minimum Version, 4.4.4 Technical.Requirement.Maximum Version,
4.5 Installation Remarks and 4.6 Other Platform Requirements. Note that the numbers cited refer to the SCORM 1.2 metadata identifier numbers.

The 4.1 Technical.Format category identifies the data type of the object being parsed. This string is restricted to be either a MIME type or 'non-digital'. The MIME type is derived by checking the extension of an embedded multimedia types or of the text file being parsed. Using a configuration file, such as the config/mimemap.txt file shown in Example 1, this invention derives the technical.format field based on the extension of the content object file name.

Example 1. config/mimemap.txt file

.htm text/html
.html text/html
.jpg image/jpeg
.gif image/gif
.avi video/x-msvideo
.swf application/x-shockwave-flash

For example, if a file is named mypicture.gif, the invention searches the configuration file for the ".gif" extension. The ".gif" key is found in the first field of the fourth line of the configuration file. The invention identifies "text/html" as the MIME type for the 4.1 Technical.Format metadata entity.

This invention derives 4.2 Technical.Size metadata entity by checking the size of the multi-media object or text object.

This invention derives 4.3 Technical.Location and 4.3.1 Technical.Location.Type by identifying the URI for the location of the object in a flat files repository.

This invention derives technical requirements ( Type, Name, Minimum Version, Maximum Version, and Installation Version) by using configuration files. Example 2 is a representation of a possible config/TechRequirements.txt file that maps...