- From: Peterson, Eric L. [US-US] <Eric.L.Peterson@leidos.com>
- Date: Tue, 18 Jun 2024 14:37:39 +0000
- To: Franconi Enrico <franconi@inf.unibz.it>
- CC: "public-rdf-star-wg@w3.org" <public-rdf-star-wg@w3.org>
- Message-ID: <PH2P110MB085783266E3C90D0C5DA9301D8CEA@PH2P110MB0857.NAMP110.PROD.OUTLOOK.COM>
Thanks Enrico! Can you help me solve the problem of when I want to keep my provenance outside of the semantic store? If I name an rdf:Statement with a URI, I can say things about the edges in my store - in an RDF web page outside of my store or some such. This is actually a real scenario. A few years back, my customer, for space reasons kept their metadata outside of their pre-RDF graph DB super computer. Thanks again for your prompt and helpful reply! -Eric ________________________________ From: Franconi Enrico <franconi@inf.unibz.it> Sent: Tuesday, June 18, 2024 3:52 AM To: Peterson, Eric L. [US-US] <Eric.L.Peterson@leidos.com> Cc: public-rdf-star-wg@w3.org <public-rdf-star-wg@w3.org> Subject: EXTERNAL: Re: Naming triples CAUTION: This email originated from outside of Leidos. Be cautious when clicking or opening content. 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.
Received on Tuesday, 18 June 2024 14:37:54 UTC