Skip to main content

Specification Versioning

The AXAG specification follows semantic versioning: MAJOR.MINOR.PATCH.

Version Rules​

  • MAJOR — Breaking changes to normative requirements
  • MINOR — New optional fields or conformance requirements
  • PATCH — Clarifications, typo fixes, informative content updates

Annotation Versioning​

Annotations MAY declare the specification version they conform to. The manifest records the generator's version in its own version field, so axag-version is only needed where one page mixes annotations written against different versions:

<button
  axag-version="1.1.0"
  axag-intent="product.search"
  axag-entity="product"
  axag-action-type="read"
>Search</button>

Backward Compatibility​

  • MINOR versions MUST be backward-compatible with the same MAJOR version
  • Deprecated attributes MUST remain valid for at least one MINOR version after deprecation
  • Deprecation MUST be declared via axag-deprecated="true" and axag-deprecated-replacement