The problem standards solve
Imagine moving a course from one system to another. If each system stores quizzes, grades and files in its own private way, someone must rebuild everything by hand. Now imagine a learner who wants to take records of their achievements from one provider to another. Without a shared format, that is a manual task too.
A standard is an agreed description of how something should be done, so that independent makers can build parts that fit together. A standard is open when its specification is publicly available, can be implemented by anyone without unreasonable fees, and is developed or maintained through a transparent process. That is a general description; groups define it in slightly different ways.
Open standards are not the same as open-source software. Software is a product; a standard is a document that products follow. A closed program can follow an open standard, and an open-source program can use a private format.
What standards cover in education
Web and document formats. HTML for web pages, EPUB for e-books, and CSV for simple tables are open and widely supported. Content stored in such formats can usually be opened by many programs now and in future. Questions about file formats and hosting often come down to choosing formats like these.
Accessibility. The Web Content Accessibility Guidelines describe how to make web material usable by people with a wide range of disabilities. Following them is central to web accessibility standards work, and many institutions use them as a benchmark.
Learning content packaging. Specifications such as SCORM packaged online lessons so that they could be loaded into different course systems, and newer approaches have been developed since. The aim is to avoid rebuilding a lesson for each platform.
Tool connections. Learning Tools Interoperability is a specification that lets an external tool, such as a quiz app, be launched from inside a course system without separate logins and with a defined way of returning results. This makes it simpler to combine learning management systems with other tools.
Question and test exchange. Specifications for describing quiz questions allow question banks to move between systems.
Activity data. The xAPI specification describes how to record learning activities as simple statements, such as a learner completing a video. This feeds into learning analytics, with the privacy cautions that raises.
Credentials. Open badges describe achievements in a portable, verifiable way, and are related to wider work on micro-credentials and verifiable digital records.
Metadata and discovery. Shared vocabularies for describing resources, such as title, author, subject and license, help search tools find materials across repositories and libraries.
Character and language support. Standards such as Unicode allow text in nearly all the world’s writing systems to be stored and displayed consistently, which matters for multilingual learners.
The names above are technical shorthand. You do not need to learn them to benefit, but it helps to recognize them when a supplier or a project mentions them.
Why this matters for open education
Avoiding lock-in. If content and records are stored in open formats, an institution can change tools without losing its work. This makes it easier to try new tools, including open-source ones.
Reuse. Open educational resources are more useful when they are published in formats that many tools can read and edit. A lesson locked in a single proprietary file is harder to adapt.
Accessibility. Standards give teachers and developers a common target for inclusive design, and a way to test whether it has been met.
Portability for learners. Standards for credentials and records help people carry what they have learned across institutions.
Longevity. Open formats tend to remain readable for longer because many parties can support them.
Limits to keep in mind
Claims versus reality. A product that says it supports a standard may implement only part of it, or a particular version. Ask for demonstrations, not only statements.
Competing standards. Several specifications can cover similar ground, and the field changes. Older standards may remain in use for years after newer ones appear.
Complexity. Standards documents are long, and implementing them takes skill. Small projects sometimes cut corners.
Interoperability is not the same as quality. Two tools may exchange data perfectly and still teach poorly.
Governance varies. Some standards bodies are broadly representative; others are dominated by a few big organizations. Process matters.
Questions to ask when choosing a tool
- Which standards does it support, and which versions?
- Can I export my content, learners’ records and results in an open format?
- Has it been tested for accessibility against recognized guidelines?
- Can it connect to the other systems we already use?
- Is the specification free to read and to implement?
These questions are useful whether you are a teacher choosing an app, an administrator comparing systems, or a learner deciding where to keep a portfolio.
The quiet infrastructure
Open standards seldom get attention because, when they work, nobody notices them. A quiz moves, a record transfers, a page opens in a screen reader. Together with open content, open data and open-source software, they form the plumbing that lets open education operate across institutions and borders instead of inside a single vendor’s system.