Skip to main content
U.S. flag

An official website of the United States government

DoDI 1322.26 Fungible References

Department of Defense Instruction (DoDI) 1322.26 formally assigns responsibility to the Advanced Distributed Learning (ADL) Initiative and Defense Advanced Distributed Learning Advisory Committee (DADLAC) for maintaining the Instruction’s fungible references. The fungible references serve as the official reference and support resource for DoDI 1322.26, and defines technical requirements and best practices across the DoD.

The fungible references contain the most current technical information available regarding the contents of DoDI 1322.26. DoD Components are encouraged to refer to the fungible references on a regular basis for the latest available technical information and guidelines.

The ADL Initiative and the DADLAC update the fungible references when new information or recommended changes to standards, specifications, conformance, testing, acquisition, and other distributed learning (DL) topic areas are identified. Thus, the fungible references are expected to change on a routine basis due to DoD evolving needs and technological advancements—too frequent to include in the base Instruction content outlined in the DoDI 1322.26.

The fungible references are organized as follows:

  1. Definition
  2. Technical Specifications and Standards
  3. Implementation Guidance
  4. Other Acquisition Guidance and Development Considerations
  5. Reference


Distributed Learning is defined in DoDI 1322.26 as learning content and systems, mediated with technology, that are accessed through a network or experienced via portable media.

Technical Specifications and Standards

Distributed learning specifications and standards are published technical documents that are designed to ensure interoperability of learning technology products, services, and data. Specifications and standards help establish consistent protocols that can be universally understood and adopted to simplify DL processes.

The ADL Initiative is the principal steward of two DL specifications and standards: Shareable Content Object Reference Model (SCORM®) and Experience Application Programming Interface (xAPI). The affordances of SCORM and xAPI, and the various types of DL they support, underpin the DoDI 1322.26 policy.

  • SCORM is a collection of standards and specifications that enables self-paced, asynchronous DL that is delivered through a web browser. Additional information is available at DoDI SCORM Reference.
  • xAPI is both a learning-technology specification and a suite of web-service application programming interfaces (API) that support a simple object-based model for describing, recording, and accessing one’s experience or performance within a formal or informal learning activity. Additional information is available at DoDI xAPI Reference.

Specifications and standards make it easier to understand and compare competing products and systems. It is only through the application of such standards that new DL products can be tested and verified for conformance. The ADL Initiative oversees the DL conformance testing software for SCORM and xAPI.

Implementation Guidance

Acquisition of Training and Education Systems

The DoD conducts acquisition of DL systems, such as learning management systems (LMSs), learning content management systems (LCMSs), or learner record stores (LRSs), in support of its training and education programs. DoD Components should consider the following before acquiring new DL systems:

  • Standards Compliance: DoD Components shall develop or acquire DL systems that support the latest versions and editions of existing DL specifications and standards to maximize interoperability.
  • Data Interoperability: DoD Components should consider acquiring DL systems that enable the transmission of data to other systems, such as those that support human resources, student information management, and training management.
  • Adobe Flash™: DoD Components should thoroughly examine the controls, interfaces, and capabilities of DL systems for Adobe Flash use or reliance before acquiring them. Deprecation of Adobe Flash will render dependent features useless and create security vulnerabilities within the system.
  • 508 Compliance: DoD Components shall thoroughly examine 508 compliance of any new DL systems and its applications, including authoring tools. The Voluntary Product Accessibility Template, commonly referred to as VPAT, is one method for such examination. VPAT is a document used to evaluate how accessible an application is according to the Section 508 standards.

SCORM and xAPI Implementation Options

DoDI 1322.26 establishes guidance for use of SCORM and xAPI that includes adopting existing DL specifications and standards to support interoperability of DL systems. The ADL Initiative updates the fungible references as best practices emerge and/or alternative practices for SCORM and xAPI are deemed to be preferable for DL.

DoD Components should adopt existing DoD Information Technology Standards and Profile Registry specifications and standards using one of the following options:

Option 1: Implement a SCORM-conformant LMS
  • Conform to all mandatory requirements for a supported version of SCORM (supported versions are SCORM 1.2, SCORM 3rd Edition and SCORM 2004 4th Edition).
Option 2: Implement SCORM-conformant LMS with LRS
  • Conform to all mandatory LMS requirements for a supported version of SCORM (supported versions are SCORM 1.2, SCORM 3rd Edition and SCORM 2004 4th Edition).
  • Conform to the xAPI specification version 1.0.3 or IEEE 9274.1.1.
  • Can optionally conform to the xAPI SCORM Profile to support translation and exchange of historic and incoming SCORM data to xAPI.
  • Can optionally conform to the Quartz version of the cmi5 specification to support launch, packaging, and other cmi5-specific features.
  • Can optionally send or receive data to and from other LRS implementations.
Option 3: Implementing Stand-alone LRS
  • Conform to the xAPI specification version 1.0.3 or IEEE 9274.1.1.
  • Conform to all mandatory LRS requirements for the targeted version of xAPI.
  • Can optionally send and receive data to or from other LRS implementations.
  • Can optionally conform to the Quartz version of the cmi5 specification or to the SCORM Profile.

When deploying Option 2 and Option 3 that leverage xAPI, the following processes must be followed:

  1. When mapping trackable events to xAPI Statements, the vocabulary in xAPI (e.g. Verbs, Activity Types) should leverage a suitable existing vocabulary found in known xAPI Profiles. Existing vocabularies must be used rather than creating a new vocabulary term that performs the same function. The ADL Initiative maintains a listing of these profiles deemed to be suitable for DoD usage. Note: The term “vocabulary” is used loosely in this guidance and will be replaced with the term “concept” when using Linked Data solutions, such as those that leverage the xAPI Profile Specification.
  2. If the intended function of an xAPI Verb is slightly different from an existing verb, or additional data is needed, strongly consider use of context, result, extensions, or other xAPI mechanisms to add this data to the Statement.
  3. Where applicable, use of entire xAPI Profiles is highly encouraged. Examples include cmi5 for course-based content and the Video Profile for any sort of media (audio/video).
  4. If existing xAPI Profiles do not meet organizational requirements, then consider creating a new xAPI Profile. The xAPI Profile Specification must be followed for the creation of any new vocabulary term.
  5. Profile authors must follow Internationalized Resource Identifier (IRI) design best practices, the following IRI pattern should be adopted by anyone creating new concepts for a profile: [profile name] / [concept type] / [concept]. Only customize the content in the IRI in brackets. For example, the Video Profile Verb,, follows this pattern.
  6. xAPI Profiles should include information about the profile such as the name of the profile, a description, the organization or person that authored it, and the date/time it was published.

Section 508 Accessibility

DoD Components must comply with federal regulations mandating electronic and information technology resources be made accessible to people with disabilities (e.g., “508-compliant”). Access to these resources and the experience using these resources shall be comparable to non-disabled individuals in compliance with the requirements, applicability, and alternatives provided in DoD Manual 8400.01-M, Procedures for Ensuring the Accessibility of Electronic and Information Technology (E&IT) Procured by DoD Organizations. Current specific standards and methods for development and testing DL systems for Section 508 compliance are available at Section

Deprecation of Adobe Flash

The Adobe Flash plug-in is a browser-based technology which has been commonly used to support the development of web-based courseware and content by the DoD. Due to ease of use and popularity in DL authoring tools, use of this technology in DoD DL systems is rampant. In the year 2020, Adobe Flash will no longer be supported by Adobe or by commonly available Internet browsers allowed for use within DoD environments. As a result, DoD Components:

  • SHOULD NOT develop, fund, pay for, or acquire any DL content, tools, websites, or any other capability that contains any Adobe Flash code of any version or derivative of Adobe Flash.
  • SHOULD NOT update, modify, refurbish, or re-engineer any DL content, tools, websites or any other capability to a state in which it contains Adobe Flash code. This includes non-Adobe Flash modifications that leave the content, etc. in a state of containing Adobe Flash.
  • SHOULD carefully analyze the user interface and output of authoring tools, including web tools or plug-ins, currently in use for underlying Adobe Flash technology, and desist in usage of tools found to contain or use any form of underlying Adobe Flash technology.

Other Acquisition Guidance and Development Considerations

Security: DoDI 1322.26 does not specifically address cybersecurity considerations, although the ADL Initiative recognizes that such considerations are imperative for DL implementations. Recommendations, such as the deprecation of Adobe Flash, may be made as a result of a combination of provisions, including security.

Technical Publications: When specifically acquiring or developing Interactive Electronic Technical Manuals, consider the Darwin Information Typing Architecture (DITA) or S1000D specifications.


DoD Information Technology Standards Registry (DISR) is an online repository of Information Technology (IT) standards. The standards are intended to facilitate interoperability and integration of systems within the Global Information Grid (GIG) Access website.