Skip to content

Conversation

gkellogg
Copy link
Member

to clarify that it describes only IRIs relative to the document base, not the vocabulary mapping.

Add additional explanatory text on relative IRIs to distinguish them from properties, values of @type, or values of properties defined to be vocabulary relative.

Fixes #488.

…ve to the document base, not the **vocabulary mapping**.

Add additional explanatory text on relative IRIs to distinguish them from properties, values of `@type`, or values of properties defined to be vocabulary relative.

Fixes #488.
@azaroth42
Copy link
Contributor

👍

@azaroth42 azaroth42 merged commit 8d8487b into master Feb 5, 2018
@azaroth42 azaroth42 deleted the clarify-iri-resolution branch February 5, 2018 16:40
@kidehen
Copy link

kidehen commented Feb 5, 2018

What does this mean?
Does JSON-LD now support the use of IRIs for identifying the predicate of an RDF Statement, yes or no?

@gkellogg
Copy link
Member Author

gkellogg commented Feb 5, 2018

JSON-LD has always supported IRIs for identifying predicates. The issue is document-relative, vs vocabulary-relative IRIs, which we're going to consider further. So #488 remains open.

@kidehen
Copy link

kidehen commented Feb 5, 2018

Okay, I should be much clearer about the fact that my quest is for the use of "relative HTTP URIs" to identify the predicates of RDF statements when using JSON-LD notation :)

Resolving this is very important. I would like to always provide both RDF-Turtle and JSON-LD examples when producing Semantic Web of Linked Data utility demos etc..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants