-
Notifications
You must be signed in to change notification settings - Fork 35
Prevent keyword alias to be declared as prefix #154
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
5e2043e
prevent keyword aliases to be declared as prefix in term definition
pchampin d650bf4
add test for keyword-alias declared as prefix
pchampin 0b831dd
fixed typo
pchampin c48303d
Rename expand/pr30 to expand/pr33 to avoid conflict with PR #158.
gkellogg e73b87c
Add text to ignore and optionally warn if terms aren't keywords but b…
gkellogg 42092ca
Update spec text, as keyword pattern won't appear with `@prefix`. Als…
gkellogg 68d0782
Ignore non-keyword '@' patterns in IRI Expansion.
gkellogg 57bd226
More tests for non-keyword '@' patterns.
gkellogg c9e9d90
Update HTML versions of test manifests.
gkellogg File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Might want to say "has the form of a keyword", so that
@the-next-keyword
would be rejected too. This is related to another discussion from the F2F, for which we don't yet have an open issue: we want to discourage the use of things that may be keywords in the future (should => must).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Per w3c/json-ld-syntax#16, keyword-like strings MUST be ignored and SHOULD result in a processor warning. I'll add text and tests to ensure they're ignored (with and without
@vocab
), but we can't test for warnings.