Yes if I understand your use case correctly then such a flag already exists: dash:neverMaterialize
Holger > On 26 Jul 2022, at 9:22 am, Adam Kimball <[email protected]> wrote: > > 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 > > > > > -- > 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] > <mailto:[email protected]>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/topbraid-users/df659e52-2df1-473c-9c15-1df133f2d75dn%40googlegroups.com > > <https://groups.google.com/d/msgid/topbraid-users/df659e52-2df1-473c-9c15-1df133f2d75dn%40googlegroups.com?utm_medium=email&utm_source=footer>. -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/5E9BED92-1E43-4649-A548-90C25544A91B%40topquadrant.com.
