Well, the problem seems to have something to do with prefix declarations. When I deleted the atm: prefix declaration and recreated it, the problem disappeared.
Perhaps I am confused about how to handle prefixes. In this particular ontology, I made the default namespace identical to the namespace associated with the atm: namespace. So there are two prefixes associated with the same namespace. @prefix : <http://xyz.arc.nasa.gov/ontology/ATM#> . @prefix atm: <http://xyz.arc.nasa.gov/ontology/ATM#> . Is this not recommended practice? I wanted to define classes using the explicit atm: prefix rather than relying on the default namespace as I thought this was the preferred practice. In addition, this file is being imported by other ontology files. Rich -- -- 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 Ensemble, 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.
