Suppose I have created a SPARQL-based SHACL constraint that prohibits a resource with a certain value for a certain property from being used in certain contexts. A real example of this, from our data, is that concepts with a lifecycle stage of "Deleted" may not be used as the object of the dct:Subject property; attempting to do this in our EVN projects will result in a constraint violation message when the user goes to save the resource.
My question is: Would it be possible to make EVN enforce the SHACL constraint earlier - ideally in real time, so that resources that violate a constraint (like the rule against using deleted concepts) are not even available to the user in the typeahead box? ___ Carl Burnett Ontology Engineer | Healthwise Healthwise helps people make better health decisions. -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
