I am working with a team that is using a large number of sh:values and rules shapes to produce inferred triples for use in EDG. It's working really well. However, we've found a reason we might want to materialize these triples to allow greater access to them from SPARQL, etc.
The problem we are running into is that we only want to materialize a subset of the triples since doing all of them generates too much data. Ideally, we could annotate a shape to declare that it should or should not materialize triples. It's like "deactived" for materialization.
Any ideas here?
Thanks!
Adam