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

On tisdag 4 februari 2020 kl. 23:40:58 CET Martynas Jusevičius wrote:
> I don't see how RDF* can stay compatible with RDF:
> [...]

The RDF* data model is an extension of the RDF data model.

Hence, it is compatible with the RDF data model in the sense that everything 
you can do with the RDF data model, you can also do with the RDF* data model.

-Olaf


>     A node may be a URI with optional fragment identifier (URI
> reference, or URIref), a literal, or blank (having no separate form of
> identification). Properties are URI references.
> 
> https://www.w3.org/TR/rdf-concepts/#section-URI-Vocabulary

> 
> On Tue, Feb 4, 2020 at 11:36 PM Holger Knublauch <holger@topquadrant.com> 
wrote:
> > On 5/02/2020 08:15, Jeen Broekstra wrote:
> > 
> > On Wed, Feb 5, 2020 at 9:03 AM Martynas Jusevičius 
<martynas@atomgraph.com> wrote:
> >> I've read Kurt Cagle's post:
> >> https://www.linkedin.com/pulse/state-graph-merger-property-graphs-semanti

> >> c-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.
> > 
> > Yes, the Concise Bounded Description (of resources like city:_Seattle)
> > could include its reified triples.
> > 
> > Holger

Received on Wednesday, 5 February 2020 07:31:49 UTC