Daniel; Notice you have created a logical inconsistency here. The semantics of owl:allValuesFrom is that if a value exists for the property,then the value can only come from the specified class. So when you define ":prop only :V1" in the subclass of :C, then all instances that have a :prop property should be an instance of :V1.
If you then add ":prop only :V2", then you have defined a contradictory definition - :prop can only be of type V1 and :prop can only be of type V2. Composer therefore chooses one of these arbitrarily. Of course, you can always fill in any value via 'Add empty row" - autocomplete works nicely. What you may be looking for is that a :prop in an instance of C can be filled with a value from either :V1 or :V2. In that case use the logical OR. I.e., in Manchester syntax: :prop only (:V1 or :V2) HTH -- Scott On Wednesday, May 16, 2012 10:44:22 AM UTC-5, Daniel Elenius wrote: > > I think there is a bug in the "class choosers" for creating/adding > property values: > > Create three top-level classes, C, V1, and V2. > Create a property prop. > On C, add the restriction "prop only V1". > On C, add the restriction "prop only V2". > Create an instance of C. > Select "create and add" on the widget for "prop" on the new instance. > You only get to choose "V1". You should get "V1" and "V2" both. Right? > > Ok, semantically the property values have to be instances of V1, but > they may not be asserted that way. It would be very helpful if you could > browse all the classes in all the inherited restrictions. > > Regards, > Daniel > -- You received this message because you are subscribed to the Google Group "TopBraid Suite Users", the topics of which include Enterprise Vocabulary Network (EVN), 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
