Bradley; I think looking into SVN would be a good idea. This can at least streamline the passing back-and-forth of files. Calais is directly supported in Composer and may be worth investigating. SPARQLMotion scripts may be possible for automating validation, making changes, and certainly stripping out instances.
-- Scott On Dec 15, 10:27 am, bradleys <[email protected]> wrote: > 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.
