Arthur; A property of sml:ExportToRDFFile is the base URI, so it is specified directly in the module. It would probably be a good idea to bind the original base URI to a variable, then use SPARQL string manipulation to, for example, substitute "owl" for "n3", then use that variable binding as the base URI when exporting the file.
sml:ModifyPrefixes can be used to manipulate other namespaces in the file. -- Scott On Feb 20, 9:19 am, Arthur Keen <[email protected]> wrote: > Holger, > > Thanks for the pointer on which SPARQLMotion functions to use. I am > also going to need to re-factor the namespaces and base URI's as they > contain the .n3 suffix as well. Is there a SPARQLMotion function for > doing that? I will give it a try this weekend. > > Arthur > > On Feb 19, 2009, at 7:15 PM, Holger Knublauch 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 -~----------~----~----~----~------~----~------~--~---
