Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
ADR 0048 proposes a way of supporting multiple versions of the product carbon footprint (PCF) data model over 3.0 API. In effect this would mean splitting the version of the API and the version of the data model.
Because of tight timelines we cannot include this in version 3.0 of the standard yet. We as PACT feel that, because of the added complexity it brings, it needs more reasoning, more reference cases to other architecture and more feedback from software solution providers implementing real-world data exchange.
In order to make future realization of ADR 0048 possible without requring us to wait for a new backwards incompatible version 4.0, we can include ADR 0049: adding a mandatory
specVersionparameter, which is fixed to specVersion=3. This will enable us to introduce a multi-version API as a minor release (3.x) because it will not break backwards compatibility with existing 3.0 APIs.Alternatives are:
pcf.exchange.com/pact/2/...pcf.exchange.com/pact/3/...