Inventing the connective tissue for open K-12 curriculum
How Learning Tapestry created the K-12 Open Content Exchange specification and are actively proving it through half a decade of deployments.
The Problem: The Invisible Failure Between Author and Teacher
A curriculum author writes a unit. A teacher uses it in class. Between those two moments lies an obstacle course that nobody talks about: authoring tools, content management systems, export pipelines, learning management systems, print production, third-party distribution platforms, district content filters, device rendering engines.
At every hop, something breaks. Structure is lost. Links break. Images drift. Math is mangled. Accessibility metadata disappears. A carefully authored lesson arrives in a classroom missing half of what made it work.
The reason is simple: there has been no public specification for K-12 content exchange. Every platform operator invented their own undocumented conventions. Every integration was bespoke. Every migration was a teardown. Content moved between systems the way luggage moves between airlines: technically transferred, frequently damaged, occasionally lost entirely.
The curriculum interoperability problem was not that systems could not talk to each other. It was that there was no shared language for the conversation.
The reason there was no shared language was not a technical difficulty. Specifications for content exchange exist in other domains. The reason is that nearly none of the people drafting K-12 content specs were operating in production. They were designing in theory what they had never pressure-tested in practice.
A specification is only as good as its reference implementations. Without running systems that consume and produce spec-compliant content at scale, a spec is a document. With them, it is infrastructure.
The Solution: Specification That Lives Where Authors Already Are
Learning Tapestry was in the unusual position of already operating production platforms for two of the most demanding curriculum pipelines in the country: OpenSciEd and Louisiana’s statewide ELA initiative. Steve Midgley’s background in federal education technology policy supplied the standards credibility and convening relationships. The operational depth of LT’s existing systems supplied the pressure-testing that separates a spec that works from a spec that reads well.
OCX was designed in Google Docs authoring workflows where most K-12 curriculum is actually written. That single design choice is why OCX survived where more elegant specs failed.
OCX was not designed in the abstract. It was designed around the actual authoring environments, export formats, and consumption patterns of real curriculum publishers. The result is a specification that works because it meets authors and systems where they already are.
Content marked up with OCX can be consumed by a learning content management system, exported to an LMS, rendered to HTML, and compiled to print without losing structure. The same content, faithfully represented across every delivery channel.
LCMS Engine and Bulk Downloader are published on GitHub under the Apache-2.0 license. Not whitepapers about what an implementation might look like, but running code that processes real curriculum in production every day.
The Impact
OpenSciEd runs an OCX-aligned pipeline for its science curriculum. Louisiana’s statewide ELA initiative is aligned with OCX. New Visions for Public Schools, Odell Education, and Open Up Resources have adopted or aligned their content workflows with the specification.
The real success measure is this: OCX is boring. Authors using it do not think about it. Content moves between systems and arrives intact. That is the entire point. The best infrastructure is invisible.
OCX was designed to disappear. The point is curriculum that moves, not a spec that impresses.
Most useful ed-tech specs are the ones nobody argues about five years later.
References
- K-12 OCX Working Group, “K-12 Open Content Exchange Specification,” k12ocx.github.io.
- Learning Tapestry, “LCMS Engine,” GitHub.
Explore the specification. Or talk to us about using it.
A public standard for K-12 curriculum exchange, backed by production implementations and years of real-world use.
View the specification Let’s talk