I am not aware of a glitch that would remove sh:constraint triples.
Usually TBC leaves such triples in the files untouched. Could you send
me a file with instructions on what exactly made the triples disappear?
Also, it rather sounds like the sh:sparql (now: sh:select) triple may
have
Has anyone else noticed the following problem. I define an sh:constraint on
a class and all is well. If I define a second one on the same class all is
fine until I reload the graph, and then one of them 'disappears'. TBC knows
that I had a second one, because it now tells me that I have an
