Currently when setting core:enableOptional in the config then it is the user that has the possibility to make the corresponding criteria optional.
But actually, if we know in the config that a certain property is not always there (e.g. by looking at SHACL cardinalities), could we make it ALWAYS optional ? in a transparent way for the user.
This would be something similar to the way the SERVICE keyword currently behaves.
Currently when setting
core:enableOptionalin the config then it is the user that has the possibility to make the corresponding criteria optional. But actually, if we know in the config that a certain property is not always there (e.g. by looking at SHACL cardinalities), could we make it ALWAYS optional ? in a transparent way for the user. This would be something similar to the way the SERVICE keyword currently behaves.