Canadian Journal of Learning and Technology

Volume 30(3) Fall / automne 2004

Editorial - A Gentle Introduction to Technical E-learning Standards

Norm Friesen, Ph.D.

Author

Norm Friesen (normf@athabascau.ca) is a researcher at Athabasca University, Canada. Correspondence concerning this article should be addressed to: Norm Friesen, Upper Suite, 15082 Victoria Avenue, White Rock, BC, V4B 1G3.

The observation “the nice thing about standards is that there are so many to choose from” (Tanenbaum, 1981, as cited in Quotation Details, 2004) has been circulating in e-learning standards circles for some time. Although no one involved in standards development would claim to be seeking a situation in which standards and specifications compete, overlap, or develop in parallel, this statement certainly reflects the varied and complex nature of standards organizations and standards development processes. This editorial provides what is hopefully a gentle overview of e-learning standardization—specifically as it relates to Learning Objects and Canadian projects and initiatives. In doing so, this editorial also explicitly introduces the themes and issues developed in the articles on learning objects and e-learning standards that have been included in this special edition of the Canadian Journal of Learning and Technology. This overview of e-learning standardization focuses specifically on three key organizations and on the e-learning specifications and standards they develop. These organizations are the IMS Global Consortium, the IEEE LTSC, and the ISO/IEC SC36.

Standards for E-Learning: What and Why

Standards can be defined as “documented agreements containing technical specifications or other precise criteria to be used consistently as rules, guidelines, or definitions of characteristics, to ensure that materials, products, processes and services are fit for their purpose” (ISO, 2004, 3). In the context of e-learning technology, standards are generally developed for use in systems design and implementation for the purposes of ensuring interoperability, portability and reusability. These attributes should apply to both the systems themselves and of the content, data and processes they manage. The articles in this special edition of the CJLT make frequent reference to “specifications” in addition to “standards.” Specifications represent standards early in their development, prior to receiving approval from accredited standards bodies. Specifications are often experimental, incomplete and rapidly evolving. They capture a rough consensus, and are meant to enable technology development and to manage short-term risk. Standards, on the other hand, are much more conclusive and complete, and they evolve much more slowly. They should capture general acceptance, can serve regulatory purposes, and be used to manage long-term risk. In e-learning, standards are often multi-part, typically consisting of: (a) a “data” or “conceptual” model which specifies the standard’s “normative” content in abstraction; (b) one or more “bindings,” which specify how the data model is expressed in a formal idiom, which is most often XML; and (less frequently) (c) an “API” (Application Programming Interface) or “service definition” that defines points of contact between cooperating systems.

Data models are mentioned quite frequently in the articles included in this collection. By far the most frequently referenced data model is that of the IEEE’s “Learning Object Metadata” standard (IEEE Learning Technology Standards Committee, 2002). This standard specifies the way that learning objects can be consistently and systematically described—much in the same way that a library catalogue record reliably classifies a book or other publication. The expression of this and other data models in XML—or any other formal idiom—receives somewhat less emphasis in the articles in this edition. One notable exception is the article in this issue by Petrinjak and Graham, “Creating Learning Objects from Pre-Authored Course Materials,”, which focuses quite specifically on the “mark-up” of course contents using XML, and provides examples of what such mark-up might look like.

Since the advent of the personal computer, digital technologies have, of course, become increasingly common in education—both in distance and classroom education and training settings. However, these technologies have typically been applied in ad hoc and divergent forms: Innumerable courses, course components and systems for managing and delivering them have been developed independently of one another, often at great expense. Moreover, this content and these systems are often created in a manner that makes it very difficult, if not impossible, to support their interchange or their successful interoperation. Standards in e-learning address these shortcomings by ensuring the interoperability, portability and reusability of this content and of these systems.

The development of technical standards in e-learning can be seen as part of the maturation of this recently emergent field or industry. According to a recent survey of the Information Technology (IT) industry in The Economist (Siegele, 2003), similar process of industry maturation has occurred in a wide variety of sectors:

Railways, electricity, cars and telecommunications all learned to love standards as they came of age. At a certain point in their history, it became clear that rather than just fighting to get the largest piece of the pie, the companies within a sector needed to work together to make the pie bigger…. Today, the IT industry is finally getting the standards religion. (Siegele, 2003, 5)

Although there is certainly some debate on the matter (e.g. Friesen, 2004a), “getting the standards religion” ( 5) can also be said to characterize what has been happening the e-learning sector as well.

Alphabet Soup: Ims, Ltsc, and Iso/Iec Jtc1 Sc36

As mentioned above, this introductory piece provides an overview of three major organizations that contribute to the development of e-learning standards: The IMS Global Consortium, the IEEE LTSC (Institute of Electrical and Electronics Engineers, Inc., Learning Technology Standards Committee), and the ISO/IEC (International Standards Organization/International Electrotechnical Commission). There are other standards organizations (many of them national or regional standards bodies) that may make significant contributions to international e-learning standards development, but which fall outside of the scope of this introduction. These include ANSI (American National Standards Institute), CEN-ISSS (European Committee for Standardization-Information Society Standardization System), DIN (Deutsches Institut für Normung), BSI (British Standards Institute) and the CSA (Canadian Standards Association).

Ims

The IMS Global Learning Consortium, Inc. (IMS) “develops and promotes the adoption of open technical specifications for interoperable learning technology” (IMS, 2003, 1). The IMS is the standards-related organization that receives by far the most frequent mention in the articles in this special issue, and that can be said to enjoy the highest recognizability within the educational technology community. The IMS is a non-profit organization that includes more than 40 Contributing Members and affiliates, a significant number of which are American and British commercial entities, and a smaller number, which are universities and federal governmental agencies. Members are mainly English-speaking, which sometimes leads to a de-emphasis on multilingual and multicultural issues. The IMS is the only standards development organization highlighted here that has significant, direct representation from those involved in the K-12 sector. Canada has been represented in the IMS though the sponsorship of Industry Canada, and at least two IMS working groups have been co-chaired by Canadian representatives.

Numerous IMS specifications are discussed and referenced in the articles included in this collection. This issue’s first article alone (Mohan’s “Building an Online Course Based on E-Learning Standards”) discusses at some length two IMS specifications: Content Packaging, which is designed to standardize the way learning objects and metadata are “parceled” for easy delivery and access; and the Digital Repositories Interoperability specification, which recommends ways in which repositories can operate together (or interoperate) to simplify access and use.

In the second paper, Petrinjak and Graham reference at least two IMS specifications in discussing “learning object semantic structures.” These specifications are the IMS Question and Test Interoperability specification (which allows questions and other data to be shared between test banks and testing applications) and the IMS Reusable Definition of Competency or Educational Objective, which allows for the standardized expression of competencies and outcomes.

The article by Magee mentions yet another specification, the IMS Vocabulary and Definition Exchange, which, as the article itself explains, is “designed to allow the description and creation of controlled vocabularies that could be easily interchanged”. Finally, the last two articles in this collection (Buzza, Bean, Harrigan, & Carey, and Paquette) have as their primary focus an IMS specification which has recently been receiving a great deal of attention among researchers in Canada. This is the IMS Learning Design, a specification which has as its aim the standardized expression of units of instruction (including activities, environments, roles, resources, and services) in order to allow these units to be shared, reused, and executed or “played” like a script by software systems. The first of these two articles considers what would be involved in the construction of collections or “repositories” of these instructional units or scripts. The second and final article in this collection presents a conversation among researchers who are intensively involved in the implementation of the IMS Learning Design specification in a range of contexts.

Ieee Ltsc

The IEEE “is a non-profit, technical professional association of more than 380,000 individual members in 150 countries” (IEEE, 2004, 1). It is also an accredited standards development organization. Within the IEEE, the Learning Technology Standards Committee (LTSC) is chartered by the IEEE Computer Society Standards Activity Board to “develop accredited technical standards, recommended practices, and guides for learning technology” (LTSC, 2004, 1). The LTSC also “coordinates formally and informally with other organizations that produce specifications and standards for similar purposes” (LTSC, 2004, 1). These other organizations include the IMS and the e-learning standards development body in the ISO/IEC. The LTSC’s active membership includes individuals from small and large private sector organizations, the US military and military contractors, and from governmental organizations and universities of various nationalities. The LTSC, like the IEEE as a whole, is a respected source of standards, especially in the English-speaking world. This e-learning standards body is responsible for having produced the first “official” e-learning standard: the aforementioned Learning Object Metadata standard or simply, the “LOM.” Despite the prominence and productivity of this group, IEEE e-learning standards are seen as benefiting significantly from the approval that can only be conferred by organizations such as the ISO and IEC—those with official, delegated international representation.

Iso/Iec

The ISO is a standardization body that is recognized internationally, and that was established under the auspices of the United Nations. Founded in 1946, it is responsible for creating standards in many areas, including computers and communications. Its members comprise the national standards organizations of approximately 140 countries, including the Standards Council of Canada (ISO, 2004a, 6). The IEC is a similarly international organization that “prepares and publishes international standards for all electrical, electronic and related technologies” (IEC, 2004). To avoid duplication of efforts, the ISO and IEC formed a Joint Technical Committee (JTC1) to “develop, maintain, promote and facilitate IT standards” in a number of areas of common interest (JTC1, 2004 1).

One of the Sub Committees of JTC1, SC36, was formed in 2000 with the task of developing standards specifically for “information technology for learning, education, and training” (ISO, 2002, 1). In SC36, participation occurs on the basis of national representation (this is also the case in JTC1, the ISO and the IEC in general; for more about SC36 specifically, see: http://jtc1sc36.org). In passing resolutions, drafts and standards documents, one vote is given to each country at the table, with each nation being represented by a nationally appointed delegation or body. The Canadian delegation to SC36 is administered and supported through the Standards Council of Canada, and has recently also received support from Industry Canada. Plenary meetings of SC36 are held twice annually, in conjunction with multiple meetings of the SC36 working groups that are individually responsible for developing standards in different sub-domains. Of the e-learning standards development organizations described here, SC36 is unique in the explicitly international, multi-lingual character of its representation, in its emphasis on standards for collaborative e-learning (see Friesen, 2004b) and in its emphasis on formally coordinating standards development in e-learning with relevant standards activities in other areas.

Red Hot to Cool Blue: The Standards Development Process

A widely circulated diagram that lays out the e-learning standards development process has been provided by the IMS. It serves as a good starting point for understanding how the IMS, LTSC, and SC36 work together and with the larger e-learning community. This diagram depicts the standards development process as a predominantly linear one. Although this process is depicted as cycling through iterations and feedback loops, it ultimately appears to move from “research and development concepts” and “user needs” to eventually arrive at “approved standards.” In the original version of this diagram, the work and activity of stakeholders and developers is shown in “hot” red, with the colour blue used to suggest the “cooled” stability of officially approved standards.

Figure 1. Standards development process.

Figure 1 indicates how implementations, reference models, specifications and standards can be understood as fitting together into an overall standardization process. Implementations and reference models refer to ways that specifications and standards are applied in communities. They include systems and tool development, as well as “application profiling” work that integrates multiple specifications or standards (e.g. SCORM, the “Sharable Content Object Reference Model”) or interprets and applies a single standard (e.g. CanCore) (see Friesen, Hesemeier, Fisher, Roberts, & Habkirk, 2004; Duval, Hodgins, Sutton, & Weibel, 2002, for more on application profiles). A significant proportion of implementation and profiling work mediates between the abstraction of many standards and specifications and the particularities and requirements of implementation.

The IMS diagram also makes it clear that the activity of the IMS and of similar organizations applies only to the development of specifications. Examples of other organizations that focus particularly on specifications development are the AICC (Aviation Industry CBT [Computer-Based Training] Committee) and the W3C (World Wide Web Consortium). The AICC has developed nine AICC Guidelines and Recommendations resources—one of which is referenced in SCORM, and has been adapted by the LTSC for standardization. The W3C, on the other hand, “develops interoperable technologies (specifications, guidelines, software, and tools) to lead the Web to its full potential” (World Wide Web Consortium, 2002, 1). The W3C has been responsible for developing XML and other specifications that form the foundation upon which e-learning and other standards and specifications are now being built. One of its activities, the W3C Web Accessibility Initiative, promotes means for accessing the Web for people with disabilities, and is central to the article by Kelly, Phipps, and Swift in this collection.

The IMS diagram is slightly less accurate in indicating the way that user and stakeholder needs and input are integrated into the standards development process. These inputs can and should inform standards at all stages of their development—not just at the beginning. On its way to becoming a standard, a given specification tends not to move in linear or even circular/iterative fashion that is easy to delineate. As will be illustrated below, work is can be shared across the IMS, LTSC and SC36 in a manner that sometimes appears to be ad hoc, through arrangements derived from mutual need, or as a result of political considerations.

In the case of the IMS, the LTSC and SC36, standards development work is apportioned to working groups, with each working group developing a specification or standard during a period of time that can last from nine months to two or more years. Because a standard or specification can develop through a number of successive generations, the lifetime of working groups tend to be longer rather than shorter. A second diagram from the IMS (See Figure 2) clearly schematizes this standards or specifications development cycle—showing very clearly how it occurred at one point in the IMS itself.

Figure 2. Specification development cycle.

In the case of each of the three standardization organizations considered in this paper, a plenary body governs working group activity. This body must approve formal applications for starting new working groups or working group activities. As the diagram also shows, working group activity simultaneously feeds into and draws from the community of developers and implementers, whose feedback and requirements are expected to be incorporated into standards as they are being developed. Also, each organization develops standards or specifications documents through a prescribed set of stages, beginning with a proposal or scope, and proceeding through base or committee drafts through to a stable version of a specification or standard that is released to the public. In the case of the LTSC and ISO/IEC JTC1 SC36 (2002), documents proceed from one stage to the next through highly formalized balloting procedures, in which numerous ballot comments must be individually addressed.

Lifecycle of a Standard

This section briefly presents the history of two particular areas of specification activity—the development of the IEEE Learning Object Metadata (LOM) standard and the IMS Learning Design specification (IMS LD)—as case studies in standards development. The history of these normative documents illustrates the intricate, inter-organizational dynamic of the standards development process, and highlights the complex interaction of community requirements and standards development.

The Ieee Lom Standard

The IEEE LOM, a standard that is central to a majority of articles in this collection, was originally developed in response to the very practical needs of those assembling online collections of reusable learning materials (learning objects). These collections required standardized metadata for the purposes of discovery, management and resource sharing. In 1996, the IMS (then known as the Instructional Management Systems consortium), and ARIADNE (Alliance of Remote Instructional Authoring and Distribution Networks for Europe) began the joint development of the Learning Object Metadata, at approximately the same time as the emergence of the Dublin Core Metadata Initiative. The development of the LOM was subsequently handed over to the IEEE LTSC, where, after multiple drafts and revisions, it was developed into an official IEEE standard.

While the LOM was being developed, implementers and others required stable, publicly available versions of the specification—both of the abstract data model, and of its bindings in XML and other encodings. This need was addressed by the IMS, which developed these versions or documents, and in effect “hosted” open and stable versions of the specification for the general community. Now that the IEEE has standardized the LOM, the IMS will be officially referencing the IEEE document, rather than referring implementers to its earlier versions of metadata documents. The next step generally envisioned for standards like the LOM is formal standardization by the ISO/IEC through SC36, with one option being to “fast-track” the standard through a high-level JTC1 committee.

However, because the LOM is already very widely accepted and implemented in its current form, and its further standardization in SC36—either via SC36 balloting procedures or “fast tracking” through JTC1—brings with it risks of significant revision or even outright rejection. Consequently, it has been agreed by many stakeholders that stabilizing and supporting the standard in its present form is currently more important than its further standardization. As a further result, the LOM will not be subjected to further incremental revisions and minor changes. Instead, a longer-term perspective is being taken, and ways are being considered for the IEEE LTSC and the SC36 subcommittee to work together in the future to develop “next generation” or “2.0 version” of this metadata standard over a number of years. In 2003 and 2004, Canadian representatives have been submitting documents and studies (e.g. Friesen, in press) in the hopes of initiating productive discussions about the development of new versions of this standard.

Ims Learning Design

IMS LD is a specification that has a much shorter history than the LOM. However, as mentioned above, this specification has been the subject of great interest in the Canadian e-learning community—an interest, which is clearly registered in the final two articles in this collection. The IMS Learning Design specification has its beginnings in the Open University of the Netherlands, in the form of an Educational Modeling Language developed by Dr. Rob Koper. This modeling language was brought—more or less mid-stream—into an IMS working group that was originally charged with the task of developing a specification related to instructional design. This working group, co-chaired by Canadian Dr. Katy Campbell, subsequently undertook the task of simplifying this modeling language or system, and adapting it to existing IMS specifications, including an earlier IMS version of Learning Object Metadata. IMS Learning Design was released as a “Version 1.0” IMS specification in February 2003, and its subsequent uptake and implementation has involved a wide variety of international initiatives or groups, as well as some systems developers and vendors. These include the Valkenberg group featured in the last article in this collection, the European-based “UNFOLD” community, as well as Blackboard, e-live Learning Design, and LAMS (Learning Activity Management System) International.

Conclusion

Despite the permanence, stability and univocality implied by the term “standard,” it is clear that the processes and histories of standards development are anything but predicable, unambiguous and simple. Perhaps especially in an emerging domain such as e-learning, standards development involves the difficult task of hitting a moving target from a position that is itself changing. The “target” is represented by emerging and accepted practices, capabilities and requirements in the domain, and the “changing position,” by the standards development dynamic itself. The articles in this special edition of the CJLE demonstrate, however, that a gradual alignment of position and target seems to be occurring. Many of the articles foreground the opportunities and challenges that have been encountered as existing activities, content and requirements are applied to emergent standards and specifications.

In his article in this issue, “E-Learning Lifecycles,” Magee reflects on this process quite explicitly, and refers the notion of “communities of practice” as a way of conceptualizing and clarifying complex implementation and adoption issues. Magee concludes: “It is apparent that if e-learning specifications are going to achieve adoption and become more than just a tool for organizing information, they need to be able to give each community of practice the power to place information into a meaningful context”. The articles in this collection can be seen in many ways as describing means through which abstract information—data models and XML expressions—is made concretely meaningful and useful in the context of implementer and user communities.

References

AICC. (2002). AICC FAQ. Retrieved September 21, 2004, from http://www.aicc.org/pages/aicc_faq.htm

Duval, E., Hodgins, W., Sutton, S., & Weibel, S. L., 2002. Metadata principles and practicalities. D-Lib Magazine, 8(4). Retrieved September 21, 2004, from http://www.dlib.org/dlib/april02/weibel/04weibel.html

Friesen, N. (2004a). Three objections to learning objects. In R. McGreal (Ed.) Online education using learning objects (pp. 59-70). London: Routledge Falmer.

Friesen, N. (2004b). Interoperability in Asynchronous Collaborative Learning Forums Proceedings of the IEEE International Conference on Advanced Learning Technologies. Retrieved September 21, 2004, from http://www.learningspaces.org/n/papers/ACLF.pdf

Friesen, N. (in press). A report on the international learning object metadata survey. International Review of Research in Open and Distance Learning, 5(3).

Friesen, N., Hesemeier, S., Fisher, S., Roberts, A., & Habkirk, S. (2004). CanCore: Best Practice for Learning Object Metadata. In R. McGReal (Ed.) Learning Objects and Metadata (pp. 225-235.). London: Kogan Page.

IEC. (2004). International Electrotechnical Commission - IEC. Retrieved September 21, 2004, from http://www.tisi.go.th/iso_iec/iec_e.html

IEEE Learning Technology Standards Committee. (2002). Final 1484.12.1-2002 LOM Draft Standard. Retrieved September 21, 2004, from http://grouper.ieee.org/LTSC/wg12/20020612-Final-LOM-Draft.html

IEEE. (2004). About the IEEE. Retrieved September 20, 2004, from http://www.ieee.org/portal/index.jsp?pageID=corp_level1&path=about&file=index.xml&xsl=generic.xsl

IMS. (2003). IMS Website. Retrieved September 20, 200, from http://www.imsglobal.org/

ISO. (2004). The magical demystifying tour of ISO 9000 and ISO 14000 - In the beginning. Retrieved September 4, 2004 from http://www.iso.org/iso/en/iso9000-14000/basics/general/basics_2.html

ISO. (2004a). About ISO - Introduction. Retrieved September 4, 2004 from http://www.iso.org/iso/en/aboutiso/introduction/index.html

ISO/IEC JTC 1SC36. (2002, June). Information technology: Learning by IT. ISO Bulletin, SC36 N0264. Retrieved September 1, 2004, from http://jtc1sc36.org/doc/36N0264.pdf

JTC1. (2002). JTC1 Website. Retrieved September 21, 2004, from http://www.jtc1.org/

Learning Technology Standards Committee. (2004). LTSC website. Retrieved September 21, 2004, from http://ltsc.ieee.org/

Quotation Details (2004). Quotation Details. Retrieved September 28, 2004, from http://www.quotationspage.com/quote/473.html

Tannenbaum, A. (1981). Computer networks. (2nd ed.) New York: Prentice-Hall.

Siegele, L. (2003, May 8). Survey: The IT Industry. The Economist. Retrieved September 21, 2004, from http://www.economist.com/surveys/displayStory.cfm?Story_id=1747362

World Wide Web Consortium. (2002). W3C Homepage. Retrieved September 21, 2004, from http://www.w3.org/


ISSN: 1499-6685