How can we deactivate rdfs:label constraint?

[Hamid Abdirad]

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 constraint is in the built-in system collections/imports and I am unable to reliably track it. 

I am experimenting with some large datasets in which we do not really need/have a label for all nodes, so I do not want to make up thousands of triples for labels just to avoid these violations. 

Thank you

[Holger Knublauch]

I believe it should disappear when you add a triple

teamworkconstraints:MissingLabelConstraint sh:deactivated true .

HTH

Holger

--
The topics of this mailing list include TopBraid EDG and related technologies such as SHACL.
To post to this group, send email to topbrai...@googlegroups.com
---
You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to topbraid-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/7e74d93c-dad0-4e3d-a769-2dab50ab3bc4n%40googlegroups.com.

[Hamid Abdirad]

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 instead."

Thank you,

Hamid

[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 perform the sh:deactivated check before executing the native implementation.

As a bit of technical background: SHACL distinguishes between data graphs and shapes graphs. In TopBraid, the shapes graphs are considered to be stored in Ontologies and their owl:imports (esp files). Placing shape-related triples into instance data graphs will usually not have any effect.

Holger

To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/8aae549e-446c-4324-b52e-b45fe7e57f74n%40googlegroups.com.

[Hamid Abdirad]

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