- From: Souripriya Das <souripriya.das@oracle.com>
- Date: Thu, 8 Aug 2024 11:15:08 +0000
- To: "ddooss@wp.pl" <ddooss@wp.pl>, RDF-star WG <public-rdf-star-wg@w3.org>
- Message-ID: <CY5PR10MB607147C5619A13D05ECB9608FAB92@CY5PR10MB6071.namprd10.prod.outlook.com>
Hi Dominik, >I agree that the approach "one PG edge -> one RDF triple" appears to be more natural and intuitive. It is easier to grasp and implement compared to mapping one LPG edge to multiple RDF triples. > However, I am not in favor of the concept of introducing IDs. This assumes that the graph database has explicitly implemented identifiers, which is not true for all implementations. To the best of my knowledge, no PG standard enforces the use of such identifiers. I agree that edge-IDs are not required in PG because those are not used as endpoints of other edges. There are other ways of arriving at an an edge to add annotations to it or retrieve annotations from it. In RDF1.2, however, triples can be used as endpoints (i.e., subject or object of other triples) and hence we need IDs for them. That is why I used edge-ID for the PG edge in my example to make it easier to illustrate its conversion to RDF1.2. Thanks, Souri. ________________________________ From: ddooss@wp.pl <ddooss@wp.pl> Sent: Wednesday, August 7, 2024 4:36 PM To: Souripriya Das <souripriya.das@oracle.com>; RDF-star WG <public-rdf-star-wg@w3.org> Subject: [External] : Re: one RDF1.2 "stated" 4-tuple per LPG edge Hi Souri, I agree that the approach "one PG edge -> one RDF triple" appears to be more natural and intuitive. It is easier to grasp and implement compared to mapping one LPG edge to multiple RDF triples. However, I am not in favor of the concept of introducing IDs. This assumes that the graph database has explicitly implemented identifiers, which is not true for all implementations. To the best of my knowledge, no PG standard enforces the use of such identifiers. Best, Dominik Dnia 07 sierpnia 2024 19:24 Souripriya Das <souripriya.das@oracle.com> napisał(a): Sorry, I was using a custom notation just to communicate the idea. So, by (s) -[id:p]-> (o), I meant an edge with - s and o as the source and destination, respectively - id as its (unique) edge-id and - p as its edge-type (or label). ________________________________ From: ddooss@wp.pl <ddooss@wp.pl> Sent: Wednesday, August 7, 2024 12:22 PM To: Souripriya Das <souripriya.das@oracle.com>; RDF-star WG <public-rdf-star-wg@w3.org> Subject: [External] : Re: one RDF1.2 "stated" 4-tuple per LPG edge Hi Souri, Souripriya Das <souripriya.das@oracle.com>: LPG edge: (s) -[id:p]-> (o) A little explanation. What does the notation `id:p` mean in PG? Did you mean (s)-[p:p { "id": p }]->(o) (i.e. in the schema (s)-[p :p { "id" STRING }]->(o)) in GQL and related languages, e.g. Cypher? Or maybe your notation means something else? Best, Dominik
Received on Thursday, 8 August 2024 11:15:17 UTC