Skip to main content

​
Where the Spec Lives

The canonical OMSS specification is maintained in the github.com/omss-spec/omss-spec repository. The spec is versioned by directory. (Beta versions are on a different branch):
  • spec/v1.1/ — OMSS v1.1 (current, status: Final)
  • spec/v1.0/ — OMSS v1.0 (past, status: Final)
  • BETA: spec/v2.0/ — OMSS v2.0 (future, status: Draft)

​
How to Contribute

  1. Read the spec — Familiarize yourself with the current version before proposing changes.
  2. Open a RFC — Describe the problem, ambiguity, or improvement you have in mind.
Please review the Code of Conduct and Contributing Guide before submitting.

​
Versioning and Breaking Changes

OMSS follows Semantic Versioning:
  • PATCH — Clarifications and bug fixes (no behavior change)
  • MINOR — Backward-compatible new features or fields
  • MAJOR — Breaking changes (require a new /vN/ URL prefix)
Deprecated endpoints return Deprecation: true and Sunset: <date> headers. Deprecated features are supported for at least one full major version before removal, with a minimum 6-month announcement period. (This is best-effort; We cannot guarantee this.)

​
Deprecation in v1.1

The following endpoints are sunset in OMSS v1.1 and will be removed in v2:
  • GET /v1/movies/{id}
  • GET /v1/tv/{id}/seasons/{s}/episodes/{e}
  • POST /v1/refresh/{id}
Clients should prepare to migrate once OMSS v2 endpoints are defined.

​
Registry

Implementations can be listed in REGISTRY.md in the main spec repo. To be added, please open an issue with your implementation details. The registry is maintained by the OMSS maintainers and is not a formal endorsement of any implementation.
Thank you for contributing to OMSS! Your feedback and participation help make the standard better for everyone.
Last modified on July 26, 2026