No, it doesn’t find anything arbitrary. By default, the root of the tree is 
owl:Thing (you can change it). The tree will display all subclasses of its root 
and then for each child, its subclasses and so on.

If owl:Thing has no subclasses, you will see nothing but owl:Thing.

> On May 7, 2018, at 10:16 PM, Rob Atkinson <robatkinson...@gmail.com> wrote:
> 
> 
> Ok, I was about to respond... right, the class tree in the SWA applications 
> needs to use asserted rdfs:subClassOf triples - the automated inferences that 
> TBC makes are not visible.
> 
> 
> That seems a pretty critical piece of behaviour which ought to have big(ger?) 
> flags in the documentation -  and it seems to choose something arbitrary if 
> it doesnt find anything? (maybe it create a help message as a virtual class 
> to inform if no subclasses are present.)
> 
> OK - is it possible then for it to be clever and import a SPIN rule which 
> finds what entities are present then asserts the necessary subclass axioms?  
> Does such a thing already exist?
> 
> I would appreciate a quick recipe for exactly how to do this - I havent yet 
> got up to working out how to automate SPIN processing - I want some "system" 
> rules to happen automatically but be able to invoke other SPIN rules manually 
> in SWP interfaces FYI
> 
> 
> rob
> 
> 
>> on another front:
>> file 1( which shoiws correct class hierarchy in EDG, but doesnt show imports 
>> in TBC )
>> 
>> TBC assigned a default baseURI  
>> file:///C:/repos/surround/provrules/pizza_example/out/pizza_prov_out.ttl <>
>> 
>> when I change this in the baseURI and named Ontology in the file to:
>> http://www.co-ode.org/ontologies/pizza/pizza_prov_out/ 
>> <http://www.co-ode.org/ontologies/pizza/pizza_prov_out/>
>> 
>> TBC then displayed import correctly.
> 
> I guess the owl:imports statements were dangling off the 
> <http://www.co-ode.org/ontologies/pizza/pizza_prov_out/> 
> <http://www.co-ode.org/ontologies/pizza/pizza_prov_out/> resource which was 
> not identical to the declared base URI. It seems that you have fixed that.
> 
> Holger
> 
> (I still need to allocate time for your other, longer, email)
> 
> 
> 
>> 
>> 
>> On Tuesday, 8 May 2018 10:44:22 UTC+10, Rob Atkinson wrote:
>> 
>> Ahh - it seems top have dumped the screenshots...
>> 
>> I'm talk about two ontologies which import the same class model showing 
>> different set of classes in the class navigator pane (North-west)  in a SWA 
>> template - but the same classes if i open them in TBC
>> 
>> Rob
>> 
>> 
>> On Friday, 4 May 2018 13:11:48 UTC+10, Holger Knublauch wrote:
>> Sorry, I need more details to be helpful.
>> 
>> Are you referring to the class hierarchy view, or what is shown on the main 
>> area (forms)? What sort of instances are you looking at?
>> 
>> Holger
>> 
>> 
>> On 4/05/2018 12:29, Rob Atkinson wrote:
>>> 
>>> I have a SWA template based application that shows me different class 
>>> models in the class navigator depending on which of two simple graphs I 
>>> view - even though they import the same model ontology. What controls what 
>>> is shown in the Class navigator - in fact customising this is the next step 
>>> but first I need to find out what its sensitive to...
>>> 
>>> -- 
>>> Rob Atkinson
>>> e: rob.at...@surroundaustralia.com <>
>>> w: http://www.surroundaustralia.com <http://www.surroundaustralia.com/>
>>> m: +61 419 202973
>>> 
>>> Location:  Wollongong - Australia (61)
>>> ______________________________
>>>  
>>> Copyrights:
>>> SURROUND Australia Pty Ltd is the copyright owner of all original content 
>>> and attachments.
>>> All rights reserved. 
>>>  
>>> Confidentiality Notice:
>>> The contents of this e-mail are confidential to the ordinary user of the 
>>> e-mail address to which it is addressed and may also be privileged. If you 
>>> are not the addressee of this e-mail you may not copy, forward, disclose or 
>>> otherwise use it or any part of it or its attachments in any form 
>>> whatsoever. If you have received this e-mail in error please e-mail the 
>>> sender by replying to this message. 
>>> ______________________________
>>> 
>>> -- 
>>> 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 topbraid-user...@googlegroups.com <>.
>>> For more options, visit https://groups.google.com/d/optout 
>>> <https://groups.google.com/d/optout>.
>> 
>> -- 
>> 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 topbraid-users+unsubscr...@googlegroups.com 
>> <mailto:topbraid-users+unsubscr...@googlegroups.com>.
>> For more options, visit https://groups.google.com/d/optout 
>> <https://groups.google.com/d/optout>.
> 
> 
> -- 
> 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 topbraid-users+unsubscr...@googlegroups.com 
> <mailto:topbraid-users+unsubscr...@googlegroups.com>.
> For more options, visit https://groups.google.com/d/optout 
> <https://groups.google.com/d/optout>.
> 
> 
> -- 
> 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 topbraid-users+unsubscr...@googlegroups.com 
> <mailto:topbraid-users+unsubscr...@googlegroups.com>.
> For more options, visit https://groups.google.com/d/optout 
> <https://groups.google.com/d/optout>.

-- 
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 topbraid-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to