Magnus; I'm a little unclear on exactly where this happens. When you say "I want to add this prop to a class…" what sequence of actions are you taking? Are you adding a value to the range of a property?
I think the "inconsistencies" you are experiencing are actually features designed to support OWL syntax. The message "Class or (non- annotation) property name expected" means that you are trying to add a value that is not allowed in OWL syntax. But your description states that you are adding a class and that the difference is whether the class is imported or locally defined. I wasn't able to find any place where this behavior is different for local vs. imported resources. So a more precise description of where this occurs will be necessary. -- Scott On Jan 7, 7:43 am, grindcrank <[email protected]> wrote: > I have a property "matches" between classes. When I want to add this > prop to a class with an existing target class ("Add existing ..."), > the following happens: > > Usually I try to find the target class using the CTRL+SPACE > autocompletion. Imported classes are found by this way but the form > field keeps having a red frame and the error message "Class or (non- > annotation) property name expected" shows in the status bar. > > When I look up the target class using the class navigation, everything > works out fine. When I add a not imported taregt class (i.e. one that > is in my actual ontology) using the method in the above paragraph, > everything works out fine. > > This GUI behaviour seem quite inconsistent to me. Has anyone noticed > the same and maybe can offer a workaround? > > Thanks, > > Magnus Niemann
-- You received this message because you are subscribed to the Google Groups "TopBraid Composer Users" group. 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-composer-users?hl=en.
