W3C home > Mailing lists > Public > public-data-shapes-wg@w3.org > March 2015

Re: shapes-ISSUE-30 (shape-and-data-graphs): Are shapes and data in the same graph? [SHACL Spec]

From: Richard Cyganiak <richard@cyganiak.de>
Date: Sun, 29 Mar 2015 23:49:54 +0100
Message-Id: <B8225EFB-9EF6-481E-9059-D52C165FF8CB@cyganiak.de>
Cc: "public-data-shapes-wg@w3.org" <public-data-shapes-wg@w3.org>
To: "kcoyle@kcoyle.net" <kcoyle@kcoyle.net>
Karen,

> On 29 Mar 2015, at 16:34, Karen Coyle <kcoyle@kcoyle.net> wrote:
> 
>>> In my current design, templates can set a flag to indicate whether they also need to see the graph containing the constraint definitions in their WHERE clause. This means that most operations can be very fast, and only access the query graph. Other operations may need to see the constraints graph too, and these may be slower.
>> 
>> Wouldn’t this be better solved with named graphs? Have the data under validation in the default graph, and pass in a variable like ?constraintGraphName that could be used like this to access the constraint graph:
>> 
>>     GRAPH ?constraintGraphName { … }
>> 
>> Implementations could detect whether ?constraintGraphName is actually used in the template, and optimise the case where it’s not.
> 
> This though assumes that you have control over the instance data, which is not always the case. So although this may work for some applications, others will be operating over data created by third parties who have their own data model. I mention this just so we can keep in mind that we have both situations to address.

I don't follow. Why does the described design require that I have control of the instance data, and why wouldn't it work with third-party data?

Richard
Received on Sunday, 29 March 2015 22:50:19 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:30:18 UTC