This article or chapter is incomplete and its contents need further attention.
Some information may be missing or may be wrong, spelling and grammar may have to be improved, use your judgment!
The goal of standardization is to improve efficiency of actions and interactions. In more operational terms, a standard is a “formal document that establishes uniform criteria, methods, processes and practices — which may or may not be requirements.” [1]
There are various levels or degrees of standardization:
- Highly formal standardization documents adopted by bodies such as ISO, IEEE, IEC, ITU, etc.
- Standards like the W3C "Recommendations" or the IETF "Requests for Comments" (RFCs) or the OASIS document or IMS pedagogical standards.
- Any sort of specification, formal requirement made by influential organizations or individuals, e.g. technical innovations.
- De facto standards (usually no formalization at all and often referring to the use of products like Microsoft *.doc files)
The difference between a standard, a technical standard, norms, requirement, technical specification is not obvious. E.g., In large standardization organization such as ISO, a standard is usually more high level, takes longer to complete and requires more votes than a technical specification. Furthermore, there may differences between cultures and areas.
For example, wikipedia, defines a technical standard as “an established norm or requirement in regard to technical systems. It is usually a formal document that establishes uniform engineering or technical criteria, methods, processes and practices. In contrast, a custom, convention, company product, corporate standard, and so forth that becomes generally accepted and dominant is often called a de facto standard.”. The definition of software standard (July 2018) reflects acceptance of more informal practice: “Software standards consist of certain terms, concepts, data formats, document styles and techniques agreed upon by software creators so that their software can understand the files and data created by a different computer program. To be considered a standard, a certain protocol needs to be accepted and incorporated by a group of developers who contribute to the definition and maintenance of the standard.”
Standards can be open or propriety. Open means publicly available, not necessarily free.
Standards in educational technology[edit | edit source]
This is a short, somewhat chaotic overview for now. See also:
There are many rationales for adopting standards in education, e.g. sustainability of assets and other information or the possibility to exchange. For the latter, Gartner's (2016) report on Top 10 Strategic Technologies Impacting Higher Education in 2016 coins the exostructure strategy concept to describe a strategy to insure that external collaboration can be leveraged and cites examples like as Open Badges, Learning Tools Interoperability (LTI), Caliper Learning Analytics Interoperability Framework, Question and Test Interoperability (QTI), Accessible Portable Item Protocol (APIP), eduPerson, MLO and Postsecondary Electronic Standards Council (PESC) transcripts.
There are no real general standards, but the closet things are
- Rather formal Instructional design methods like MISA who do make a few minimal assuptions about good pedagogy
- Data standards like IMS Learning Design or IMS Simple Sequencing do rely or support some classes of instructional design models. Even IMS Content Packaging default organisation section can be considered a pedagogical standard if one considers that "shovelware" or "page turners" are a standard pedagogical design ;)
- In some countries there are quite precise curricula standards, e.g.
- American Association for the Advancement of Science’s (AAAS, 1993) Benchmarks for Science Literacy
- National Research Council’s (NRC, 1996) National Science Education Standards,
- Various quality standards used to evaluate institutions, programs or courses.
Pedagogical data standards[edit | edit source]
- Assembly and data description
- Modeling languages (see educational modeling language)
- Combined profiles
- APIs
- More stuff
- The SCORM specifications define some java-script bindings to insure interroperability of simple interactive contents (that is BTW one of the areas where a lot of systems are not Scorm compatible, even if they claim so ...)
- IMS Learning Tools Interoperability (LTI), allows connecting services of platform to those of another, e.g. Moodle with Google Drive.
- IMS General Web Services to allow for interoperability of various systems. This is a fairly new standard (Jan 2006) and is an interesting initiative.
Some technical standards of interest[edit | edit source]
There are various standardization bodies and procedures:
This is a list of bodies that create "real" or "de facto" standards
- RFC - Requests for comments (Informal Internet standards, sometimes standardized by an "official body" sometimes not. The most important source for Internet standards.)
(including ICT standards)
- NIST US National Institute of Standards and Technology
(see also the entries for various standards !)
- AICC/CMI CMI001 Guidelines for Interoperability Version 3.4. October 23, 2000. Includes: AICC Course Structure Format, AICC CMI Data Model, Available at: http://www.aicc.org/.
- IMS Learning Resource Meta-data Specification Version 1.2. Includes: IMS Learning Resource Meta-data Information Model, IMS Learning Resource Meta-data XML Binding Specification, and IMS Learning Resource Meta-data Best Practice and Implementation Guide. Available at: http://www.imsglobal.org
- IEEE Information Technology - Learning Technology - Learning Objects Metadata LOM: Available at: http://ltsc.ieee.org/.
- Advanced Distributed Learning (ADL), Sharable Content Object Reference Model (SCORM)® 2004 3rd Edition, Available at: http://www.adlnet.gov/