For debugging, you may want to look into SPIN constraint checking: http://composing-the-semantic-web.blogspot.com/2009/01/introducing-spin-sparql-inferencing.html http://composing-the-semantic-web.blogspot.com/2009/01/video-sparql-based-inferencing-and.html
This is a convenient way to use queries to check that constraints are being met in the models. -- Scott On Feb 20, 9:46 am, Arthur Keen <[email protected]> wrote: > Scott, > > Thanks, that sounds like a very useful feature and it takes care of > the base URI and namespace as well, but I will try the SPARQLMotion > script first as I have a large number of ontology models representing > the meta objects in a high fidelity reservoir simulator, and I want to > keep them separated for more fine grained SCM that is needed for > collaboration and for maintaining backwards compatibility on object > loads across different schema versions of the objects we load. For > the reservoir objects, I can change the language in my translator. I > am looking forward to switching to RDF/XML as I will then be able to > use Gruff as an additional visualization for debugging purposes as it > currently reads ntriples and rdf/xml but not N3. > > Arthur > > On Feb 19, 2009, at 9:13 PM, Scott Henninger wrote: > > > > > Another idea is to use the Export... Export/Merge/Convert RDF Graphs > > wizard manually. This will let you convert one ontology at a time, > > but to a number of formats including RDF/OWL serializations. To do > > this open the file, choose a folder and open the Export wizard. > > > This exports the current ontology (RDF graph) to the file you name in > > the wizard. The wizard will also give you the option of merging > > imported models. So if you need/want all 50 models in one file you > > can do that by importing them all in the currently selected model, > > chose Export..., then check all of the models you want to merge > > > -- Scott > > > On Feb 19, 7:15 pm, Holger Knublauch <[email protected]> wrote: > >> 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 > > >> On Feb 19, 2009, at 4:23 PM, Arthur wrote: > > >>> 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. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
