1、g44g40g40g40g3g54g87g71g3g20g23g27g23g17g20g20g17g20g140g16g21g19g19g23g11g40g85g85g68g87g68g3g76g81g70g82g85g83g82g85g68g87g72g71g21g23g3g45g88g81g72g3g21g19g20g19g12g44g40g40g40g3g54g87g68g81g71g68g85g71g3g73g82g85g47g72g68g85g81g76g81g74g3g55g72g70g75g81g82g79g82g74g92g179g39g68g87g68g3g48g82g71g
2、72g79g3g73g82g85g3g38g82g81g87g72g81g87g3g50g69g77g72g70g87g3g38g82g80g80g88g81g76g70g68g87g76g82g81g44g40g40g40g3g38g82g80g83g88g87g72g85g3g54g82g70g76g72g87g92g54g83g82g81g86g82g85g72g71g3g69g92g3g87g75g72g47g72g68g85g81g76g81g74g3g55g72g70g75g81g82g79g82g74g92g3g54g87g68g81g71g68g85g71g86g3g38g82
3、g80g80g76g87g87g72g72g44g40g40g40g22g3g51g68g85g78g3g36g89g72g81g88g72g3g49g72g90g3g60g82g85g78g15g3g49g60g3g20g19g19g20g25g16g24g28g28g26g15g3g56g54g36g3g3g21g23g3g45g88g81g72g3g21g19g20g19g20g23g27g23g17g20g20g17g20g55g48Recognized as anAmerican National Standard (ANSI)The Institute of Electrical
4、and Electronics Engineers, Inc.3 Park Avenue, New York, NY 10016-5997, USACopyright 2005 by the Institute of Electrical and Electronics Engineers, Inc.All rights reserved. Originally Published 14 January 2005. Printed in the United States of America.IEEE is a registered trademark in the U.S. Patent
5、+1 978 750 8400. Permission to photocopy portions of any individual standard for educationalclassroom use can also be obtained through the Copyright Clearance Center.NOTEAttention is called to the possibility that implementation of this standard may require use of subjectmatter covered by patent rig
6、hts. By publication of this standard, no position is taken with respect to theexistence or validity of any patent rights in connection therewith. The IEEE shall not be responsible foridentifying patents for which a license may be required by an IEEE standard or for conducting inquiries into thelegal
7、 validity or scope of those patents that are brought to its attention.Copyright 2010 IEEE. All rights reserved. iiiIntroduction(This introduction is not part of IEEE Std 1484.11.1-2004, IEEE Standard for Learning TechnologyData Model forContent Object Communication.)This Standard describes a data mo
8、del to support the interchange of agreed upon data elements and theirvalues between a learning-related content object and a runtime service (RTS) used to support learningmanagement.Notice to usersErrataErrata, if any, for this and all other standards can be accessed at the following URL: http:/stand
9、ards.ieee.org/reading/ieee/updates/errata/index.html. Users are encouraged to check this URL forerrata periodically.InterpretationsCurrent interpretations can be accessed at the following URL: http:/standards.ieee.org/reading/ieee/interp/index.html.PatentsAttention is called to the possibility that
10、implementation of this standard may require use of subject mattercovered by patent rights. By publication 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 identifyingpatents or patent a
11、pplications for which a license may be required to implement an IEEE standard or forconducting inquiries into the legal validity or scope of those patents that are brought to its attention.ParticipantsThe following is a list of participants in the Computer Managed Instruction Working Group. Tyde Ric
12、hards, ChairJack Hyde, Chair (December 1998March 2001)Scott Lewis, Technical EditorMitchell BonnettFrank FaranceMike ForeLeonard GreenbergTom KingRolf LindnerKiyoshi NakabayashiBoyd NielsonClaude OstynDaniel RehakRobby RobsonSchawn Throppiv Copyright 2010 IEEE. All rights reserved.The following memb
13、ers of the individual balloting committee voted on this standard. Balloters may havevoted for approval, disapproval, or abstention.When the IEEE-SA Standards Board approved this standard on 23 September 2004, it had the followingmembership:Don Wright, ChairSteve M. Mills, Vice ChairJudith Gorman, Se
14、cretary*Member EmeritusAlso included are the following nonvoting IEEE-SA Standards Board liaisons:Satish K. Aggarwal, NRC RepresentativeRichard DeBlasio, DOE RepresentativeAlan Cookson, NIST RepresentativeMichelle TurnerIEEE Standards Project EditorMitchell BonnettDebbie BrownKeith ChowGeoffrey Darn
15、tonKameshwar ErankiFrank FaranceMike ForeLeonard GreenbergJackie HydeRobert Bruce KelseyTom KingRolf LindnerCarol Ann LongGregory LuriWilliam MeltonGeorge MiaoKiyoshi NakabayashiBoyd NielsenClaude OstynDaniel RehakTyde RichardsRobby RobsonThomas StaraiBrian TaliesinSchawn ThroppEamonn WebsterPhilome
16、na ZimmermanChuck AdamsH. Stephen BergerMark D. BowmanJoseph A. BruderBob DavisRoberto de BoissonJulian Forster*Arnold M. GreenspanMark S. HalpinRaymond HapemanRichard J. HollemanRichard H. HulettLowell G. JohnsonJoseph L. Koepfinger*Hermann KochThomas J. McGeanDaleep C. MohlaPaul NikolichT. W. Olse
17、nRonald C. PetersenGary S. RobinsonFrank StoneMalcolm V. ThadenDoug ToppingJoe D. WatsonCopyright 2010 IEEE. All rights reserved. vContents1. Overview 11.1 Scope 11.2 Purpose. 12. Normative references . 23. Definitions, abbreviations, and acronyms 23.1 Definitions . 23.2 Abbreviations and acronyms .
18、 34. Conformance 34.1 Data instances 34.2 Sending implementations. 44.3 Receiving implementations 44.4 Repository implementations 44.5 Implementation-defined values 44.6 Smallest permitted maximum values. 45. Conceptual model (informative) 46. Data model . 56.1 Content object communication 66.2 Auxi
19、liary data types . 33Annex A (informative) Bibliography 40Annex B (informative) Understanding the ISO/IEC 11404:1996 real and time interval data type definitions used in this Standard 41Annex C (informative) ISO 8601:2000 representation of the date time type 43Copyright 2010 IEEE. All rights reserve
20、d. 1IEEE Standard for Learning TechnologyData Model for Content Object Communication1. OverviewThe scope and purpose of this Standard are discussed in 1.1 and 1.2.1.1 ScopeThis Standard describes a data model to support the interchange of agreed upon data elements and theirvalues between a learning-
21、related content object and a runtime service (RTS) used to support learningmanagement. This Standard does not specify the means of communication between a content object and anRTS nor how any component of a learning environment shall behave in response to receiving data in theform specified. This St
22、andard is based on a related data model defined in “Computer Managed Instruction(CMI) Guidelines For Interoperability,” version 3.5 B1, by the Aviation Industry CBT Committee(AICC).1To balance the need to support existing implementations with the need to make technicalcorrections and support emergin
23、g practice, this Standard selectively includes those data elements from theCMI specification that are commonly implemented, renames some data elements taken from the CMIspecification to clarify their intended meaning, modifies the data types of data elements taken from the CMIspecification to reflec
24、t ISO standard data types and internationalization requirements, removes someorganizational structures used in the CMI specification to group data elements that are specific to the AICCcommunity of practice and not generally applicable, and introduces some data elements not present in theCMI specifi
25、cation to correct known technical deficiencies in data elements taken from that specification.1.2 PurposeThere is widespread acknowledgement that the data model for content object communication defined in theAICC “Computer Managed Instruction (CMI) Guidelines for Interoperability,” version 3.5 B1, h
26、as broadapplicability to systems used for learning management. The purpose of this Standard is to build consensusaround, resolve ambiguities in, and correct defects in the AICC data model for the data exchanged betweenlearning-related content objects and an RTS used to support learning management.1T
27、he numbers in brackets correspond to those of the bibliography in Annex A.IEEEStd 1484.11.1-2004 IEEE STANDARD FOR LEARNING TECHNOLOGY2 Copyright 2010 IEEE. All rights reserved.2. Normative referencesThe following referenced documents are indispensable for the application of this Standard. For dated
28、references, only the edition cited applies. For undated references, the latest edition of the referenceddocument (including any amendments) applies.IETF RFC 2396, Uniform Resource Identifiers (URI): Generic Syntax.2ISO 639-1, Code for the representation of names of languagesPart 1: Alpha-2 code.3ISO
29、 639-2, Codes for the representation of names of languagesPart 2: Alpha-3 code.ISO 3166-1, Codes for the representation of names of countries and their subdivisionsPart 1: Countrycodes.ISO 8601:2000, Data elements and interchange formatsInformation interchangeRepresentation of datesand times.ISO/IEC
30、 646:1991, Information technologyISO 7-bit coded character set for information interchange.4ISO/IEC 10646-1, Information technologyUniversal Multiple-Octet Coded Character Set (UCS)Part 1:Architecture and Basic Multilingual Plane.ISO/IEC 11404:1996, Information technologyProgramming languages, their
31、 environments and systemsoftware interfacesLanguage-independent datatypes.3. Definitions, acronyms, and abbreviations3.1 DefinitionsFor purposes of this Standard, the following terms and definitions apply. The Authoritative Dictionary ofIEEE Standards Terms B2 should be referenced for terms not defi
32、ned in this Clause.3.1.1 content object: A collection of digital content that is intended for presentation to a learner by alearning technology system. It may include learning material and processing code. Example: A contentobject might be an HTML page with an embedded video clip and an ECMAScript c
33、omponent written inaccordance with IEEE Std 1484.11.2TM-2003.NOTEFor more information on IEEE Std 1484.11.2-2003, see B3.53.1.2 implementation defined (adj.): An indication that the implementation provider shall define anddocument the requirements for correct program constructs and correct data of a
34、 value or behavior. When thevalue or behavior in the implementation is designed to be variable or customizable on each instantiation ofthe system, the implementation provider shall document the nature and permissible ranges of this variation. 2IETF publications are available on the World Wide Web fr
35、om the following website: http:/www.ietf.org.3ISO 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 available in the United States from the Sales Department, American Na
36、tional Standards Institute, 25 West 43rd Street, 4th Floor, New York, NY 10036, USA (http:/www.ansi.org/).4ISO/IEC publications are available from the ISO Central Secretariat, Case Postale 56, 1 rue de Varemb, CH-1211, Genve 20, Swit-zerland/Suisse (http:/www.iso.ch/). ISO/IEC publications are also
37、available in the United States from Global Engineering Documents, 15 Inverness Way East, Englewood, Colorado 80112, USA (http:/ Electronic copies are available in the United States from the American National Standards Institute, 25 West 43rd Street, 4th Floor, New York, NY 10036, USA (http:/www.ansi
38、.org/).5Notes in text, tables, and figures are given for information only and do not contain requirements needed to implement the Standard.IEEEDATA MODEL FOR CONTENT OBJECT COMMUNICATION Std 1484.11.1-2004Copyright 2010 IEEE. All rights reserved. 33.1.3 interaction: A recognized and recordable input
39、 or group of inputs from a learner to a content object.3.1.4 launch (v.): To cause a content object to be delivered to a learner. 3.1.5 learner: An individual engaged with a learning technology system to acquire knowledge or skills. 3.1.6 learner attempt: A tracked effort by a learner to satisfy the
40、 requirements of a learning activity thatuses a content object. It may span one or more learner sessions and be suspended between learner sessions.See also: learner session.NOTEThe learner attempt begins with the beginning of the first learner session and continues until the learningactivity termina
41、tes.3.1.7 learner session: An uninterrupted period of time during which a learner is accessing a content object.See also: learner attempt.3.1.8 learning management system (LMS): A computer system that may include the capabilities toregister learners, schedule learning resources, control and guide th
42、e learning process, analyze and reportlearner performance, and schedule and track learners. See also: runtime service.NOTESome implementations of learning management systems also have the ability to launch and deliver content. Forthis Standard, these capabilities are known as a runtime service.3.1.9
43、 runtime service (RTS): Software that controls the execution and delivery of learning content and thatmay provide services such as resource allocation, scheduling, inputoutput control, and data management.See also: learning management system.3.1.10 score: A numerical value or a point on a descriptiv
44、e scale. A score may be the result of a learnerassessment.3.2 Acroynms and abbreviationsAICC Aviation Industry CBT CommitteeCMI computer managed instructionIANA Internet Assigned Numbers AuthorityLMS learning management systemRTS runtime serviceSPM smallest permitted maximumURI Uniform Resource Iden
45、tifierURN Uniform Resource Name4. ConformanceConformance to this Standard is discussed in 4.1 4.6.In this Standard, “shall” is to be interpreted as a requirement on an implementation; “shall not” is to beinterpreted as a prohibition.4.1 Data instancesA conforming data instance shall be an instance o
46、f the data model as defined in 6.1. IEEEStd 1484.11.1-2004 IEEE STANDARD FOR LEARNING TECHNOLOGY4 Copyright 2010 IEEE. All rights reserved.4.2 Sending implementationsA conforming sending implementation shall send data instances that conform to this Standard.4.3 Receiving implementationsA conforming
47、receiving implementation shall accept data instances that conform to this Standard.4.4 Repository implementationsA conforming repository implementation shall accept, store, and provide data that conform to this Standardupon request.4.5 Implementation-defined valuesThe processing and meanings of valu
48、es that are not specified by this Standard (e.g., sentinel, missing, andempty values) are implementation-defined.NOTEFor example, bindings, application profiles, or implementations may specify the processing or meanings ofdefault values or sentinel values for specific data elements. An application p
49、rofile might specify that in the absence ofanother value, the default value for mode is normal.4.6 Smallest permitted maximum valuesThis Standard defines SPM values for data elements with data types that include bag, array, set, andcharacterstring. For these data elements, a receiving implementation or a repository implementation thatconforms to this Standard shall accept and process at least that number of entries or characters specified bythe SPM for the element and may accept and process a larger number.NOTES1The i
