Libraries & Implementations

This page is coming soon. The OpenChronology standard is pre-release and the library ecosystem is just getting started. This page will be the living registry of community implementations as they appear. In the meantime, see the specification or use Chronology Studio as the reference JavaScript implementation.

What this page will contain

A registry of implementations, organized by language

OpenChronology is language-agnostic by design. The format is a JSON document with a published schema — any language with a JSON library can implement a parser in an afternoon. This page will list every known implementation so developers can drop one into their project without starting from scratch.

Listings will be tagged with capability badges so you can immediately see what each library supports:

parse — Read and deserialize .chron files validate — Validate against the JSON Schema create — Programmatically generate events calendar — .chroncal support universe — .chronverse support package — Pack/unpack .chronpkg bundles stream — .chronstream feed support render — Timeline visualization

Languages planned for coverage: JavaScript / TypeScript, Python, Rust, Go, PHP, Ruby, Java / Kotlin, C# / .NET, Swift, Dart / Flutter, and others as the community grows. Each section will list official and community libraries with their spec version support, maintainer, and status (Official, Community, or Experimental).

Available now

The reference implementation

openchronology.js — JavaScript / Browser & Node.js
The official reference parser, hosted at openchronology.org/src/openchronology.js. ESM module. Covers parse, validate, create, and render (via Chronology Studio). Spec v0.3. Maintained by the OpenChronology Working Group.

For implementers

Building a library?

Everything you need to write a conforming parser, validator, or creator is in the open:

The specification — normative definition of every field, every file type, and all conformance tiers.
The schema registry — machine-readable JSON Schemas for .chron, .chroncal, .chronverse, .chronpkg, and .chronstream.
The AI Guide — paste a single context block into any AI assistant and bootstrap a working implementation in minutes.
Example .chron files — 17 validated events you can use as test fixtures.

The minimum recommended implementation for a useful library is parse + validate + create for the base .chron event type. That alone covers the vast majority of use cases.

To register your library for listing on this page, open a GitHub issue or pull request against github.com/knoj/openchronology. There is no approval process — implementations that parse correctly and declare their supported spec version are listed.