1、IEEE Std 1484.20.1-2007IEEE Standard for LearningTechnologyData Model forReusable Competency DefinitionsIEEE3 Park AvenueNew York, NY 10016-5997, USA25 January 2008IEEE Computer SocietySponsored by theLearning Technology Standards Committee1484.20.1TMIEEE Std 1484.20.1TM-2007 IEEE Standard for Learn
2、ing TechnologyData Model for Reusable Competency Definitions Sponsor Learning Technology Standards Committee of the IEEE Computer Society Approved 27 September 2007 IEEE-SA Standards Board This Standard is based on the IMS Reusable Definition of Competency or Educational Objective Specification, Ver
3、sion 1.0, published on October 25, 2002, by the IMS Global Learning Consortium, Inc. Abstract: This Standard defines a data model for describing, referencing, and sharing competency definitions, primarily in the context of online and distributed learning. This Standard provides a way to represent fo
4、rmally the key characteristics of a competency, independently of its use in any particular context. It enables interoperability among learning systems that deal with competency information by providing a means for them to refer to common definitions with common meanings. Keywords: competency, compet
5、ency definition, reusable competency definition The Institute of Electrical and Electronics Engineers, Inc. 3 Park Avenue, New York, NY 10016-5997, USA Copyright 2008 by the Institute of Electrical and Electronics Engineers, Inc. All rights reserved. Published 25 January 2008. Printed in the United
6、States of America. IEEE is a registered trademark in the U.S. Patent +1 978 750 8400. Permission to photocopy portions of any individual standard for educational classroom use can also be obtained through the Copyright Clearance Center. iv Copyright 2008 IEEE. All rights reserved. Introduction This
7、introduction is not part of IEEE Std 1484.20.1-2007, IEEE Standard for Learning TechnologyData Model for Reusable Competency Definitions. This Standard defines a data model for describing, referencing, and sharing competency definitions, primarily in the context of online and distributed learning. T
8、his Standard provides a way to represent formally the key characteristics of a competency, independently of its use in any particular context. It enables interoperability among learning systems that deal with competency information by providing a means for them to refer to common definitions with co
9、mmon meanings. Dedication The LTSC Reusable Competency Definitions Working Group dedicates this standard to the memory of Claude Ostyn. As chair of the LTSC 1484.20 Working Group, he provided initiative, guidance, and technical insight that made this standard possible. His hard work is much apprecia
10、ted and will be remembered. Notice to users Errata Errata, if any, for this and all other standards can be accessed at the following URL: http:/ standards.ieee.org/reading/ieee/updates/errata/index.html. Users are encouraged to check this URL for errata periodically. Interpretations Current interpre
11、tations can be accessed at the following URL: http:/standards.ieee.org/reading/ieee/interp/ index.html. Patents Attention is called to the possibility that implementation of this standard may require use of subject matter covered by patent rights. By publication of this standard, no position is take
12、n with respect to the existence or validity of any patent rights in connection therewith. The IEEE is not responsible for identifying Essential Patent Claims for which a license may be required, for conducting inquiries into the legal validity or scope of Patents Claims or determining whether any li
13、censing terms or conditions are reasonable or non-discriminatory. Further information may be obtained from the IEEE Standards Association. v Copyright 2008 IEEE. All rights reserved. Participants At the time this standard submitted to the IEEE-SA Standards Board for approval, the Competency Data Sta
14、ndards Working Group had the following membership: Claude Ostyn, Chair* Scott Lewis, Technical Editor Michael Brown Mike Collett Geoffrey Darnton Geoffrey A. Frank Jason L. Haag Chad J. Kainz Fanny Klett Rolf Lindner Daniel R. Rehak Robby Robson Christian Stracke Schawn E. Thropp Luk Vervenne *Decea
15、sed The following members of the balloting committee voted on this standard. Balloters may have voted for approval, disapproval, or abstention. William J. Ackerman Juan C. Carreon Keith Chow Paul Colcher Tommy P. Cooper Geoffrey Darnton Thomas J. Dineen Kameshwar V. Eranki Allan M. Gillard John Gart
16、h Glynn Randall C. Groves Jason L. Haag Rutger A. Heunks Werner Hoelzl Dennis Horwitz Atushi Ito Chad J. Kainz Piotr Karocki Robert B. Kelsey Fanny Klett Mark J. Knight Susan Land Rolf Lindner Gregory Luri Jonathan C. Mason Gary Michel Georges F. Montillet Michael S. Newman Claude Ostyn Daniel R. Re
17、hak Robert A. Robinson Robby Robson Randall M. Safier Bartien Sayogo Colin Smythe Thomas E. Starai Christian Stracke Schawn E. Thropp Mark A. Tillinghast Derek T. Woo When the IEEE-SA Standards Board approved this guide on 27 September 2007, it had the following membership: Steve M. Mills, Chair Rob
18、ert M. Grow, Vice Chair Don Wright, Past Chair Judith Gorman, Secretary Richard DeBlasio Alex Gelman William R. Goldbach Arnold M. Greenspan Joanna N. Guenin Kenneth S. Hanus William B. Hopf Richard H. Hulett Hermann Koch Joseph L. Koepfinger* John Kulick David J. Law Glenn Parsons Ronald C. Peterse
19、n Tom A. Prevost Narayanan Ramachandran Greg Ratta Robby Robson Anne-Marie Sahazizian Virginia C. Sulzberger Malcolm V. Thaden Richard L. Townsend Howard L. Wolfman *Member Emeritus vi Copyright 2008 IEEE. All rights reserved. Also included are the following nonvoting IEEE-SA Standards Board liaison
20、s: Satish K. Aggarwal, NRC Representative Michael H. Kelley, NIST Representative Don Messina IEEE Standards Program Manager, Document Development Michael D. Kipness IEEE Standards Program Manager, Technical Program DevelopmentContents 1. Overview 1 1.1 Scope . 1 1.2 Purpose 1 2. Normative references
21、 2 3. Definitions, acronyms, and abbreviations 2 3.1 Definitions . 2 3.2 Acronyms and abbreviations . 3 4. Special terms 3 5. Conformance 3 5.1 Shall and shall not 3 5.2 RCD instances . 3 5.3 Smallest permitted maximum values. 3 6. Data model . 4 6.1 General information. 4 6.2 Reusable competency de
22、finition 5 6.3 Auxiliary data types. 14 Annex A (informative) Bibliography . 18 Annex B (informative) Conceptual overview. 19 Annex C (informative) An example XML binding schema . 22 vii Copyright 2008 IEEE. All rights reserved. IEEE Standard for Learning TechnologyData Model for Reusable Competency
23、 Definitions 1. 1.11.2Overview Scope This Standard defines a data model for describing, referencing, and sharing competency definitions, primarily in the context of online and distributed learning. This Standard provides a way to represent formally the key characteristics of a competency, independen
24、tly of its use in any particular context. It enables interoperability among learning systems that deal with competency information by providing a means for them to refer to common definitions with common meanings. This Standard enables information about competencies to be encoded and shared. This St
25、andard does not define whether a competency is a skill, knowledge, ability, attitude, or learning outcome, but it can be used to capture information about any of these. Policies regarding reusable competency definitions (RCDs), such as the best practice to look for an existing definition to reuse in
26、stead of inventing a new one for the same purpose, are outside of the scope of this Standard. Purpose This Standard is based on the existing IMS Global Learning Consortium (IMS) specification entitled IMS Reusable Definition of Competency or Educational Objective (RDCEO) B4.1Implementations that con
27、form to the IMS specification will conform to this Standard. 1The numbers in brackets correspond to those of the bibliography in Annex A. 1 Copyright 2008 IEEE. All rights reserved. IEEE Std 1484.20.1-2007 IEEE Standard for Learning TechnologyData Model for Reusable Comptency Definitions 2. 3. 3.1No
28、rmative references The following referenced documents are indispensable for the application of this document (i.e., they must be understood and used, so each referenced document is cited in text and its relationship to this document is explained). For dated references, only the edition cited applies
29、. For undated references, the latest edition of the referenced document (including any amendments or corrigenda) applies. IEEE Std 1484.12.1TM-2002, IEEE Standard for Learning Object Metadata.1,2IETF RFC 3986:2005, Uniform Resource Identifiers (URI): Generic Syntax.3ISO 6391, Code for the representa
30、tion of names of languagesPart 1: Alpha-2 code.4ISO 6392, Codes for the representation of names of languagesPart 2: Alpha-3 code. ISO 31661, Codes for the representation of names of countries and their subdivisionsPart 1: Country codes. ISO/IEC 10646, Information technologyUniversal Multiple-Octet C
31、oded Character Set (UCS).5ISO/IEC 11404:1996, Information technologyProgramming languages, their environments and system software interfacesLanguage-independent datatypes.6W3C Recommendation (28 October 2004), XML Schema Part 2: Datatypes Second Edition.7Definitions, acronyms, and abbreviations Defi
32、nitions For purposes of this document, the following terms and definitions apply. The Authoritative Dictionary of IEEE Standards Terms B1 should be referenced for terms not defined in this Clause. 3.1 competency definition record: An instance of a data structure that represents an identifiable compe
33、tency definition. 1IEEE publications are available from the Institute of Electrical and Electronics Engineers, Inc., 445 Hoes Lane, Piscataway, NJ 08854, USA (http:/standards.ieee.org/). 2The IEEE standards or products referred to in this introduction are trademarks of the Institute of Electrical an
34、d Electronics Engineers, Inc. 3IETF publications are available from the Internet Engineering Task Force website at http:/ietf.org/rfc.html. 4ISO publications are available from the ISO Central Secretariat, Case Postale 56, 1 rue de Varemb, CH1211, Genve 20, Switzerland/Suisse (http:/www.iso.ch/). IS
35、O publications are also available in the United States from the Sales Department, American National Standards Institute, 25 West 43rd Street, 4th Floor, New York, NY 10036, USA (http:/www.ansi.org/). 5ISO/IEC publications are available from the ISO Central Secretariat, Case Postale 56, 1 rue de Vare
36、mb, CH1211, Genve 20, Switzerland/Suisse (http:/www.iso.ch/). ISO/IEC publications are also available in the United States from Global Engineering Documents, 15 Inverness Way East, Englewood, CO 80112, USA (http:/ Electronic copies are available in the United States from American National Standards
37、Institute, 25 West 43rd Street, 4th Floor, New York, NY 10036, USA (http:/www.ansi.org/). 6ISO/IEC 11404:1996 may be downloaded at no cost from http:/www.iso.org/. 7W3C publications are available from the World Wide Web Consortium, 32 Vassar Street, Room 32G515, Cambridge, MA 02139, USA (http:/www.w
38、3.org/). 2 Copyright 2008 IEEE. All rights reserved. IEEE Std 1484.20.1-2007 IEEE Standard for Learning TechnologyData Model for Reusable Comptency Definitions 3.2 LangString: A data type that represents one or more character strings. A LangString value may include multiple, semantically equivalent,
39、 character strings, such as translations or expressions of a description in different languages. 3.24.5. 5.15.25.3Acronyms and abbreviations IMS IMS Global Learning Consortium RCD reusable competency definition RDCEO Reusable Definition of Competency or Educational Objective SPM smallest permitted m
40、aximum URI Uniform Resource Identifier XML Extensible Markup Language Special terms In this Standard, the following special terms and definitions apply. competency: Any aspect of competence, such as knowledge, skill, attitude, ability, or learning objective. NOTEIn this Standard, the term “competenc
41、y” is to be interpreted in the broadest sense to include learning objectives (those things that are sought) as well as competencies (those things that are achieved). The term “competency” is also used to include all classes of things that someone, or potentially something, can be competent in, altho
42、ugh some communities of practice use the term with nuance, for example, limiting its use to skill and excluding knowledge or understanding.8Conformance Shall and shall not In this Standard, “shall” is to be interpreted as a requirement on an implementation; “shall not” is to be interpreted as a proh
43、ibition. RCD instances A conforming RCD instance shall conform to the data model as specified in Clause 5. Smallest permitted maximum values This standard defines smallest permitted maximum (SPM) values for many data elements. The SPM is the number of entries that a conforming implementation is requ
44、ired to process for a given data element in an RCD instance. An RCD instance may contain more entries for a data element than the SPM. An implementation that receives entries in excess of the SPM shall not produce an error. The implementation may, but is not required to, process those entries. For t
45、he purposes of the SPM, an entry may be an element within a collection, such as a bag or record, or it may be a character in a string. SPM values are defined for 8Notes in text, tables, and figures are given for information only and do not contain requirements needed to implement the guide. 3 Copyri
46、ght 2008 IEEE. All rights reserved. IEEE Std 1484.20.1-2007 IEEE Standard for Learning TechnologyData Model for Reusable Comptency Definitions Items in a collection: For example, an SPM is defined for Statement elements within a Definition. If the SPM for the number of Statement elements is n but th
47、e number of statements in an RCD instance is n + 1, an implementation that receives the Statement elements shall not produce an error. The implementation shall process at least n elements but may ignore the element that exceeds the SPM. Character strings defined in the types CharacterString and Lang
48、String: For example, if a string found in an element of one of these types in an RCD instance contains more characters than specified by the SPM, an implementation that receives the string shall not produce an error but may ignore the extra characters. NOTE 1NOTE 2NOTE 3NOTE 4NOTE 56.6.1NOTE 1NOTE 2
49、NOTE 3NOTE 4NOTE 5The intent is for the SPM values to cover most cases. The meaning of “process” in this subclause depends on the nature of the application. This Standard does not define any provision for whether or how a system may process more than the SPM value for a particular data element. This Standard does not define failure conditions if a system cannot process the SPM value for a particular data element. If the SPM for the number of elements in a collection is n, but the number of elements is n + 1,
