You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rename format from Codex to CDX (Content-addressed Document eXchange)
The format shared the name "Codex" with OpenAI's coding-agent platform,
which now dominates developer/AI search and is broadening toward document
workflows. Rename to CDX to restore discoverability and a distinct identity.
Changes:
- Brand/prose: Codex -> CDX; introduce the expansion "Content-addressed
Document eXchange" at first mention; drop redundant "CDX Document Format"
- Manifest spec-version key: "codex" -> "cdx"
- MIME types: application/vnd.codex* -> application/vnd.cdx*
- Extension namespace IDs: codex.* -> cdx.* (8 extensions)
- Schema $id and $ref host: https://codex.document -> https://cdx.dev
- Tooling: generate-template.ts (emits cdx key/IDs) and
check-example-coverage.ts (extension-id matcher) updated
Intentionally unchanged: the .cdx file extension (already name-independent);
the GitHub repo/org name and repo-path URLs (separate admin action; GitHub
auto-redirects); package.json name; docs/archive/** (historical record).
Validation: schemas compile, all 11 example documents validate, 71/71
cross-references resolve, 8/8 extensions and 15/15 schemas covered.
Note: https://cdx.dev is a placeholder schema namespace (JSON Schema $id
URIs need not resolve); repoint at a controlled domain if desired.
**An open specification for documents that unify viewing and editing, with modern security and machine readability.**
6
+
**CDX — Content-addressed Document eXchange.**An open specification for documents that unify viewing and editing, with modern security and machine readability.
7
7
8
8
> Status: Draft Specification (v0.1)
9
9
@@ -85,7 +85,7 @@ This divide creates workflow friction, format conversion overhead, and lost fide
85
85
86
86
## Key Feature: Verifiable Provenance
87
87
88
-
Codex documents form a **cryptographic hash chain** — each document's identity IS its content hash, and each document can reference its parent by hash:
88
+
CDX documents form a **cryptographic hash chain** — each document's identity IS its content hash, and each document can reference its parent by hash:
Copy file name to clipboardExpand all lines: docs/design-decisions.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# Design Decisions
2
2
3
-
This document records key design decisions made during the Codex format specification development.
3
+
This document records key design decisions made during the CDX format specification development.
4
4
5
5
## DD-001: ZIP Container Format
6
6
@@ -559,7 +559,7 @@ This section captures key strategic insights from early design discussions that
559
559
**Build Order**:
560
560
1.**cdx-core** (Rust library) — Foundation everything else builds on
561
561
2.**cdx-cli** — Dogfoods the core library, essential for tooling development
562
-
3.**Pandoc writer** — Markdown → Codex (the academia unlock)
562
+
3.**Pandoc writer** — Markdown → CDX (the academia unlock)
563
563
4.**Web viewer** — cdx-core compiled to WASM (zero-install demonstration)
564
564
565
565
**Why Pandoc**: Academics don't adopt new editors, they adopt new export targets. A Pandoc writer fits existing workflows with zero friction for authors.
Copy file name to clipboardExpand all lines: examples/collaboration-document/metadata/dublin-core.json
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@
7
7
"description": "A demonstration of collaboration extension features including comments, suggestions, reactions, and tracked changes with multiple authors.",
{ "type": "text", "value": "Figure: Codex document architecture showing the relationship between content, presentation, and metadata layers." }
610
+
{ "type": "text", "value": "Figure: CDX document architecture showing the relationship between content, presentation, and metadata layers." }
611
611
]
612
612
}
613
613
]
@@ -624,8 +624,8 @@
624
624
"type": "barcode",
625
625
"id": "qr-demo",
626
626
"format": "qr",
627
-
"data": "https://codex.document/spec",
628
-
"alt": "QR code linking to Codex specification",
627
+
"data": "https://cdx.dev/spec",
628
+
"alt": "QR code linking to CDX specification",
629
629
"errorCorrection": "M",
630
630
"size": 150
631
631
},
@@ -701,7 +701,7 @@
701
701
"signer": {
702
702
"name": "Jane Smith",
703
703
"title": "Technical Lead",
704
-
"organization": "Codex Foundation",
704
+
"organization": "CDX Foundation",
705
705
"email": "jane.smith@example.com"
706
706
},
707
707
"timestamp": "2025-01-28T14:00:00Z",
@@ -905,7 +905,7 @@
905
905
"type": "paragraph",
906
906
"id": "conclusion",
907
907
"children": [
908
-
{ "type": "text", "value": "This document demonstrates all block types defined in the Codex content schema. Each block type serves a specific semantic purpose, enabling reliable machine processing and consistent rendering across implementations." }
908
+
{ "type": "text", "value": "This document demonstrates all block types defined in the CDX content schema. Each block type serves a specific semantic purpose, enabling reliable machine processing and consistent rendering across implementations." }
0 commit comments