Fix stale parser evaluation results - #236
Draft
jeswr wants to merge 3 commits into
Draft
Conversation
jeswr
changed the title
9 tasks
Collaborator
|
Thanks for this. Sorry for the late comment. Feel free to mark it ready for review. |
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
2 participants
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.
Closes #234.
Closes #237.
Updates the active parser evaluation results currently blocking rdfjs/N3.js#640:
no-last-nlpath1path2numbersequals1equals2trailing-semicolonThe expected IRIs now use the current
w3c-cg.github.ioaction-document base. The machine-localfile:/home/.../numbers.n3#isvalue is replaced by the same published action base. The numeric expectations preserve the lexical forms from the input instead of canonicalizing them.Validation with rubensworks/rdf-test-suite.js#143 and the rdfjs/N3.js dependency stack: