-
Notifications
You must be signed in to change notification settings - Fork 157
Are @subject and @iri redundant? #15
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
Comments
This issue was originally raised by Gregg: http://lists.w3.org/Archives/Public/public-linked-json/2011Jul/0060.html I think in this case it makes sense to keep both @subject and @iri even though @subject is just syntactic sugar. So for me it would be fine to close this issue.. let's see what Gregg thinks about it - I've CCed him. P.S.: For me this issue is quite different from the @type/@datatype issue (#31). I wouldn't like to treat them the same way.
|
Updated specs in 44c7dde. |
In the spec, @subject is used to denote the subject of an item, and @iri is used to denote a value which is an IRI. However, from chaining, the distinction seems to go away. For example, consider the following two graphs:
and
From step 2.6.1 in the spec, the first use of "@subject" ("@" in that version) generates a triple in the same way that step 2.2, for "@iri", does.
We could simplify the spec by either removing "@iri", or replacing "@subject" with "@iri". Of course, using the aliasing mechanism we've discussed, the other could continue to exist as semantic sugar in the default context.
So, @subject works the same as @iri when given in an object of a property, so @iri could be considered redundant
(albeit more understandable at least for @Coerce). The question would be if @iri is sugar for objects with only that key (an no other properties), or if it works just like @subject.
The text was updated successfully, but these errors were encountered: