W3C home > Mailing lists > Public > public-rdf-star@w3.org > February 2020

Re: How is RDF* supposed to work with Linked Data?

From: Andy Seaborne <andy@apache.org>
Date: Wed, 5 Feb 2020 11:01:13 +0000
To: public-rdf-star@w3.org
Message-ID: <21ae3bcd-a261-66e1-f667-e9027e9b0959@apache.org>

On 04/02/2020 22:15, Jeen Broekstra wrote:
> On Wed, Feb 5, 2020 at 9:03 AM Martynas Jusevičius 
> <martynas@atomgraph.com <mailto:martynas@atomgraph.com>> wrote:
>     I've read Kurt Cagle's post:
>     https://www.linkedin.com/pulse/state-graph-merger-property-graphs-semantic-kurt-cagle/
>     The reification looks neat. But it seems to me that Linked Data* would
>     be broken.
> I think /breaking/ it is too strong, but you're right that the reified 
> triple itself can not be directly referenced outside the local context. 
> However, it is not unique in that respect, it's somewhat similar to how 
> blank nodes are treated: you can only reference them indirectly (by 
> means of specifying the relations in which they occur).
>     The idea with Linked Data is to follow the links. But <<city:_Seattle
>     city:isConnectedTo city:_SanFranciso>> has no URI, so how should we
>     address it on the web?
> You can't follow a link to the reified statement itself, but you can 
> decompose to get to its constituent parts of course, and follow those 
> links.

And the <<...>> itself behaves more like a literal.  The syntax 
completely describes the triple. Triples don't exist at a place on the 
web, same for literals.

(aside from <<>> being in the subject position).

> Jeen

Received on Wednesday, 5 February 2020 11:01:20 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 5 February 2020 11:01:21 UTC