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
