Catrina; We do need to be clear on what you are viewing. Here's my take on what you are saying:
Scenario 1: - all files in Composer Workspace - using Ensemble served by TBC-ME localhost - Result is: all works as designed Scenario 2: - all files in Live workspace (Is this assumption correct?) - using Ensemble served by Live host - Result is: "No appropriate form definition could be found." error in Ensemble when opening a tree node (from an association tree) If this is the case then there could be a difference in how Live and TBC-ME are processing forms. We'll need to verify. Question #1: Does the error message appear in Ensemble? Question #2: Is the tree an association hierarchy (i.e. something other than rdfs:subClassOf)? Question #3: Is Ensemble wired to view the contents of a node in the Form? The answers to all three of these matter in terms of what we might be looking for. The following seems to be a new problem (?): <When I open the hierarchy in Composer, the class and property definitions do not appear. The skos:Concept is not recognized.> One thought is that previous inferences are interfering with the class view. Make sure all inferences are retracted and I'd suggest removing .owlinf to make sure that you start with a clean slate w.r.t. inferences. This would be good advice for both Composer and Live workspaces (you may need to log onto your server to remove files from the Live workspace). -- Scott On Sep 15, 7:18 pm, Catrina <[email protected]> wrote: > Scott, > > My hierarchy nodes are all instances of the skos:Concept class, which > is a subclass of owl:Thing. > I am not using a custom form layout. > > My hierarchy content ontology imports my vocabulary file (which > contains the data model - class and property definitions), and then my > vocabulary file imports the skos and dublin core ontologies. My > hierarchy ontology is stored in the RDF store (Oracle). My vocabulary > file and the skos rdf is stored in the same project as my .oracle file > on our server. > > When I open the hierarchy in Ensemble using localhost, I do not get > this error. I thought that could be because the imports are found in > my TBC workspace. > > When I open the hierarchy in Composer, the class and property > definitions do not appear. The skos:Concept is not recognized. > > When I open the hierarchy in Ensemble using our server, I get this > error. As I mentioned, both my vocabulary and the skos files are on > the server. > > Thanks, > Catrina --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
