On 14/05/2020 19:06, Chris Tomlinson wrote:
Hi Andy,
I want to validate a named graph in the context of the union graph. I don’t want to
validate the union graph. The union graph has information in it such as the ontology
which defines subClass and subProperty relations needed to
Hello Andy,
I have standalone code using validator.validate(Shapes, Graph, Node) where the
graph is a merge of the target graph, e.g., P707, and the ontology graph. This
works fine to validate examples like P707 generating sh:results just for
references to P705 which is not otherwise included
Hi Andy,
Thanks very much for the shacl guidance. The use of sh:targetSubjectsOf is
quite helpful. I replaced the bdo:personName w/ bdo:isRoot which must be
present on any Entity resource so that if a Work or Place or other entity is
checked it will fail if it isn’t a bdo:Person.
This still
Thank you very much, very helpful.
One final question. When you say a FILTER (such as FILTER
{!sameTerm(a,b)}) removes certain solutions in a SELECT query, does that
mean it removes rows that do not pass the FILTER? It does not try and
do anything clever about removing individual values within
Steve,
> On 14 May 2020, at 12:53, Steve Vestal wrote:
>
> Thank you very much, very helpful.
>
> One final question. When you say a FILTER (such as FILTER
> {!sameTerm(a,b)}) removes certain solutions in a SELECT query, does that
> mean it removes rows that do not pass the FILTER? It does
?graph names the graph to be validated.
?graph can be a URI of a named graph in the dataset
or ?graph=default for the default graph (note: this is the storage
default graph, not the union default graph)
or ?graph=union for the union of all named graphs which is what I think
you're asking
Hi Andy,
I want to validate a named graph in the context of the union graph. I don’t
want to validate the union graph. The union graph has information in it such as
the ontology which defines subClass and subProperty relations needed to
successfully validate a target graph such as
