W3C home > Mailing lists > Public > public-linked-json@w3.org > March 2018

Re: edge attributes in JSON-LD

From: james anderson <james@dydra.com>
Date: Sat, 31 Mar 2018 17:14:24 +0000
Message-ID: <010201627d0d933c-dba5b03c-e1ac-4e77-bddd-82facbfd963f-000000@eu-west-1.amazonses.com>
To: Linked JSON <public-linked-json@w3.org>

> On 2018-03-31, at 17:00, Sandro Hawke <sandro@hawke.org> wrote:
> 
> 
> 
> On March 31, 2018 2:59:15 AM EDT, Ivan Herman <ivan@w3.org> wrote:
>> Sandro, I do not have a problem with the quad/named-graph approach at
>> all, and JSON-LD is o.k. with it. But the original request was on
>> setting attributes to edges, which is a different ballgame…
>> 
> 
> Forgive my ignorance, but what's the difference between stating an attribute of an edge and a stating a property+value of a single-triple graph?   Aren't attributes and properties the same thing?  Aren't edges the same as graph arcs, which can be written down as spo triples?
> 
> I can imagine one formal difference which might arise in the case of duplicate or mutable edges, but actually the RDF named graph model handles that in the edge-attribute style (not the mathematical graph style), so again I'm not seeing a difference except that RDF puts the attribute on a set of edges instead of a single edge.  If you choose to only use singletons, I think it's the same.
> 
> What am I missing?

fernandez, hogan, &co go through the reasons to do this, the various approaches and some notion of the space requirements for wikidata used cases here:

    http://aidanhogan.com/docs/reification-wikidata-rdf-sparql.pdf




---
james anderson | james@dydra.com | http://dydra.com
Received on Saturday, 31 March 2018 17:14:52 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:18:51 UTC