My first advise would be to modularize the ontology by separating model definition from the instance data. To do this, create a new file for your instances that imports the model file. Let's call it, for example, test-data.rdf. Your colleague who does the text mining will have a different set of instances. Let's call it text-mining.rdf. Both, test-data.rdf and text-mining.rdf would import the same ontology. Let's call it model.rdf.
With this set up model.rdf does not change simply because you iterate through the text mining runs. It may, of course, still change when, as part of ontology development, you decide to modify it. Rather that send files to each other through mail or Sharepoint, I recommend using a version control system such as CVS or SVN. TBC integrates with the version control systems, so you will be able to do commits and updates directly from TBC. The file names will not need to change, the version control system will manage version numbers internally. Regards, Irene -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of bradleys Sent: Tuesday, December 15, 2009 11:27 AM To: TopBraid Composer Users Subject: [tbc-users] Configuration advice: distrobuted ontology development I am looking for some configuration advice for our ontology development. Currently we have one Maestro License. I develop the ontology on a laptop drive, strip out any instances needed for my testing, upload to Sharepoint, send email to my Text mining person, who downloads the file, runs Gate and instatiates the ontology and then give it back to me by email. I validate the results, makes changes, strip out the instances and upload to SharePoint 2007 and we repeat the process. This creates multiple versions of the same basic ontology with only a date variation in the filename and we need to be able to carry on with ontology development will doing concurrent text mining builds. I am aware of you Multi User Mode and Sesame Repositories feature. Do you have any advice as to how we can set this up better? -- 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. -- 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.
