Tim; The way this works is keyed off of the base URI. When opening a file, Composer finds the import URI and searches the workspace. If the file exists there, then it is loaded. If not, the URI is used to search the Web. So the default is always local.
A couple of follow-ups to see if we can find the problem. <On inspection, when I look at B, everything seems fine> Does the owl:imports statement use the same URI that is in Composer's workspace? Use the File Registry (Window > Show View >File Registry to verify) <...and everything gets out of whack> How so? What sorts of problems are you seeing? Is the import recognized properly (a globe icon will appear if it is not)? -- Scott On Dec 22, 3:18 pm, Tim Darr <[email protected]> wrote: > I have two ontologies, A and B. Ontology B imports A from the local file > system in TBC. I have a simple program that generates some instances, based > on classes in A and saves them in B. This is done programmatically outside > TBC using Jena. On inspection, when I look at B, everything seems fine; the > A import is there and all the instances that I created are there. > > However, when I try to load B back into TBC, it thinks that A is a remote > ontology, not a local ontology and everything gets out of whack. I cannot > seem to get TBC to understand that A is a local ontology, not a remote > ontology. > > Is there anyway to get around this? > > -Thanks- > > Tim -- 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.
