Thank you, Holger. I place the triple into the ontology and it is working
as expected.
The explanation of the technical background makes sense. We will avoid
placing shape-related triples in the data graphs.
Best,
Hamid
On Wednesday, February 14, 2024 at 2:33:48 AM UTC-8 Holger Knublauch
Hi Hamid,
where did you place the sh:deactivated triple? It should go into an Ontology,
not another asset collection such as Taxonomy. I have just tried it and the
deactivation seems to work. You are right about the change to bypass the SPARQL
engine for 7.8 but I checked the code that it will
Hi Holger,
I tried inserting the triple, but it did not deactivate the shape. Do you
know any other workaround?
BTW. I see this comment on that shape, not sure if it matters here:
"As of TopBraid 7.8, the validation engine will bypass the SPARQL query and
use a native, optimized query
I believe it should disappear when you add a triple
teamworkconstraints:MissingLabelConstraint sh:deactivated true .
HTH
Holger
> On 9 Feb 2024, at 8:44 pm, Hamid Abdirad wrote:
>
> Hello,
> AFAIK, EDG requires a rdfs:label for named nodes and raises the following
> violation when it is
Hello,
AFAIK, EDG requires a rdfs:label for named nodes and raises the following
violation when it is not available:
Missing label
Suggestion: Generate a label for
My question:
(1) Is it possible to deactivate this constraint for select collections?
EDG Version: 7.8.0
It looks like this
