Paul; The core issue is that TopBraid uses the base URI as the file identifier, not the pathname in the workspace. This is following a Web-based model of file access. The implication is that Composer/Live treats all files with the same base URI as the same file. If there is more than one file that uses the same base URI, then Composer must choose which file it references for a unique base URI - the "primary file".
When you open a non-primary file, provided the primary file is not already opened, a message will appear asking whether or not you want to make the file the primary reference for the base URI. Choosing 'yes' will change the base URI reference to the current file, hence changing all if the imports using that base URI (SPARQLMotion scripts that load RDF from that base URI will also be affected). If a file is not the primary reference for a base URI, the file icon in the Navigator will appear with a yellow warning sign. You can also use the File Registry View (Windows > Show View) to view all base URIs, their associated files, and which are the primary and not primary references. <I do understand this behavior because both ontologies have the same identifier, but anyhow how can I make TBC point to the right file? > In your case, since the two SKOS files are really two different models, they should have different base URIs. I'd suggest changing one of them. Then the imports will be unambiguous. This is actually a good example of the meaning of a base URI - if two files are different, they need to have different identifiers. I.e. different base URIs. <Now the client changes mind and wants to use the OWL Full version > I wasn't sure what was meant by "client" here and want to make sure I'm not missing something. If this is an issue other than the above, let me know. -- Scott On Oct 14, 4:32 am, PaulZH <[email protected]> wrote: > Context. > > The SKOS ontology has two flavours: one OWL Full and one OWL-DL. > Topbraid inludes in its workplace/Topbraid/Common folder the OWL Full > version. > > What I did: > - I downloaded the OWL-DL version and imported it into another folder > of the Eclipse workplace. > - Then I (local) imported this ontology into my own, so far so good. > > Now the client changes mind and wants to use the OWL Full version > - I deleted the imported OWL-DL version > - I import the OWL Full version from the TBC Common folder, but after > importing it still points to the location of the DL version. > > I do understand this behavior because both ontologies have the same > identifier, but anyhow how can I make TBC point to the right file? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
