Rename "scope" to "release_status" #104
Merged
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.
and "model_scope" to "scope".
For a long time, fairgraph has been remapping the openMINDS "scope" property to "model_scope", mainly because fairgraph already used the keyword "scope", which maps to the term "stage" in the KG Core API.
For openMINDS compatibility, and because "release_status" is more meaningful from a user perspective (the possible values are "released", "in progress" and "any"), this PR renames the keyword.
For user-facing methods like
list(), we retain "scope" as a deprecated alias for "release status", to ease the transition."model_scope" may still be used as an alias for "scope" in
ModelandValidationTest, and the use of this alias is recommended as long as "scope" (in the release_status sense) is only deprecated, and not removed entirely.