W3C home > Mailing lists > Public > public-esw-thes@w3.org > January 2005

RE: Quick comment from new SKOS user

From: Matthews, BM (Brian) <B.M.Matthews@rl.ac.uk>
Date: Thu, 6 Jan 2005 12:12:32 -0000
Message-ID: <F5839D944C66C049BDB45F4C1E3DF89D181F89@exchange31.fed.cclrc.ac.uk>
To: "'Dickinson, Ian John (HP Labs, Bristol, UK)'" <ian.dickinson@hp.com>, public-esw-thes@w3.org


Point taken, I accept that there is an ambiguity - there
has been a long history of different names for this most
fundamental of thesaurus relationships in SKOS and its

The interpretation we have settled on :

C0 skos:narrower C1
"C0 has the narrower concept C1"

is more natural if you think of it "operationally" in the 
directed labelled graph.  To answer the query:
"From concept C0 find me all its narrower concepts". 
then you follow all the skos:narrower properties from C0.
With the other interpretation, you would follow the skos:broader,
which would seem odd!

The versions of SKOS Core guide
demonstrates how the property should be interpreted.


> -----Original Message-----
> From: public-esw-thes-request@w3.org
> [mailto:public-esw-thes-request@w3.org]On Behalf Of 
> Dickinson, Ian John
> (HP Labs, Bristol, UK)
> Sent: 06 January 2005 11:53
> To: public-esw-thes@w3.org
> Subject: Quick comment from new SKOS user
> Hi,
> I've just started using SKOS in a project I'm working on, and there's
> one thing I found slightly confusing from the outset. Consider two
> concepts, C0 and C1, and the statement
> C0 skos:narrower C1
> I find this ambiguous, since the two readings
> "C0 is a narrower concept than C1"
> "C0 has the narrower concept C1"
> are equally plausible from a simple reading of the statement. If
> anything, I find former interpretation slightly more natural, since in
> colloquial English when stating a "narrowment" (:-) the narrower thing
> usually comes first. E.g:
> car narrower garage-door
> "My car is fortunately narrower than my garage door"
> garage-door narrower car
> "My garage-door has-narrower-thing my car"
> I know it's a different sense of 'narrow', but still ...
> RDFS solves this by adding a preposition to indicate the direction
> rdfs:subClassOf, rather than just rdfs:subClass which would have the
> same problem. I guess it's too late now to change the actual SKOS
> predicate name, but perhaps you could clarify the direction of the
> relationship in the documentation.  The same comment applies to
> skos:broader, btw.
> Apologies if this has come up before. I did take a quick look at the
> archive but didn't see anything.
> Regards,
> Ian
Received on Thursday, 6 January 2005 12:13:11 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:45:17 UTC