The papiNet Standard
papiNet organizes the standard by version, release, and build with particular rules for the types of changes that can be made for each.
papiNet is constantly monitoring the business environment. This results in an evolving standard whereby new business requirements and processes are being incorporated into the standard. We do this by releasing a new 'build' for our current version and release, V2.31, of the standard.
A version is defined to be a major redesign of the standard. We have had only two to date - hence the "V2" portion in our naming convention. A Release is defined to be a major update to a version. We have had 3 to date and one minor release of the third - hence the "31" portion of the V2.31 designation. A 'build' can be viewed as a maintenance update to the current version/release. A new 'build date' is provided with these updates.
Different Releases of the Same Version
papiNet is very careful to only implement changes for a release that do not prevent users from communicating with each other. This means that:
- A user of an earlier release can send their e-business document without modification to a user of a later release.
- A user of a newer release would need to verify that they are not sending a new item to the user of an earlier release. This is possible because items added at a newer release are always optional.
Different Builds of the Same Release
Events sometimes force us to reissue a release. We indicate that the release has been reissued by the version build number that is associated with the root element of the schema. The types of changes that are considered are:
- Adding an enumeration to a list
- Correcting spelling errors in the schema
- Documentation updates
- Changes made for a build are documented in the Build Notes page for the release.
