Thanks Holger - OK - I saved the imported ontology like you said. Inspecting the contents, I find the only difference from what I got by downloading the TTL file directly from W3C was the insertion of
# baseURI: http://www.w3.org/ns/locn This is a comment! http://www.w3.org/TR/turtle/#sec-grammar-comments But I guess it is important to TopBraid. I've previously noticed similar comments used to indicate imports as well. Hmmm. Now we are getting into (black) magic? Furthermore, when I put a copy of this saved file in a place where I could open it, then TopBraid automatically created a second Ontology resource whose URI is the baseURI, in addition to the explicit one already in the file. So clearly TopBraid insists on having an Ontology present whose URI is the baseURI declared in the file (graph). If you make any changes to the file and then save it, you end up with two ontologies in the file, which in turn confuses some other tools. One of my colleagues has pointed out that this may be coming from OWLAPI "the automatic ontology IRI mapping tools in OWLAPI assume that the base URI is the ontology IRI. As far as I know this should be just a convention." Is this the source of the problem in TB? -- -- You received this message because you are subscribed to the Google Group "TopBraid Suite Users", the topics of which include Enterprise Vocabulary Network (EVN), TopBraid Composer, TopBraid Live, TopBraid Insight, SPARQLMotion, SPARQL Web Pages 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 --- You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
