Governance

Principles

The 28x standard is maintained according to principles of:

  • Clarity: Changes must improve precision or remove ambiguity
  • Stability: Version increments are reserved for substantive changes
  • Openness: The standard remains free to use, modify, and implement
  • Neutrality: The standard does not encode cultural, religious, or ideological preferences

Versioning

The standard follows semantic versioning (vMAJOR.MINOR.PATCH):

  • Major version: Changes that break backward compatibility or fundamentally alter the specification
  • Minor version: Additions that extend the standard without breaking existing implementations
  • Patch version: Corrections, clarifications, or typographical fixes

Current version: v0.1

Stewardship

The 28x standard is maintained as an open specification. Decisions about changes, extensions, and clarifications are made through:

  1. Documentation: All changes are documented in version history
  2. Rationale: Changes must be justified in terms of clarity, necessity, or correctness
  3. Review: Proposals are open to review before adoption

Openness

This standard is published for public use. Anyone may:

  • Implement the standard in software or systems
  • Reference the standard in documentation or research
  • Propose modifications or extensions
  • Create derivative works

Attribution to the standard is appreciated but not required for use.

Future Development

Potential areas for future versions:

  • Detailed conversion algorithms between 28x and other calendars
  • Week definitions and naming conventions
  • Regional or cultural naming variations
  • Integration protocols with existing temporal standards

These extensions will be developed with the same principles: clarity over completeness, stability over novelty.

Contributions

While the standard is open, contributions and proposals should align with the core principles: regularity, computational clarity, and neutrality. Proposals that introduce irregularity, cultural specificity, or unnecessary complexity will not be accepted.

Longevity

This standard is designed for long-term stability. Changes will be conservative and well-justified. The goal is to create a temporal reference that remains reliable and useful for decades, not to evolve constantly.

If you have questions, proposals, or need clarification on the standard, the specification itself serves as the primary reference. This site will be updated as the standard evolves, maintaining backward compatibility wherever possible.