[Top] [All Lists]

Re: [ontolog-forum] using SKOS for controlled values for controlled voca

To: "[ontolog-forum]" <ontolog-forum@xxxxxxxxxxxxxxxx>
Cc: "semantic-web@xxxxxx" <semantic-web@xxxxxx>, William Waites <ww@xxxxxxxx>
From: Amanda Vizedom <amanda.vizedom@xxxxxxxxx>
Date: Sat, 9 Oct 2010 18:43:08 -0400
Message-id: <AANLkTim4yQbKhcw2=Scy-utbBegKD7ia_7U4_aE47AxJ@xxxxxxxxxxxxxx>
It seems to me that your use case really presents an attempt to wrest ontological precision out of SKOS.  It's often sufficiently challenging to wrest ontological precision from OWL, but at least OWL is meant to support some degree of formal (logical) precision in specifying ontologies.  SKOS is explicitly *not* an ontology language, as I understand it. I read the introduction to the SKOS primer as emphasizing this: SKOS is designed more for mapping between resources in different Knowledge Organization Systems, including and especially across KOSes of different kinds.  It's not, I think, very well especially suited for ontological _expression_, for which task SKOS relations would be logically underspecified.

The lexical/conceptual distinction is clear, though, and supports the argument against using lexical properties to specify ontological relations (be they subclass or value-list or other in nature).


On Sat, Oct 9, 2010 at 17:59, Laskey, Ken <klaskey@xxxxxxxxx> wrote:

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.


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


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

Semantic Relations and Systematic Displays

--- On Sat, 10/9/10, Pavithra <pavithra_kenjige@xxxxxxxxx> wrote:

From: Pavithra <pavithra_kenjige@xxxxxxxxx>
Subject: Re: using SKOS for controlled values for controlled vocabulary
To: "KenLaskey" <klaskey@xxxxxxxxx>, "William Waites" <ww@xxxxxxxx>
Cc: "semantic-web@xxxxxx" <semantic-web@xxxxxx>, "John F. Sowa" <sowa@xxxxxxxxxxx>, ontolog-forum@xxxxxxxxxxxxxxxx
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]


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


--- On Sat, 10/9/10, William Waites <ww@xxxxxxxx> wrote:

From: William Waites <ww@xxxxxxxx>
Subject: Re: using SKOS for controlled values for controlled vocabulary
To: "Laskey, Ken" <klaskey@xxxxxxxxx>
Cc: "semantic-web@xxxxxx" <semantic-web@xxxxxx>
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.


 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" .

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

To Post: mailto:ontolog-forum@xxxxxxxxxxxxxxxx

Message Archives: http://ontolog.cim3.net/forum/ontolog-forum/  
Config Subscr: http://ontolog.cim3.net/mailman/listinfo/ontolog-forum/  
Unsubscribe: mailto:ontolog-forum-leave@xxxxxxxxxxxxxxxx
Shared Files: http://ontolog.cim3.net/file/
Community Wiki: http://ontolog.cim3.net/wiki/ 
To join: http://ontolog.cim3.net/cgi-bin/wiki.pl?WikiHomePage#nid1J
To Post: mailto:ontolog-forum@xxxxxxxxxxxxxxxx    (01)

<Prev in Thread] Current Thread [Next in Thread>