Versions Compared

Old Version 14

changes.mady.by.user Allana Cameron

Saved on

compared with

New Version 15

changes.mady.by.user Allana Cameron

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The interoperability specifications will follow semantic versioning, using a three-part version number and release type tag (e.g., v0.1.0 DFT, v1.1.1 TI, etc.,).

Image Modified

Major:

  • Increments every time a breaking change is made.
  • Indicated by increasing the Major number.

Minor:

  • Increments every time new non-breaking changes are made (i.e., changes that create new capabilities, but do not render existing implementations to be non-conformant.
  • Indicated by increasing the Minor number.
  • Resets to 0 each time the Major version changes.

Patch:

  • Non-breaking changes (e.g., corrections).
  • Indicated by increasing the Patch number.
  • Resets to 0 each time the Minor version changes.

Release Tag:

  • Draft (DFT)
  • Trial Implementation (TI)
  • Final

IO Specification Publication Process Flow

...

Click on the image to view in full size.

IO Specification Publication Process Roles

...

RoleDescription
IO Change Control BoardThe Interoperability Change Control Board (CCB) will manage the evolution of the interoperability specifications, deciding on the priorities and content for upcoming releases, managing the backlog and roadmap milestones. The CCB will consist of Interoperability management , subject matter experts and representatives from the Operational and Strategic Governance bodies.
IO Team
Jurisdictional Partners
Public Stakeholders
Operational Governance
Strategic Governance

IO Specification Publication Process Example

...

The following table provides an example scenario of a specification flowing through the Interoperability Publication Process from the initial Draft through to its' Final release.

DraftTIFinalDescription
0.1.0 DFT

Draft releases: First release
0.2.0 - 0.3.0 DFT

Draft releases: Specifications will evolve through multiple Draft versions, which will be available for open public review and may be validated in prototyping events (e.g., Projectathon) to assist in the stability of the specifications and ability to transition to Trial Implementation.

1.0.0 TI
Trial Implementation: First Major release
Specifications may be validated in prototyping events (e.g., Projectathon). Input from jurisdictions and other stakeholders (e.g., vendors, PCHO's), the backlog & roadmap will inform future releases. If additional corrections and/or enhancements are required, the cycle will begin again in Draft.
1.0.1 DFT

Draft release: A correction is identified as a required change to the v1.0.0 TI release.
Note: for patch corrections (e.g. typos, description updates), the specification may not go into open review.

1.0.1 TI
Update to the Trial Implementation release: correction update included.
v1.0.1 released to the public and implemented by the market.
1.1.0 - 1.11.0 DFT

Draft releases: Including new development towards the next Trial Implementation (i.e., IO Program continues to plan and develop backlog and roadmap items.)

1.11.0 TI
Trial Implementation: Minor update (i.e., includes enhancements developed and tested in Draft versions 0.5.0 - 0.11.0). Note: v1.1.0 may supersede 1.0.1.
1.12.0 DFT

Draft: First draft of a new Minor release 
1.13.0 - 1.15.0
DFT

Draft: Subsequent drafts in preparation for the next Trial Implementation Major release
Specifications will evolve through multiple Draft versions, which will be available for open public review and may be validated in prototyping events (e.g., Projectathon) to assist in the stability of the specifications and ability to transition to the next Trial Implementation release.

2.0.0 TI

Trial Implementation: Second TI release.
Note v2.0.0 TI may co-exist with v1.1.0 TI, depending on market adoption of v1.1.0 TI.
Input from governance, jurisdictions and other stakeholders (e.g., implementers, PCHO's), the backlog & roadmap will inform future releases.

At such time where no further changes are required, the TI release will be deemed ready to transition to the Final version. Until such time, the cycle of Draft - Trial Implementation releases will continue.



Release 1 FinalFinal release: v1.0 Final is based on v2.0.0 TI
Specifications deemed as Final are ready for implementers to use for compliance / certification. The Final version is not intended to change.
Note: For newly emerging capabilities / features, the specification cycle would begin again with a Draft version.