Shane; When you change the base URI of a file (or graph), any file that imports the file will be broken because the base URI defined in the owl:imports statement has changed. If you use the Ontology Overview in TopBraid Composer to make base URI changes, Composer will do a reverse lookup of where the base URI is imported and open a dialog box to choose which importing files should be changed.
This would be the recommended and safest way to refactor base URIs. -- Scott On Aug 10, 9:59 am, swingard <[email protected]> wrote: > I need to change the base URI's for every owl file in my project. > Many of the owl files import one another and I found if I open each > seperately and do a find and replace in notepad that it seems to work, > but when I copy everything back to topbraid there is a problem with > almost all the base uri's. Does this have something to do with the > way the owl files import one another? I found I could also open each > owl file with an in-line text editor and all the base URI changes > seems to have worked except the last owl file is too big to open. So > any ideas of how I should approach this would be greatly appreciated. -- You received this message because you are subscribed to the Google Group "TopBraid Suite Users", the topics of which include 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
