Hi TK, if you are wondering about restricting the user interface, then there are only limited ways: the preference pages of Classes and Properties views have options to make certain system properties visible or invisible. This won't prevent the user from using them though.
I think the cleanest mechanism would be to define a collection of constraint checks (in SPIN) that check whether any "dangerous" properties are used in your model. Then, you could use the Problems View to get a list of all places where the expressivity goes beyond AG's native capabilities/optimizations. Such a collection of SPIN constraints could be shared with others, and also produced for other subsets of OWL such as OWL Lite. Holger On Mar 4, 2009, at 1:38 PM, TK wrote: > > Goal: I'm trying to constrain my the TBC 2.6.2 [IDE] to only what > AllegroGraph 3.1.1 (the backend reasoner ) is capability of > understanding. > > Is there a way to configure TBC so that it only uses the RDFS and > selected OWL constructs that are in the AllegroGraph reasoner? They > are: > > rdf:type > rdfs:subClassOf > rdfs:subPropertyOf > rdfs:domain > rdfs:range > > owl:inverseOf > owl:TransitiveProperty > owl:SameAs > owl:hasValue > > Thanks in advance, > --tk > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
