Re: Naming triples

I live happily without RDF named graphs by constructing provenance networks which are much richer than RDF graphs.  And they are optimizable.  I claim we should put the optimization  burden on the SPARQL query tool before we complicate RDF - like named graphs did and like the RDF-star proposal threatens to do.

Please consider quads, my friends.

Just add a new SPARQL term called EDGE.  It would be completely synonymous with GRAPH.

The fourth member of the quad is a terrible thing to waste.

[cid:0b1525d3-d2c3-4f4c-a91b-68d670b1ab6a]


________________________________
From: Peterson, Eric L. [US-US] <Eric.L.Peterson@leidos.com>
Sent: Monday, June 17, 2024 3:26 PM
To: public-rdf-star-wg@w3.org <public-rdf-star-wg@w3.org>
Subject: Re: Naming triples

I have been naming my triples for many years.

I just use the fourth member of the quad for the triple name (URI):

[cid:df79a4e1-e667-4995-b138-6d22e993d233]
________________________________
From: Peterson, Eric L. [US-US] <Eric.L.Peterson@leidos.com>
Sent: Monday, June 17, 2024 3:04 PM
To: public-rdf-star-wg@w3.org <public-rdf-star-wg@w3.org>
Subject: Naming triples

Hi folks;

Thanks for working on getting us something better than triple reification for edge metadata!

Would I be justified in being very disappointed in a spec that didn't allow me to name triple terms?

For simplicity below, I didn't model this example the way I would at work.  But look at all the notational duplication.  Can we have a spec that allows that naming of triple terms and the subsequent referencing of the name in place of a triple term?

I'm very new to RDF-star/SPARQL-star.  Please forgive me if I've missed some way around this issue.

<<_:Person__1 ex :hasPhoneNumber _:11111111111>> pr:clearance  _:UNCLASSIFIED .
<<_:Person__1 ex :hasPhoneNumber _:11111111111>> pr:source  _:DHS .
<<_:Person__1 ex :hasPhoneNumber _:11111111111>> pr:likelihood 0.8
<<_:Person__1 ex :hasPhoneNumber _:11111111111>> pr:dataSet _:someDataSet .
<<_:Person__1 ex :hasPhoneNumber _:11111111111>> pr:sourceRecord _:PERSON .
<<_:Person__1 ex :hasPhoneNumber _:11111111111>> pr:sourceRecordID 329 .


Thanks!

-Eric