Parsa; There are a couple of interacting features here:

1. rdfs:label takes precedence over subclasses of rdfs:label (such as
skos:prefLabel), so if both are present rdfs:label wins.

2. If two labels render the same, Composer will show the local name
instead

-- Scott

On Jan 14, 1:36 pm, Parsa Mirhaji <[email protected]> wrote:
> Scott
> Thanks for the heads up about the reverse direction of the tree, that helped. 
> However, now that you pointed out about the use of the human readable lables 
> (skos:prefLable) it seems not working consistently? From the screenshot below 
> you can see that the instances of classes are not shown through their human 
> readable labels (neither in the instances view nor in the Associations view. 
> However instances of an owl:Class are consstently shown by their 
> skos:prefLable.
> Secondly if you look at the SN:Clinical_Drug class (highlighted and selected 
> in the right side panel), although it does have a skos:prefLabel and a 
> matching label for that matter, it does not show up neither in the class view 
> nor in the instances view... I looked into the file but didn't see a 
> difference on what may be causing this? As the model is constructed running a 
> script, it should be created the same way as others...
> So the most important question from my perspective is how to get the lables 
> work with the instances because that is what will make the difference in 
> usability of the TBC as an SKOS editor...
> Thanks
> Parsa
>
> [cid:3346320988_1252032]
>
> On 1/14/10 11:00 AM, "Scott Henninger" <[email protected]> wrote:
>
> Hello Parsa;  Some thoughts below.  If these don't help out you may
> want to send an example we can look at.
>
> <a hierarchy is expected to be built through following a provided a
> selected property (or so is my understanding)>
>
> Yes, this is the case, but keep in mind that the default layout for
> this view is like rdfs:subClassOf.  I.e. higher levels of the tree are
> objects of the lower level's subjects.  I.e. in your case:
>   :C0000970 :rb :C0724005
>
> You can use Switch direction (top-right of view) to reverse this.
>
> From what I see in the image, if there were a relationship somewhere
> of the form:
>   :xyz :rb :C0000970
>
> ...then it will appear as a next level of the tree beneath :C0000970.
> Note that the properties shown in :C0000970's form are in the opposite
> direction:
>   :C0000970 :rb :C0074808
>
> (BTW, if you turn on human readable labels - see person icon in top
> icon menu - you would see the skos:prefLabel in the tree.  I.e. it
> would read "Acetaminophen" instead of "C0000970".)
>
> -- Scott
>
> On Jan 13, 3:57 pm, Parsa Mirhaji <[email protected]> wrote:
>
>
>
> > When using the Associations View in TBC-ME 3.1.1 a hierarchy is expected to 
> > be built through following a provided a selected property (or so is my 
> > understanding). However, when I use a property (:rb in this case as 
> > illustrated in the image below), it only goes one step forward, although 
> > there are other objects associated with that same property to the selected 
> > node (as seen in the right hand side panel from the image below). Any 
> > insight?
>
> > [cid:3346243025_8346651]
> > Thanks
> > Parsa
>
> > Parsa Mirhaji, MD. PhD.
> > Assistant Professor
> > The School of Health Information Sciences
> > The University of Texas Health Science Center at Houston
> > Tel:       (713) 500-3157
> > Fax:      (713) 500-0370
> > Assistance (Connie Tapper): (713) 500-3937
>
> > Please consider environment before printing this email or its attachments.
>
> >  image.png
> > 49KViewDownload
>
> Parsa Mirhaji, MD. PhD.
> Assistant Professor
> The School of Health Information Sciences
> The University of Texas Health Science Center at Houston
> Tel:       (713) 500-3157
> Fax:      (713) 500-0370
> Assistance (Connie Tapper): (713) 500-3937
>
> Please consider environment before printing this email or its attachments.
>
>  image.png
> 221KViewDownload
-- 
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.


Reply via email to