- From: Gregory Williams <greg@evilfunhouse.com>
- Date: Thu, 26 Jan 2023 07:55:49 -0800
- To: Souripriya Das <souripriya.das@oracle.com>
- Cc: RDF-star WG <public-rdf-star-wg@w3.org>
Received on Thursday, 26 January 2023 15:56:08 UTC
> On Jan 26, 2023, at 6:06 AM, Souripriya Das <souripriya.das@oracle.com> wrote: > > Initial Data (no shortcuts, to avoid hiding important details): > ------------------------------------------------------------------------------ > :Bush :servedAs :President . > << :Bush :servedAs :President >> :index 43 . > :Obama :servedAs :President . > << :Obama :servedAs :President >> :index 44 . > :Trump :servedAs :President . > << :Trump :servedAs :President >> :index 45 . > :Biden :servedAs :President . > << :Biden :servedAs :President >> :index 46 . … > Let's say that in 2024 Trump wins again. How will the data get represented in RDF-star? Since RDF-star, like RDF, has "no duplicate triples" constraint, the data creator has to extend the schema to introduce a new structure that involves a new property, :occurrenceOf. Since the above query was written without expecting the new structure, it has to be modified as well. Souri – I’m not sure I understand the issue here. Won’t the original query work just fine if the input data contains an extra index value? << :Trump :servedAs :President >> :index 45, 47 . => :Bush :Obama :Trump :Biden :Trump Thanks, Greg
Received on Thursday, 26 January 2023 15:56:08 UTC