This is indeed the case, as verified offline. For example, multiple resources have a label value of "application domain" and therefore will display the qname.
-- Scott On Oct 9, 1:15 pm, Holger Knublauch <[email protected]> wrote: > The system will fall back to using qnames if there are multiple > resources with the same rdfs:label. This is to distinguish them, e.g. > in input field. For example, rdfs:Class and owl:Class both are always > spelled out in their full qname. > > So in your case, could it be that your file (or imports) define things > with the same rdfs:label? > > Holger > > On Oct 9, 2009, at 10:27 AM, Li, Naicong wrote: > > > Hi, > > > When we choose to show rdfs:labels instead of qnames using the > > toggle button, we notice that some of properties are still showing > > up in qnames even though they have rdfs:label defined for them. And > > that of course affects our custom designed form layout: > > > <image001.png> > > > The following image shows that we do have rdfs:lable defined for > > these properties: > > > <image002.png> > > > Is this a bug? If so how can we get around it for now? > > > Thanks. > > Naicong --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TopBraid Composer Users" group. 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-composer-users?hl=en -~----------~----~----~----~------~----~------~--~---
