1、IEEE Std 1484.12.1-2002IEEE Standards1484.12.1TMIEEE Standard for Learning ObjectMetadataPublished by The Institute of Electrical and Electronics Engineers, Inc.3 Park Avenue, New York, NY 10016-5997, USA6 September 2002IEEE Computer SocietySponsored by theLearning Technology Standards CommitteeIEEE
2、 StandardsPrint: SH95001PDF: SS95001The Institute of Electrical and Electronics Engineers, Inc.3 Park Avenue, New York, NY 10016-5997, USACopyright 2002 by the Institute of Electrical and Electronics Engineers, Inc.All rights reserved. Published 6 September 2002. Printed in the United States of Amer
3、ica.Print: ISBN 0-7381-3297-7 SH95001PDF: ISBN 0-7381-3298-5 SS95001No part of this publication may be reproduced in any form, in an electronic retrieval system or otherwise, without the prior written permission of the publisher.IEEE Std 1484.12.1-2002(R2009)IEEE Standard for Learning Object Metadat
4、aSponsorLearning Technology Standards Committeeof theIEEE Computer SocietyReafffirmed 13 May 2009Approved 13 June 2002IEEE-SA Standards BoardApproved 14 November 2002American National Standards InstituteAbstract: A conceptual data schema that defines the structure of metadata for a learning object i
5、sspecified in this standard.Keywords: learning object, learning object metadata (LOM), metadata, reuseIEEE Standardsdocuments are developed within the IEEE Societies and the Standards Coordinating Committees of theIEEE Standards Association (IEEE-SA) Standards Board. The IEEE develops its standards
6、through a consensus develop-ment process, approved by the American National Standards Institute, which brings together volunteers representing variedviewpoints and interests to achieve the nal product. Volunteers are not necessarily members of the Institute and serve with-out compensation. While the
7、 IEEE administers the process and establishes rules to promote fairness in the consensus devel-opment process, the IEEE does not independently evaluate, test, or verify the accuracy of any of the information containedin its standards.Use of an IEEE Standard is wholly voluntary. The IEEE disclaims li
8、ability for any personal injury, property or other dam-age, of any nature whatsoever, whether special, indirect, consequential, or compensatory, directly or indirectly resultingfrom the publication, use of, or reliance upon this, or any other IEEE Standard document.The IEEE does not warrant or repre
9、sent the accuracy or content of the material contained herein, and expressly disclaimsany express or implied warranty, including any implied warranty of merchantability or tness for a specic purpose, or thatthe use of the material contained herein is free from patent infringement. IEEE Standards doc
10、uments are supplied “AS IS.”The existence of an IEEE Standard does not imply that there are no other ways to produce, test, measure, purchase, market,or provide other goods and services related to the scope of the IEEE Standard. Furthermore, the viewpoint expressed at thetime a standard is approved
11、and issued is subject to change brought about through developments in the state of the art andcomments received from users of the standard. Every IEEE Standard is subjected to review at least every ve years for revi-sion or reafrmation. When a document is more than ve years old and has not been reaf
12、rmed, it is reasonable to concludethat its contents, although still of some value, do not wholly reect the present state of the art. Users are cautioned to checkto determine that they have the latest edition of any IEEE Standard.In publishing and making this document available, the IEEE is not sugge
13、sting or rendering professional or other servicesfor, or on behalf of, any person or entity. Nor is the IEEE undertaking to perform any duty owed by any other person orentity to another. Any person utilizing this, and any other IEEE Standards document, should rely upon the advice of a com-petent pro
14、fessional in determining the exercise of reasonable care in any given circumstances.Interpretations: Occasionally questions may arise regarding the meaning of portions of standards as they relate to specicapplications. When the need for interpretations is brought to the attention of IEEE, the Instit
15、ute will initiate action to prepareappropriate responses. Since IEEE Standards represent a consensus of concerned interests, it is important to ensure that anyinterpretation has also received the concurrence of a balance of interests. For this reason, IEEE and the members of its soci-eties and Stand
16、ards Coordinating Committees are not able to provide an instant response to interpretation requests except inthose cases where the matter has previously received formal consideration. Comments for revision of IEEE Standards are welcome from any interested party, regardless of membership afliation wi
17、thIEEE. Suggestions for changes in documents should be in the form of a proposed change of text, together with appropriatesupporting comments. Comments on standards and requests for interpretations should be addressed to:Secretary, IEEE-SA Standards Board445 Hoes LaneP.O. Box 1331Piscataway, NJ 0885
18、5-1331USAThe IEEE and its designees are the sole entities that may authorize the use of the IEEE-owned certication marks and/ortrademarks to indicate compliance with the materials set forth herein.Authorization to photocopy portions of any individual standard for internal or personal use is granted
19、by the Institute ofElectrical and Electronics Engineers, Inc., provided that the appropriate fee is paid to Copyright Clearance Center. Toarrange for payment of licensing fee, please contact Copyright Clearance Center, Customer Service, 222 Rosewood Drive,Danvers, MA 01923 USA; +1 978 750 8400. Perm
20、ission to photocopy portions of any individual standard for educationalclassroom use can also be obtained through the Copyright Clearance Center.Note: Attention is called to the possibility that implementation of this standard may require use of subject mat-ter covered by patent rights. By publicati
21、on of this standard, no position is taken with respect to the existence orvalidity of any patent rights in connection therewith. The IEEE shall not be responsible for identifying patentsfor which a license may be required by an IEEE standard or for conducting inquiries into the legal validity orscop
22、e of those patents that are brought to its attention.Copyright 2002 IEEE. All rights reserved.iiiIntroduction(This introduction is not part of IEEE Std 1484.12.1-2002, IEEE Standard for Learning Object Metadata.)Metadata is information about an object, be it physical or digital. As the number of obj
23、ects grows exponen-tially and our needs for learning expand equally dramatically, the lack of information or metadata aboutobjects places a critical and fundamental constraint on our ability to discover, manage, and use objects.This standard addresses this problem by dening a structure for interoper
24、able descriptions of learningobjects.AcknowledgementsThe IEEE Learning Technology Standards Committee (LTSC) P1484.12 Learning Object Metadata (LOM)working group wishes to thank Erik Duval, Tom Wason, and Wayne Hodgins for their tireless efforts andcommitment to developing a high quality solution an
25、d document. This document has its origins in both theARIADNE1and IMS2Projects, without which this document could not have been created. This documentalso builds on metadata work done by the Dublin Core3group.ParticipantsAt the time this standard was completed, the working group had the following mem
26、bership:Wayne Hodgins,Chair1http:/www.ariadne-eu.org/2http:/www.imsproject.org/3http:/dublincore.org/Carlos C. AmanoThor AndersonPatricia BarkmanBill BlackmonKerry BlincoDebbie BrownPeter BrusilovskyJ. Richard BurkeMike CollettBen CopelandPhilip DoddsErik DuvalFrank FaranceMike ForeEddy FortePaul Fo
27、sterVladimir GoodkovskyMartha GrayJack HydeChad KainzIan KegelRoger LangeJohn ManionJon MasonEd MatlackRalf MatlackCindy MazowWilliam A. McDonaldBill MeltonBrandon MuramatsuYves NicolBoyd NielsenClaude OstynBruce PeoplesMike PettitTom Probert Roy RadaDan RehakTyde RichardsKevin RileyRobby RobsonRand
28、y SaundersJim SchoeningKathy SinitsaGayle StroupDaniel SuthersJoshua TonkelBrendon TowleJohn TylerTom WasonEamonn WebsterSteve WhiteIan WrightivCopyright 2002 IEEE. All rights reserved.The following persons were on the balloting committee: When the IEEE-SA Standards Board approved this standard on 1
29、3 June 2002, it had the followingmembership:James T. Carlo,ChairJames H. Gurney,Vice ChairJudith Gorman,Secretary*Member EmeritusAlso included are the following nonvoting IEEE-SA Standards Board liaisons:Alan Cookson, NIST RepresentativeSatish K. Aggarwal, NRC RepresentativeAndrew IckowiczIEEE Stand
30、ards Project EditorJohn BennettDebbie BrownMike CollettGuru Dutt DhingraErik DuvalFrank FaranceMike ForeEddy ForteWayne HodginsJon MasonBill MeltonDavid MetcalfBrandon MuramatsuTom MurrayBoyd NielsenClaude OstynBruce PeoplesDan RehakTyde RichardsRobby RobsonDavid RockwellJaideep RoyRandy SaundersJim
31、 SchoeningCharles SeveranceDaniel SuthersKaterynaSynytsyaSteve TealJoshua TonkelJohn TylerEdward WalkerTom WorthingtonSid BennettH. Stephen BergerClyde R. CampRichard DeBlasioHarold E. EpsteinJulian Forster*Howard M. FrazierToshio FukudaArnold M. GreenspanRaymond HapemanDonald M. HeirmanRichard H. H
32、ulettLowell G. JohnsonJoseph L. Koepnger*Peter H. LipsNader MehravariDaleep C. MohlaWilliam J. MoylanMalcolm V. ThadenGeoffrey O. ThompsonHoward L. WolfmanDon WrightCopyright 2002 IEEE. All rights reserved.vContents1. Overview 11.1 Scope 11.2 Purpose. 12. References 23. Definitions 34. Overview of t
33、he metadata structure . 34.1 Basic metadata structure 34.2 Data elements. 44.3 List values 44.4 Vocabularies 54.5 Smallest permitted maximum values. 64.6 Character sets. 64.7 Representation 65. Conformance 66. Base Schema 77. LangString 238. DateTime 259. Duration . 2710. Vocabulary. 29Annex A (info
34、rmative) Bibliography. 31Annex B (informative) Mapping to unqualified Dublin Core . 32Copyright 2002 IEEE. All rights reserved.1IEEE Standard for Learning Object Metadata1. Overview1.1 ScopeThis is a multi-part standard that species learning object metadata. This part species a conceptual dataschema
35、 that denes the structure of a metadata instance for a learning object. For this standard, a learningobject is dened as any entitydigital or non-digitalthat may be used for learning, education, or training.For this standard, a metadata instance for a learning object describes relevant characteristic
36、s of the learningobject to which it applies. Such characteristics may be grouped in general, life cycle, meta-metadata, educa-tional, technical, educational, rights, relation, annotation, and classication categories.The conceptual data schema specied in this part permits linguistic diversity of both
37、 learning objects and themetadata instances that describe them. This conceptual data schema species the data elements which compose a metadata instance for a learningobject. This part is intended to be referenced by other standards that dene the implementation descriptions of thedata schema so that
38、a metadata instance for a learning object can be used by a learning technology system tomanage, locate, evaluate, or exchange learning objects. This part of this standard does not dene how a learning technology system represents or uses a metadatainstance for a learning object.1.2 PurposeThe purpose
39、 of this multi-part standard is to facilitate search, evaluation, acquisition, and use of learningobjects, for instance by learners or instructors or automated software processes. This multi-part standard alsofacilitates the sharing and exchange of learning objects, by enabling the development of ca
40、talogs and inven-tories while taking into account the diversity of cultural and lingual contexts in which the learning objectsand their metadata are reused. IEEEStd 1484.12.1-2002 IEEE STANDARD FOR 2Copyright 2002 IEEE. All rights reserved.By specifying a common conceptual data schema, this part of
41、this standard ensures that bindings of learningobject metadata (LOM) have a high degree of semantic interoperability. As a result, transformations betweenbindings will be straightforward.This part of this standard species a base schema, which may be extended as practice develops, e.g., facili-tating
42、 automatic, adaptive scheduling of learning objects by software agents.2. ReferencesThe following referenced documents are indispensable for the application of this document. For dated refer-ences, only the edition cited applies.IETF RFC 2048:1996, Multipurpose Internet Mail Extensions (MIME) Part F
43、our: Registration Procedures.1, 2IETF RFC 2425: 1998, MIME Content-Type for Directory Information.2, 3IETF RFC 2426: 1998, vCard MIME Directory Prole.2, 3ISO 639-1:2002, Codes for the Representation of Names of LanguagesPart 1: Alpha-2 Code.4, 5ISO 639-2:1998, Codes for the Representation of Names o
44、f LanguagesPart 2: Alpha-3 Code.5ISO 3166-1:1997, Codes for the Representation of Names of Countries and their SubdivisionsPart 1: Coun-try Codes.6ISO 8601:2000, Data Elements and Interchange FormatsInformation InterchangeRepresentation of Datesand Times.7ISO/IEC 646:1991, Information TechnologyISO
45、7-Bit Coded Character Set for Information Interchange.8,9ISO/IEC 10646-1:2000, Information TechnologyUniversal Multiple-Octet Coded Character Set (UCS)Part 1: Architecture and Basic Multilingual Plane.10OED:1989, Oxford English Dictionary, 2nd Ed. 1989.111IETF RFC documents are available at http:/ww
46、w.ietf.org/rfc.2Multipurpose Internet Mail Extensions (MIME) extends the format of Internet mail to allow non-US-ASCII textual messages, non-tex-tual messages, multipart message bodies, and non-US-ASCII information in message headers.3This standard denes how contact details for people and organizati
47、ons can be represented. The vCard MIME Directory Prole isdened in IETF RFC 2425:1998 and IETF RFC 2426:1998.4ISO publications are available from the ISO Central Secretariat, Case Postale 56, 1 rue de Varemb, CH-1211, Genve 20, Switzer-land/Suisse (http:/www.iso.ch/). ISO publications are also availa
48、ble in the United States from the Sales Department, AmericanNational Standards Institute, 25 West 43rd Street, 4th Floor, New York, NY 10036, USA (http:/www.ansi.org/).5This is an international standard for the representation of languages. ISO 639-1:2002 denes two-letter language codes, e.g., “en” f
49、orEnglish, “fr” for French, “nl” for Dutch, etc. These language codes are a basis for the IETF registry of language tags, as specied inRFC 1766:1995 B6. Tags for the identication of languages. ISO 639-2:1998 denes three-letter language codes, e.g. “grc” forAncient Greek, “eng” for English.6This is an international standard for the representation of country codes, e.g., “BE” for Belgium, “CA” for Canada, “FR” for France,“GB” for United Kingdom, “US” for United States, etc. 7This is an international standard that species numeric r
