On 17 Jun 2024, at 21:04, Peterson, Eric L. [US-US] <Eric.L.Peterson@leidos.com> wrote:
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 .
According to the current proposal, you could write in Turtle concrete syntax:
<<_:b | _:Person__1 ex :hasPhoneNumber _:11111111111>> pr:clearance _:UNCLASSIFIED .
_:b pr:source _:DHS .
_:b pr:likelihood 0.8
_:b pr:dataSet _:someDataSet .
_:b pr:sourceRecord _:PERSON .
_:b pr:sourceRecordID 329 .
Note, though, that you are not naming the triple term, but one of the reifications of the triple term.
—e.