W3C home > Mailing lists > Public > public-esw-thes@w3.org > April 2012

Representing code lists in SKOS?

From: Bob DuCharme <bob@snee.com>
Date: Thu, 26 Apr 2012 15:18:54 -0400
Message-ID: <4F999F9E.2000706@snee.com>
To: public-esw-thes@w3.org
Let's say I have a few flat lists of terms that I use to describe items 
in a catalog. The size list consists of small, medium, and large, and 
the colors list consists of red, green, and blue. What would be the best 
way to represent these in SKOS?

I like the suggestion of 
http://standards.data.gov.uk/proposal/skos-and-uris-used-local-government-business-model 
to make each list a concept scheme, giving me something like this:

   @prefix skos: <http://www.w3.org/2004/02/skos/core#> .
   @prefix : <http://example.org> .

   :size a skos:ConceptScheme .
   :small a skos:Concept ; skos:inScheme :size .
   :medium a skos:Concept ; skos:inScheme :size .
   :large a skos:Concept ; skos:inScheme :size .

   :color a skos:ConceptScheme .
   :red a skos:Concept ; skos:inScheme :color .
   :green a skos:Concept ; skos:inScheme :color .
   :blue a skos:Concept ; skos:inScheme :color .

If a given T-shirt is only available in small or large, I suppose I 
could also have this, i.e. there's nothing wrong with having the same 
concept belong to multiple lists, right?

   :t-shirt96size a skos:ConceptScheme .
   :small a skos:Concept ; skos:inScheme :size .
   :large a skos:Concept ; skos:inScheme :size .

Here are my questions:

- Does this look sensible to others?

- if so, what would be best for the first ConceptScheme's prefLabel 
value: "size", "sizes", or "size list"?

- skos:Collecton might work for code lists instead of 
skos:ConceptScheme; has anyone seen it used for that?

thanks,

Bob
Received on Thursday, 26 April 2012 19:19:17 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 26 April 2012 19:19:17 GMT