RE: using SKOS for controlled values for controlled vocabulary

Pavithra,

I read the SKOS Primer but I wasn't impressed with the approach because altLabel doesn't really capture either the subclass or value nature.  Also, the primer goes on to say that upward posting is not recommended.

I saw the Collection text and my initial thought was to use the collection as a constraint.  While the milk example in the primer makes sense for broader/narrower, I didn't feel that really caught the idea of color values because red doesn't seem like a true narrowing of the color concept.

If I can say xx:color rdfs:range yy:colorList, where color is a SKOS Concept and colorList is a SKOS Collection, then I think I've got what I want.

Ken

________________________________________
From: Pavithra [pavithra_kenjige@yahoo.com]
Sent: Saturday, October 09, 2010 5:14 PM
To: Laskey, Ken; William Waites
Cc: semantic-web@w3.org; John F. Sowa; ontolog-forum@ontolog.cim3.net
Subject: Re: using SKOS for controlled values for controlled vocabulary

Ken

There is the concept / usage  of "Collections" and "Ordered Collection" and "Semantic Relations" and "Semantic Display" in that document that can be used similarly..

Pavithra
Semantic Relations and Systematic Displays

--- On Sat, 10/9/10, Pavithra <pavithra_kenjige@yahoo.com> wrote:

From: Pavithra <pavithra_kenjige@yahoo.com>
Subject: Re: using SKOS for controlled values for controlled vocabulary
To: "KenLaskey" <klaskey@mitre.org>, "William Waites" <ww@styx.org>
Cc: "semantic-web@w3.org" <semantic-web@w3.org>, "John F. Sowa" <sowa@bestweb.net>, ontolog-forum@ontolog.cim3.net
Date: Saturday, October 9, 2010, 4:40 PM

[ Since the same topic is being discussed in semantic web and ontolog thread, I have included both]

Ken,

Seems to me that there are examples in the following link about usage of "altLabels" that specifies list of  values of a SKOS concept..

[  Reference:
http://www.w3.org/TR/2009/NOTE-skos-primer-20090818/  ]

Here is the example about concept " rock" and list of values as basalt, granite, and slate.  This is similar to concept color,  and list of values  as red, yellow and blue.   Here is the usage of it..

It is also possible to use skos:altLabel to represent cases of upward posting [ISO-2788<http://www.w3.org/TR/2009/NOTE-skos-primer-20090818/#ISO2788>]. That is, when a concept aggregates more-specialized notions that are not explicitly introduced as concepts in the considered KOS:

ex:rocks rdf:type skos:Concept;
  skos:prefLabel "rocks"@en;
  skos:altLabel "basalt"@en;
  skos:altLabel "granite"@en;
  skos:altLabel "slate"@en



Thanks,
Pavithra



--- On Sat, 10/9/10, William Waites <ww@styx.org> wrote:

From: William Waites <ww@styx.org>
Subject: Re: using SKOS for controlled values for controlled vocabulary
To: "Laskey, Ken" <klaskey@mitre.org>
Cc: "semantic-web@w3.org" <semantic-web@w3.org>
Date: Saturday, October 9, 2010, 3:12 PM

On 10-10-09 18:09, Laskey, Ken wrote:
>
> What I am missing is how to say a given description
> element in one controlled vocabulary, e.g. a SKOS Concept
> Scheme, can be constrained to a list of values, e.g. a
> SKOS Collection.  I was considering rdfs:range but I’m not
> sure that is applicable.

What about making a subclass of skos:Concept for the
concepts in your controlled vocabulary and then making
rdfs:range be that subclass? You wouldn't have to use
skos:Collection at all.

So,

  eg:Colour rdfs:subClassOf skos:Concept .
  eg:colour a owl:ObjectProperty ;
      rdfs:range eg:Colour .

  eg:red a eg:Colour ;
      skos:notation "red" .
  eg:green a eg:Colour ;
      skos:notation "green" .
  eg:blue a eg:Colour ;
      skos:notation "blue" .

Cheers,
-w
--
William Waites                       <ww@styx.org>
Mob: +44 789 798 9965
Fax: +44 131 464 4948
CD70 0498 8AE4 36EA 1CD7  281C 427A 3F36 2130 E9F5

Received on Saturday, 9 October 2010 22:00:33 UTC