At the moment, CO and the other ILP-based ops have a method getNegativeConstraints that must be implemented for the OP to take any constraints into account.
It would be nice to be able to list which constraints are relevant directly in the tripleGrammar (and have getNegativeConstraints then automatically filled for all relevant OPs).
At the moment, CO and the other ILP-based ops have a method
getNegativeConstraints
that must be implemented for the OP to take any constraints into account.It would be nice to be able to list which constraints are relevant directly in the tripleGrammar (and have
getNegativeConstraints
then automatically filled for all relevant OPs).