Hallo Ian: from a applicational point of view both enumerated classes (one-of) AND inverse are very necessary (not to say indispensible!) If both features together makes reasoning much more complicated - I don't know what to do. Can we find a way which allows the user to use both features which will (in a normal case or so) NOT result in reasoning complications? For instance, in many cases inverse relations will be used only as a kind of syntactic sugar (no additional semantic provided in comparison to the original relation). But can users not familiar with DL understand such aspects of modeling? Regards RuedigerReceived on Thursday, 6 June 2002 05:55:06 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:57:50 GMT