Hi Tim, I cannot think of a solution other than copying graph B into another graph D. owl:imports is always transitive.
Maybe someone else here has additional ideas? Holger > On 27 Jan 2025, at 11:31 PM, Tim Bridwell <[email protected]> wrote: > > We have a (temporary) use case where it would be helpful to import a graph > (B) into another graph (C), but do not want the schema graph (A) that is > necessarily imported into graph (B) to be included into (C). I know owl does > not have this affordance. Is there any workaround similar to > ui:graphWithoutImports that would work at graph (C)? > > For clarity: > 1) We have (A)>(B) and need that to remain; > 2) Want (B)>(C) without also including (A) in (C). > > -- > The topics of this mailing list include TopBraid EDG and related technologies > such as SHACL. > To post to this group, send email to [email protected] > --- > 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 visit > https://groups.google.com/d/msgid/topbraid-users/e7a5d89e-b5b2-4083-9cc6-443a6f7151e8n%40googlegroups.com > > <https://groups.google.com/d/msgid/topbraid-users/e7a5d89e-b5b2-4083-9cc6-443a6f7151e8n%40googlegroups.com?utm_medium=email&utm_source=footer>. -- The topics of this mailing list include TopBraid EDG and related technologies such as SHACL. To post to this group, send email to [email protected] --- 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 visit https://groups.google.com/d/msgid/topbraid-users/A1DDDEDD-A316-473C-B175-BA05AF2E89C4%40topquadrant.com.
