Arthur; Have you thought about using SVN for this? It does require setting up a CVS server (there are services for this ala http://cvsdude.com/), and will allow rollback, version management etc. In terms of storing frequently changing files this kind of source change control change is invaluable.
-- Scott On May 13, 11:28 pm, Arthur Keen <[email protected]> wrote: > Naicong > > I asked about this a couple of months back and I was quite surprised > that Composer does not directly implement this capability. I thought > Holger's solution would work well for one-time or infrequent > translation, but my challenge is that I have to keep the models in n3 > and owl in synch throughout development through lots of changes. I > estimated that it would take a longer time to learn SPARQLMotion than > to simply code a solution in Java. Creating a spreadsheet of all my > files would be tedious and error prone because I have many models in a > very deep file hierarchy and I would have to re-visit a spreadsheet of > all models often because of frequent re-factoring. So, I wrote a > small Java utility that recurses through a source directory tree, > creates an equivalent target directory tree, and on encountering .n3 > files, loads them, and then saves them in RDF/XML into the equivalent > location in the target directory structure. Is this what you are > looking for? > > Arthur > > On May 13, 2009, at 7:59 PM, Li, Naicong wrote: > > > Hi Irene, > > > I checked the SPARQLMotion functions list and did not see any > > obvious that I could use. I check the old emails on this list and > > found this one below. Do you mean I need to do something like what > > Holger is describing? > > > Thanks for the help. > > Naicong > > > ============================ > > <image001.gif> > > Arthur > > View profile > > More options Feb 19, 5:23 pm > > Is there an easy way in TopBraid to convert an entire project > > containing a large number of models in .N3 file format to another > > format e.g., .OWL? The project contains about 50 models and the > > developers would feel more comfortable with xml trainer wheels. > > > <image001.gif> > > Holger Knublauch > > View profile > > More options Feb 19, 6:15 pm > > Not out of the box, only SPARQLMotion could help. You would need the > > list of file names though, somehow (e.g. from a spreadsheet). Then use > > a SM script to import that spreadsheet and iterate over all file > > names. Then use sml:ImportRDFFromWorkspace to load and the > > corresponding export module to save it back in the new format. > > Holger > > > From: [email protected] > > [mailto:[email protected] > > ] On Behalf Of Irene Polikoff > > Sent: Tuesday, May 12, 2009 5:20 PM > > To: [email protected] > > Subject: [tbc-users] Re: File format conversion > > > Yes, of course, with a SPARQLMotion script > > > From: [email protected] > > [mailto:[email protected] > > ] On Behalf Of Li, Naicong > > Sent: Tuesday, May 12, 2009 7:58 PM > > To: [email protected] > > Subject: [tbc-users] File format conversion > > > Hi, > > > Because of our project needs, we need to convert the ontology format > > between .n3 and .owl quite often (sometimes to .allegro as well). > > We have about 40 ontologies, and in the past we did the conversion a > > couple times by manually exporting each file to a different format > > and it’s very time consuming (and error prone). Is there a way > > that we can do this in a batch? > > > Thanks. > > Naicong --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
