inline On Wednesday, 20 May 2020 13:18:52 UTC+10, Irene Polikoff wrote: > > Please see below > > On May 19, 2020, at 10:38 PM, Rob Atkinson <[email protected] > <javascript:>> wrote: > > > Use Case: > > I have a large data graph I wish to navigate and allow users to annotate > so I expose in an EDG editor. > > > What asset collection type are you using for this? Data graph? > > yes
> 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. > > > Include where? > > via owl:imports in the data graph > If you are not working with classes and properties, why are you using the > class tree? > the classes and instances layout is a reasonable way to navigate the instances by selecting classes of interest > Why are you expecting a class tree to show instances? > i dont > It only displays classes You could bring in Instances panel, it would then > show instances for a selected class, but it is not the most convenient view > for working with instances. > it is the default that shows up > Typically, the Search table panel works better and you can use Asset > Navigator to select a class of instances you want to focus on. > > OK - thats useful to know the direction - but Search gives me nothing useful - it obviously needs more than just the ontology and the instances to work. It shows the 'rootClass" and a free text box - the free text box is not active and the "asset type" dialog (is this the "asset navigator" ? and the drop down shows "no options' this is for an ontology that can be navigated via classes and instances - so it know about everything. Does the search perhaps rely on generating shapes for every class and property? If so, perhaps it should detect there are classes but no shapes and provide a prompt to generate shapes (but of course I'd never want to pollute the data with generated shapes - they belong in the T-box world!) > A screenshot would help. > > > 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. > > > I am having hard time understanding what you are talking about. Editors > work over the entire graph closure. All information is shown - whether it > is in the currently opened asset collection or in any of the imported > graphs. > nope - it may be the design but if so its a bug -if i copy the same data into the graph it shows, if i owl:import the data it doesnt show. > > 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. > > > What do you mean by “annotations”? You don’t have to commit a working > copy. All exports work for a working copy exactly the same as production > copy. > Dont sweat on this - i mean any additional statements I want to manage about the entities in the data graph without editing the underlying data graph itself. suffice to say data is not editable, but I want to attach additional statements to the data in EDG workflows. Its not relevant to the actual issue being discussed - except to make clear the 'doing something fundamentally different than managing different aspects of instance data in separate related graphs' is not the answer I am seeking - at least until I get what seems to be basic functions working - there are good reasons not to munge everything into a single graph. > > -- > 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] <javascript:>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/topbraid-users/b2f26203-7dd7-4f86-a803-ae8f9aa31c5e%40googlegroups.com > > <https://groups.google.com/d/msgid/topbraid-users/b2f26203-7dd7-4f86-a803-ae8f9aa31c5e%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/bceda023-6c87-443f-8251-1997b1afb09e%40googlegroups.com.
