You can unlock any file using the Lock button in the Navigator. However, for Eclipse internal reasons, this button only works if TopBraid is "active", i.e. some other ontology file must be open in an editor.
Holger On Oct 15, 2009, at 12:12 PM, PaulZH wrote: > > Irene, > > Thanks for the input. > > One small issue though. > If I want to change the primary file to the in TBC included SKOS file > in the Common folder, it is refused due to the fact that this file is > locked and I do not succeed in unlocking this file. > > > Paul > > On Oct 15, 1:53 am, "Irene Polikoff" <[email protected]> wrote: >> Paul, >> >> If you open the SKOS file you want to be the primary one for the >> (shared) >> base URI, you will get a message saying that it is not primary and >> do you >> want to make it a primary. Once you say "yes", all the imports >> referring to >> its base URI should be resolved to this file. >> >> There is a File Registry view where you can see the mappings >> between base >> URIs and files. >> >> Regards, >> >> Irene >> >> -----Original Message----- >> From: [email protected] >> >> [mailto:[email protected]] On Behalf Of PaulZH >> Sent: Wednesday, October 14, 2009 5:02 PM >> To: TopBraid Composer Users >> Subject: [tbc-users] Re: caching issue with imported ontologies ? >> >> Scott, >> >> Many thanks for the elaborate explanation. >> With client was meant, the one who pays my bills :-). >> >> Some small remarks: >>> the two SKOS files are really two different >>> models >> >> I discussed this with some colleagues and they evaluated it as the >> same model but with slight differences in expressiveness. >> >>> they should have different base URIs. >> >> Yes, but they haven't and they are officially published as such. >> >>> I'd suggest changing >>> one of them. >> >> Ok, I'll do, but I would have preferred not having to do this, >> since I >> do not own these file. >> >> Paul >> >> On Oct 14, 3:47 pm, Scott Henninger <[email protected]> >> wrote: >>> 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 -~----------~----~----~----~------~----~------~--~---
