Skip to content

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

Closed
lanthaler opened this issue Aug 24, 2011 · 5 comments
Closed

Are @subject and @iri redundant? #15

lanthaler opened this issue Aug 24, 2011 · 5 comments

Comments

@lanthaler
Copy link
Member

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:

{
  "@subject": "http://greggkellogg.net/foaf#me",
  "foaf:homepage":
  {
    "@iri": "http://greggkellogg.net/"
  }
}

and

{
  "@subject": "http://greggkellogg.net/foaf#me",
  "foaf:homepage":
  {
      "@subject": "http://greggkellogg.net/"
  }
}

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.

@msporny
Copy link
Member

msporny commented Nov 29, 2011

Technically, they are redundant. However, I think that just like @type and @datatype, we should keep the two concepts separate to help people understand what is going on in the markup a bit better.

@lanthaler
Copy link
Member Author

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.

-----Original Message-----
From: Manu Sporny [mailto:reply+i-1477642-
[email protected]]
Sent: Tuesday, November 29, 2011 12:42 PM
To: Markus Lanthaler
Subject: Re: [json-ld.org] Are @subject and @iri redundant? (#15)

Technically, they are redundant. However, I think that just like @type
and @datatype, we should keep the two concepts separate to help people
understand what is going on in the markup a bit better.


Reply to this email directly or view it on GitHub:
#15 (comment)

@lanthaler
Copy link
Member Author

RESOLVED: Use the same keyword for the concepts of @subject and @iri.

RESOLVED: Use the keyword '@id' for the combined concept of @subject and @iri.

Minutes of the 2011-12-13 telecon

@gkellogg
Copy link
Member

Updated specs in 44c7dde.

@msporny
Copy link
Member

msporny commented Jan 22, 2012

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

No branches or pull requests

3 participants