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

RE: ordered concepts?

From: Miles, AJ \(Alistair\) <A.J.Miles@rl.ac.uk>
Date: Fri, 16 Dec 2005 16:08:25 -0000
Message-ID: <677CE4DD24B12C4B9FA138534E29FB1D9851E8@exchange11.fed.cclrc.ac.uk>
To: "Erik Hennum" <ehennum@us.ibm.com>, <public-esw-thes@w3.org>

Hi Erik,

Sorry to take so long replying to this - yes for these examples I'd use a skos:OrderedCollection without a label.

N.B. bear in mind the issue [1] wrt using semantic relations with collections as currently described in the SKOS Core Guide [2] which will lead to counterintuitive results if you compute RDFS entailments - i.e. you'll end up with each instance of skos:Collection being also an instance of skos:Concept.

Btw I saw a very nice presentation from some IBM colleagues of yours at a recent XMLUK meeting - they presented the DOCTOR document classification tool.



[1] http://www.w3.org/2004/02/skos/core/proposals#collections-5
[2] http://www.w3.org/TR/2005/WD-swbp-skos-core-guide-20051102/#seccollections

-----Original Message-----
From: public-esw-thes-request@w3.org [mailto:public-esw-thes-request@w3.org]On Behalf Of Erik Hennum
Sent: 02 November 2005 23:04
To: public-esw-thes@w3.org
Subject: ordered concepts?

Esteemed SKOSlians:

Apologies if there is a SKOS-user list where this question would be more appropriate or if the answer is given in an existing resource.

What is the recommended way for indicating sequence (perhaps logical, chrononological, or spatial) over a list of narrower concepts? Some common examples

.... Spring
.... Summer
.... Fall
.... Winter

.... North
.... East
.... South
.... West

In these cases, the narrower concepts have a sequence, but the relationship between the broader concept and the narrower concepts doesn't seem to require mediation by a meaningful collection -- at least not in quite the same way as the people by age example from the guide.

Is the recommendation none-the-less to provide a collection (perhaps unlabelled)? Possibly on the grounds that you might, for instance, want to order the seasons both by chronology and by average temperature?

My lazy temptation is to yearn for a skos:narrowerList property that offers a skos:memberlist for Concept with skos:narrower semantics. But perhaps there are good reasons to resist temptation....

Thanks in advance,

Erik Hennum
Received on Friday, 16 December 2005 16:08:38 UTC

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