OSI Specification Version Change

[khush-bhatia]

OSI Specification Version Change: 1.0 to 0.1.1

Announcement

We are updating the published OSI specification version from 1.0 to 0.1.1, effective March 6th.

Why the Change

When we initially published the OSI specification, we assigned it version 1.0. After further consideration, we believe this does not accurately reflect the maturity and intent of the specification at this stage.

The specification was published recently to establish a starting point, a foundation from which to iterate and improve. Assigning it version 1.0 implies a level of stability and completeness that does not match our current goals. We would like the freedom to evolve the spec incrementally without the expectation that comes with a 1.x release.

We are committed to a deliberate path toward a stable 1.0 release and we will publish a roadmap document after alignment within the steering committee.

Versioning Strategy Going Forward

We are adopting Semantic Versioning with the following approach:

Version Range	Meaning
0.x.y	Pre-stable. The spec is actively being developed. Minor and patch versions may include breaking changes as we iterate toward stability.
1.0.0	The first stable release. At this point, the spec will be considered production-ready and we will follow strict semver rules.
Major versions (2.0, 3.0, ...)	Reserved for breaking changes after the spec reaches stability.

During the 0.x phase:

• Minor version bumps (0.1.0 → 0.2.0) may contain breaking changes.
• Patch version bumps (0.1.1 → 0.1.2) will be reserved for corrections, clarifications, and non-breaking fixes.

We will document all changes in a changelog accompanying each release.

Impact

Given that the specification was published only recently, we do not anticipate significant impact from this change. There are no known production implementations that depend on the 1.0 designation.

If you have begun work based on the 1.0 version of the spec:

• The content of the specification has not changed. Only the version number is being updated.
• No migration or code changes should be necessary.
• Future references should use version 0.1.0.

What This Means for Contributors and Consumers

For contributors: This change gives us room to iterate more freely. Proposals for changes to the spec no longer carry the weight of modifying a "stable" release. We encourage feedback and contributions as we work toward a true 1.0.

For consumers: Treat the spec as a draft that is directionally correct but subject to refinement. Pin to a specific version if stability matters to your implementation, and watch the repository for release notes.

Next Steps

1. The specification in the GitHub repository will be updated to reflect version 0.1.1.
2. All references to version 1.0 in documentation and metadata will be corrected.
3. A CHANGELOG will be introduced to track all future changes.

We appreciate your understanding as we put the spec on a versioning path that better supports its long-term evolution. If you have questions or concerns, please open a discussion in the repository.