Re: [topbraid-users] Naming conflicts and human-readable labels mode

[Scott Henninger]

Rich; The way prefixes work is that they are a simple text substitution.  So given you definitions, then;   :fiddlestyx ... and   atm:fiddlestyx ...are precisely the same uri: <http://xyz.arc.nasa.gov/ontology/ATM#fiddlestyx>.  I.e., you can use either prefix to produce the URI. That's not something I would recommend, particularly using the default prefix.  Let's say you imported this file (graph) into another file (graph) that also defines the default prefix (i.e. your first @prefix statement).  Which should will be used?  In Composer, a new prefix will be created to resolve the ambiguity.  That could cause some confusion, we'd suggest you only use the default prefix to create PowerPoint slides. It seems, though that the real question is about labels, which is the rdfs:label property and its subproperties.  So the original issue could be different than this.  As Holger states, any example you can provide will be helpful. -- Scott On 6/4/2013 6:36 AM, Rich Keller wrote: 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 topbraid-users@googlegroups.com To unsubscribe from this group, send email to topbraid-users+unsubscr...@googlegroups.com 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 topbraid-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.     -- -- 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 topbraid-users@googlegroups.com To unsubscribe from this group, send email to topbraid-users+unsubscr...@googlegroups.com 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 topbraid-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.