introduce semantic versioning and update schema to latest json schema draft #41
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
|
Thanks for researching this! |
MakisH
reviewed
Aug 6, 2025
Co-authored-by: Gerasimos Chourdakis <[email protected]>
MakisH
approved these changes
Sep 4, 2025
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.
After more research, I now believe that the most common way to introduce versioning to a schema is by defining a corresponding
$id. It is possible, but not mandatory, to store the actual schema files of different versions at the URI's specified by the$id.The choice of using the
$idprefixhttps://schemas.precice.org/adapter-config/is arbitrary, feel free to adjust it.closes #37