Re: Consolidating triple/edges -- named occurrence version

> Multiple edges with the same label are handled as multiple occurrences - the predicate URI of the RDF triple is thought as a conceptual relationship - with multiple sets of annotations.
 
What does it mean for two occurrences to be labeled with the same IRI/BNode? This would certainly invalidate using r.id <http://r.id/> to identify just a single occurrence. Would this directly relate these occurrences with each other as if they share a graph?

Perhaps I mis-understand this point; I get that << :r | :s :p :o >> can be used in multiple triples to identify the same occurrence and that << :r1 | :s :p :o >> identifies a separate occurrence. How would << :r | :s :p :o >> and << :r | :s1 :p1 :o1 >> relate to each other? Why should this be considered valid? Can :r be thought to have some meaning aside from being an identifier of a triple occurrence?

> So if the application is given <http://example/occ1>, how does it determine whether URI is named occurrence and if so, how does it find the triple subject/predicate/object?
> 
> Scanning all triples to find named occurrences and looking at the id of a named occurrence is expensive.
> 
> Expecting an addition function x -> triple just for occurrences is a big step.
> 
> In the triple-term version has rdf:occurrenceOf so there is a triple to maps the blank node / URI to the 3-tuple of s,p,o that had the effect of OT.

Sorry, confused. It’s not clear that  <http://example/occ1> is associated with a single occurrence, multiple occurrences, or possibly no occurrence. Is there still some role for rdf:occurrenceOf?

Gregg Kellogg
gregg@greggkellogg.net

> 
>    Andy
> 
> [1] https://github.com/w3c/rdf-star-wg/wiki/Semantics:-Andy's-proposal#semantics
> 
> [2] Apache CommonsRDF : https://commons.apache.org/proper/commons-rdf/
>