I have been testing the 0.4.0 version of the calendar since the end of July, and with minor modifications to relative date syntax, is finally ready for a 1.0.

In accordance with Semantic Versioning, backwards compatibility will be guaranteed until the release of version 2.0 of the calendar, for the people out there (if such a person exists, please let me know) using this calendar.

I have also found that using a standalone number like 3 in the middle of text does not make it *obvious* that *time* is being communicated, thus I have specified that *only* number groups denoting the season may be omitted from both absolute and relative dates.

The 1.0 specifications is as follows; for the most recent version, see the project page here:

# The Clarentine Calendar

Current revision: 1.0.1

This is the formal specification for the Clarentine calendar. This document is a *work is progress*; it will change as feedback is incorporated.

All pronunciations shall follow the rules of Clarentine English Pronunciation (the specification of which will be published later; it’s still a work in progress).

## Section 1: Names and Definitions

- The fundamental unit of time in the Clarentine Calendar is the
*day*. The time of day is defined and notated the same way as in UTC. - This calendar uses the “J2000” epoch. The date 0.1.1 11:58:55.816 (see section 3 for interpretation of this date) is defined as J2000, or 1 January 2000 11:58:55.816 UTC, or 1 January 2000 11:59:27.816 TAI.
- All days, cycles, and seasons shall be named numerically, with the number corresponding to their position. For example:
- Day 1 -> 1st day of the cycle
- Day 11 -> 11th day of the cycle
- cycle 5 -> 5th cycle of the season

## Section 2: Time Divisions

- Time periods are divided into
**divisions**. Divisions are as follows:

Name Plural Composed of Day Days 1 UTC day Cycle Cycles 12 days Season Seasons 12 cycles Examples:

- 42 days = 3 cycles, 6 days
- 1000 days = 6 seasons, 11 cycles, 4 days

## Section 3: Absolute Dates

- Dates consist of three groups of numbers (“number groups”) separated by a full stop:
`.`

- The numbers follow the standard rules of numerical notation.
- From left-to-right, the first group of numbers represent the season, the second the cycle, and the third the day.
- A number group cannot be omitted unless a more significant number group has also been omitted.
- A separator can be omitted if the number group to the left has been omitted as well.
- If less than three number groups are present in the date, the present groups of numbers are assumed to represent the least significant divisions, and omitted numbers are understood to represent the current time for the group’s associated division.
- Only the season may be omitted for the sake of clarity; a standalone number is easily mistook as just another number as opposed to a date.
- Examples:
`4.2`

: Current season, cycle 4, day 2`3.5.6`

: Season 3, cycle 5, day 6`1234.07.08`

: Season 1234, cycle 7, day 8`9.10.11`

: Season 9, cycle 10, day 11`0.12.12`

: Season 0, cycle 12, day 12`0.0.0`

: Invalid date; cycle and day cannot be below 0

## Section 4: Relative Dates

- The rules for notation for relative dates are the same as absolute dates, as laid out in section 3, unless otherwise noted here.
- A relative date is specified by prepending an absolute date with a
`+`

or`-`

sign. - The groups of numbers still correspond to the same divisions, but are denoting the
*relative*time from that of writing. - Positive dates denote the future relative to the current time; negative dates denote the past
- Omitted numbers are assumed to be 0, or the current division of time as represented by that number group.
- Just as absolute dates, only the season number group may be omitted from the date.
- Examples:
`-1.1.1`

: 1 season, 1 cycles, and 1 day in the past`+4.6.12`

: 4 seasons, 6 cycles, and 12 days in the future`+3.2`

: 0 seasons, 3 cycles, and 2 days in the future`+4.1`

: 0 seasons, 4 cycles, and 1 day in the future