Event Author — .chron

Build a portable event file without writing code. Fill in the fields and download your .chron file — ready to share, archive, or load into any OpenChronology-compatible tool.

schemas.openchronology.org/v0.3/

↑ Import .chron prefill form

▾

📂

Drop a .chron file to edit it

or click to browse · .chron or .json

01 Event Identity required

Event Type * iThe functional role of this record. event is the default — a point or span in time. era names a period that contains other events. marker is a reference annotation or milestone. §6 spec ↗

event

era

marker

Title *

Description optional iChoose a format — plain for plain text, markdown for bold/italic/links, html for full markup. The format is stored alongside the text so renderers know how to display it.

Display Date iA human-readable date string shown to readers — any format, any calendar system. Separate from the machine-readable Start Value. E.g. "25 Halimath, SR 1418" or "XIV Kalends November".

Any format — purely for display. Machine date goes in §02.

Author

License

Canonical URL iThe permanent home of this .chron file once published. Other events use this URL in their relations to reference yours. Leave blank if you haven't hosted it yet. §3.1 spec ↗

Tags iFree-form keywords used for filtering and discovery. Stored as lowercase kebab-case in the file. No limit on count.

Press Enter or comma to add.

02 Temporal required spec §6.3 ↗

Universe iThe timeline reality this event belongs to. real is the default for historical/factual events. Choose custom to define a fictional or alternate universe (Middle-earth, Star Wars, etc.). §5 spec ↗

Calendar iThe calendar system used for start/end values. Built-in calendars (Gregorian, Julian, Islamic, Hebrew) need no definition. Choose custom for fictional or non-standard calendars. §4 spec ↗

Start Value * iThe machine-readable date. Use ISO 8601 for Gregorian (YYYY-MM-DD). For custom calendars, any string your parser understands. This is separate from Display Date, which is for human readers.

ISO 8601 for Gregorian. Any string for custom calendars.

Precision iday/month/year — known to that calendar unit. decade/century/millennium — coarser calendar windows. circa — approximate; pair with an uncertainty block. epoch — geological or cosmological scale. millisecond–second–minute–hour — sub-day precision. custom — defined by the calendar's own unit system. §6.3 ↗

This event spans a range (add end date)

End Value

End Precision

03 Spatial optional

▾

Celestial Body

Custom Region Name

04 Significance optional

▾

Significance Value iA 0–1000 integer that drives Level of Detail rendering — analogous to how maps show country names when zoomed out and street names when zoomed in. Events with higher values appear at broader zoom levels. §6.8 spec ↗

500

Higher values surface at broader zoom. Pair with scopes below for full LOD control.
e.g. Big Bang ~1000 @ universal scope · Moon landing ~900 @ global scope · Regional election ~400 @ national scope · City council vote ~200 @ local scope.

Temporal Scope iThe time scale this event is relevant at. Controls which zoom level a renderer shows it. epochal = billions of years (Big Bang); daily = a single day. §6.8.1 ↗

Geographic Scope iThe geographic scale of this event's relevance. global = Earth-wide; continental down to street for progressively finer granularity. Used alongside significance value for map zoom filtering. §6.8.2 ↗

05 Sources optional

▾

External citations — Wikipedia, official pages, academic papers. These belong here, not in the Relations block.

live preview untitled.chron

Fill in the form to see your .chron file…