Skip to content

3.1 - Can any string can be a term? #231

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.

Sign up for GitHub

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

Jump to bottom
Closed
azaroth42 opened this issue Sep 16, 2019 · 1 comment
Closed

3.1 - Can any string can be a term? #231

azaroth42 opened this issue Sep 16, 2019 · 1 comment
Labels
spec:editorial

Comments

@azaroth42
Copy link
Contributor

azaroth42 commented Sep 16, 2019 •
edited
Loading

Terms are case sensitive and any valid string that is not a reserved JSON-LD keyword can be used as a term.

I don't believe this is still exactly true. For example IRIs cannot be used as a term other than for themselves, and strings with a : in them are now treated as prefix:suffix. And what did we end up doing about error vs optional warning for terms beginning with '@'? Also ... empty string is a valid string, but can't always be used as a term?
@azaroth42
Copy link
Contributor Author

Should reference 9.1 - https://www.w3.org/TR/json-ld11/#terms

@azaroth42 azaroth42 mentioned this issue Sep 20, 2019
Closed
gkellogg added a commit that referenced this issue Sep 24, 2019
@gkellogg
Improve requirements of terms.
ecfe226 
Fixes #231.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
spec:editorial
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@azaroth42