W3C home > Mailing lists > Public > public-linked-json@w3.org > August 2011

Re: Issues with disjoint graph modelling

From: Gregg Kellogg <gregg@kellogg-assoc.com>
Date: Tue, 2 Aug 2011 20:34:04 -0400
To: Alexandre Passant <alex@seevl.net>
CC: "public-linked-json@w3.org" <public-linked-json@w3.org>
Message-ID: <EB462E09-F5D1-4034-BE0C-D51F6A4A7DCD@kellogg-assoc.com>

Sent from my iPad

On Jul 31, 2011, at 5:09 AM, "Alexandre Passant" <alex@seevl.net> wrote:

> Hi,
> 
> I like the idea of disjoint graphs exposed in 9.2. and that's definitely useful.
> Yet, I'm not convinced by the use of @ to express this.
> 
> {
>  "@":
>  [
>    {
>      "@": "http://example.org/people#john",
>      "a": "foaf:Person"
>    },
>    {
>      "@": "http://example.org/people#jane",
>      "a": "foaf:Person"
>    }
>  ]
> }
> 
> It's IMO confusing and we should come up with another term, such as
> @data (and allowing override - cf my previous e-mail) for the first
> one - as is not a subject per-se, but just a way to encapsulate the
> others.

Be it "@": [] or "@subject": [], much of these forms fall out of the general processing rules, such that every call to process an entity return a value that can be used as a subject. Otherwise, we end up adding special cases, where.none are necessary.

> Also, regarding the alternative form:
> 
> [
>  {
>    "@": "http://example.org/people#john",
>    "a": "foaf:Person"
>  },
>  {
>    "@": "http://example.org/people#jane",
>    "a": "foaf:Person"
>  }
> ]
> 
> This one cannot accomodate context (you cannot add a @context:{}
> inside the [] since it expects {} values). It may be a problem if
> someone uses it and then realise that context must be added - this
> requires to refactor the JSON and it will break the existing model. I
> do not think it brings much compared to the first one, and IMO could
> be dropped.

The second form should be allowed, but as you point out, the first form my be required to add an @context.

I favor regularity in the processing rules. @data could be handled as a pseudonym for @subject using the term mechanism, but I would resist adding specific processing instructions for it.

> Alex.
> 
> NB: If these issues should be raised on github rather than the ML, let
> me know. I'm also happy to contribute to some of the fixes / editing.

This is a great forum, and can also be added as a telecom subject.

Any help with the docs is, of course, appreciated.

Gregg

> -- 
> Dr. Alexandre Passant - @terraces
> Founder, CEO - seevl.net - @seevl
> Reinventing Music Discovery
> 
Received on Wednesday, 3 August 2011 00:32:49 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 16:25:35 GMT