Jim, can you send me (offline) a file that reproduces this problem? Chances are that there is a mismatch or non-defined prefix in one of the imports. These tend to be difficult to track down.
General best practices with SPARQLMotion scripts are: 1) Run in debug, choose Assert new prefixes, and save 2) Use ModifyPrefixes for those prefixes not caught by 1) Just as a note to all, to create a new thread, one should go to http://groups.google.com/group/topbraid-composer-users and use +new post. Otherwise threads get hijacked and it becomes difficult to find threads. -- Scott On May 11, 7:43 am, James A Miller <james_a_mil...@raytheon.com> wrote: > What defines the prefixes that will appear in the output file of a > SparqlMotion script? I am getting *most* of my expected prefixes, but > some are getting j.# prefixes, although they appear to be defined in the > n3 file. > > Jim --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TopBraid Composer Users" group. To post to this group, send email to topbraid-composer-users@googlegroups.com To unsubscribe from this group, send email to topbraid-composer-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/topbraid-composer-users?hl=en -~----------~----~----~----~------~----~------~--~---
