Repository navigation
chore: bump the validator to oold 2.0.0 - #16
Merged
Merged
Conversation
0.18.1 vendored no meta-schema newer than 1.0.0-rc.3, so this corpus presented itself as the OO-LD reference collection while none of the document rules added since applied to it.
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
1 participant
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.
OOLD_PY_VERSIONwas0.18.1, a pre-1.0 validator whose newest vendored meta-schema is1.0.0-rc.3. This repository presented itself as the OO-LD reference corpus while none of the document rules added in rc.4 and rc.5 applied to it, including the root@contextrequirement.oold2.0.0 vendors through1.0.0-rc.5.Nothing in the corpus had to change: all module schemas already carry a root
@context.make validatepasses, andmake checkis unaffected.