I am using TBCM 3.0 B2. I refactored the baseURI's and Namespaces on a set of N3-encoded models in a common workspace to remove the '.n3' suffix. However, after re-factoring, the "Imports Tab" for other models in that workspace that import the refactored models continue to display the old URI's and namespaces with the '.n3' suffix, but I can tell by looking at the text content of the model files that the import reference have indeed been refactored. This discrepancy persists after refresh and TBC reloads. I have not tried rebooting. The same thing happens if I create new models and import the refactored models.
For example, I changed baseURI and namespace on a (well) model from http://www.objectreservoir.com/owl/ontology/well.n3 http://www.objectreservoir.com/owl/ontology/well.n3# to baseURI http://www.objectreservoir.com/owl/ontology/well baseURI http://www.objectreservoir.com/owl/ontology/well# After refactoring, and a save all, the text view, the (production) model that imports the refactored (well) model has the correct import statement: <http://www.objectreservoir.com/owl/ontology/production> a owl:Ontology ; owl:imports <http://www.objectreservoir.com/owl/ontology/ field> ; owl:versionInfo "Created with TopBraid Composer"^^xsd:string . However, TopBraidComposer "Import Tab" continues to display the import statement with a '.n3' suffix. Interestingly, the "Import Grapher" displayes the imports correctly on the (production) model without the '.n3' suffix. Other than this idiosyncrasy, TBCM 3.0 b2 functions normally and imports the files correctly. Thanks Arthur --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
