The ITxPT Collaborative Community just released a new version of the Technical Specifications, approved by the Executive Board on the 7th of January. The collaboration between the members is the heart of ITxPT, and the most central result is the release of new specification versions, like the current 2.1.1 patch-level update. A patch update has little or no impact on implementation. Read here about the version levels.
Several small improvements
The 2.1.1 update consists of many small improvements that together enhance the readability and usability of the specifications. Through adding details and clarifying certain aspects, the update results in improved interoperability by minimizing the freedom of interpretation. In general, the specification is backward-compatible with 2.1.0, but some updated details might call for adjustments. To read more about how the 2.1.1 version might affect your implementations or products, please refer to the Documentation Center on https://itxpt.org/
You will find the documentation of the changes and impact under Release history.
Feedback from using the specification
The Collaborative Community generated valuable feedback that resulted in the 2.1.1 update. Three main activities created the most input to drive the update:
- The implementation of the specification version 2.1.0
- The use of the specifications in tenders
- The labeling process
Thanks to all change request contributors that enabled the current update. Do not hesitate to use the change request form to submit requests. The requests are essential drivers of improving the specification. Also, thank you to all who reviewed version 2.1.1 before publication.
What is semantic versioning? We have all seen software releases with a series of numbers to show which version it is. But what do the numbers mean, and what information can we get from the change of a single digit? In this post, we will look into semantic version conventions with a focus on the ITxPT specification versions.