Use Case: I have a large data graph I wish to navigate and allow users to annotate so I expose in an EDG editor. Its not really "reference data" - but its generated by scripting so the body should only be changed by external processes - and the idea of annotation is to provide feedback on the content, manage additional information we need to attach etc.
If I include the data, the class tree works but it shows no instance - obviously only working on the current graph, not with imports. How can we control the query scope to allow a-box import heirarchies to be handled - effectively i want to distinguish between a-box and t-box imports I think. No problem adding a property to the graph the widget could look at to use in an import closure. Obviously GraphQL in general needs to be able to access the a-box graph closure. I can workaround with data load in the short term - but it means I'd have to handle annotations in working copies and never commit them - or perhaps have an export for the working copies I can save before committing them. -- 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/b2f26203-7dd7-4f86-a803-ae8f9aa31c5e%40googlegroups.com.
