We have numerous non-rdf data sources (i.e. text files, spreadsheets, etc) where we use sparqlmotion to convert the data in those files to rdf.
Our sparqlmotion scripts utilize the "smf:buildURI" to construct URIs using our targeted namespaces. We have added these namespaces to the list of Namespace Prefixes in the sparqlmotion script to not only make our sparql constructs be more legible, but also with the assumption that those prefixes would be written into the rdf files produced from the "export to rdf" modules in our sparqlmotion script. However, the namespace prefixes are NOT be written to the .rdf files and this is causing problems when we import those .rdf files into our "federated.owl" file because TopBraid Composer ends up assigning "j.0" as the prefix for all of the .rdf files generated in this way, producing namespace prefix conflicts. How can get the sparqlmotion scripts to write out the prefix we want to use into the individual .rdf files so that when they are imported they use the prefix we want them to use (rather than TBC's arbitrary "j.0" prefix). I should note that we follow the practice whereby we do not use default namespaces in any of our rdf files so that we can have consistent prefixes no matter where the .rdf file is referenced. Thanks, Phil -- You received this message because you are subscribed to the Google Group "TopBraid Suite Users", the topics of which include TopBraid Composer, TopBraid Live, TopBraid Ensemble, SPARQLMotion and SPIN. 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-users?hl=en
