Well, to give you one example. If you open the bim.ttl its very hard to find the Deur_1 as instance of ob:Door.
You would expect to find it via: Select in class tree: mm:Object, goto its instances and select ob:Door then I would expect to find Deur_1 as backlink (incoming reference) in its resource form because the Deur_1 has ob:Door as rdf:type. (before I split mm, ob and bim I am sure this worked) To compare, now use Protégé 4.1beta and browse a bit in the class view. Here you see all stuff collected now: metaclasses, classes and with direct access to their meta-individuals/individuals including Door_1. I guess this is caused by some assumptions in your GUI which might not suit meta-modelling capabilities best, I am not sure... Hope this explains a bit the kind of issues I encounter editting our stuuf in tbc and why I sometimes move to code for convenience. Michel TNO.NL Michel Böhms sr. Research Scientist Building Innovation TNO Van Mourik Broekmanweg 6 | PO Box 49 2600 AA | Delft | The Netherlands Tel +31 888663107 Moblie +31 6 30381220 E-mail [email protected] LinkedIn http://www.linkedin.com/in/michelbohms Skype michelbohms Twitter @MichelBohms Disclaimer > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Scott Henninger > Sent: dinsdag 15 februari 2011 22:45 > To: TopBraid Suite Users > Subject: [topbraid-users] Re: > > Michel; Let us know what you find difficult and we can see if > there are effective workarounds or places where we may need > enhancements. > Editing source directly is never recommended, even though > Turtle significantly simplifies the practice. There are just > too many places the edits can go wrong. > > Typos for example - in my experiences with users and > customers, using autocomplete avoids 90+% of the problems > experienced when hand-editing ontologies. It's much more > than the occasional typo that is quickly found. In many > cases a typo leads to long debugging session because it's > difficult to see that "it's an uppercase in one place and > lower case in another", just as one example. Very difficult > for humans to distinguish these things, and many mistakes > occur. Frankly, I can't see how complex, interrelated, > models can be created without something like autocompletion > of resource names. > > -- Scott > > On Feb 15, 3:28 pm, "Bohms, H.M. (Michel)" <[email protected]> > wrote: > [...] > > :ok, but since our ontologies are quite meta-like they are > sometimes easier to edit in Turtle directly than in tbc, but > ok, I see your point..... > [...] > > -- > You received this message because you are subscribed to the > Google Group "TopBraid Suite Users", the topics of which > include TopBraid Composer, TopBraid Live, TopBraid Ensemble, > SPARQLMotion and SPIN. > To post to this group, send email to > [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/topbraid-users?hl=en > This e-mail and its contents are subject to the DISCLAIMER at http://www.tno.nl/disclaimer/email.html -- You received this message because you are subscribed to the Google Group "TopBraid Suite Users", the topics of which include TopBraid Composer, TopBraid Live, TopBraid Ensemble, SPARQLMotion and SPIN. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/topbraid-users?hl=en
