- From: Pavithra <pavithra_kenjige@yahoo.com>
- Date: Sat, 9 Oct 2010 13:40:04 -0700 (PDT)
- 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
[ Since the same topic is being discussed in semantic web and ontolog threa=
d, I have included both]
Ken,=C2=A0=C2=A0=20
Seems to me that there are examples in the following link about usage of "a=
ltLabels" that specifies list of=C2=A0 values of a SKOS concept.=C2=A0=C2=
=A0=20
[=C2=A0 Reference:
http://www.w3.org/TR/2009/NOTE-skos-primer-20090818/=C2=A0 ]
Here is the example about concept " rock" and list of values as basalt, gra=
nite, and slate.=C2=A0 This is similar to concept color,=C2=A0 and list of =
values=C2=A0 as red, yellow and blue.=C2=A0=C2=A0 Here is the usage of it..=
=20
It is also possible=0Ato use skos:altLabel to represent cases of upward=0Ap=
osting [ISO-2788]. That is, when a=0Aconcept aggregates more-specialized no=
tions that are not explicitly=0Aintroduced as concepts in the considered KO=
S:=0Aex:rocks rdf:type skos:Concept;=0A skos:prefLabel "rocks"@en;=0A sko=
s:altLabel "basalt"@en;=0A skos:altLabel "granite"@en;=0A skos:altLabel "=
slate"@en
Thanks,
Pavithra=20
--- 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
--0-519338044-1286656804=:90423
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable
<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;">[ Since the same topic is being discussed in semantic web and ontolog thread, I have included both]<br><br>Ken, <br><br>Seems to me that there are examples in the following link about usage of "altLabels" that specifies list of values of a SKOS concept.. <br><br>[ Reference:<br>http://www.w3.org/TR/2009/NOTE-skos-primer-20090818/ ]<br><br>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.. <br><br>It is also possible
to use <code>skos:altLabel</code> to represent cases of <em>upward
posting</em> [<cite><a href="http://www.w3.org/TR/2009/NOTE-skos-primer-20090818/#ISO2788">ISO-2788</a></cite>]. That is, when a
concept aggregates more-specialized notions that are not explicitly
introduced as concepts in the considered KOS:
<pre class="notecode">ex:rocks rdf:type skos:Concept;
skos:prefLabel "rocks"@en;
skos:altLabel "basalt"@en;
skos:altLabel "granite"@en;
skos:altLabel "slate"@en<br><br><br><br>Thanks,<br>Pavithra <br></pre><br><br><br>--- On <b>Sat, 10/9/10, William Waites <i><ww@styx.org></i></b> wrote:<br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"><br>From: William Waites <ww@styx.org><br>Subject: Re: using SKOS for controlled values for controlled vocabulary<br>To: "Laskey, Ken" <klaskey@mitre.org><br>Cc: "semantic-web@w3.org" <semantic-web@w3.org><br>Date: Saturday, October 9, 2010, 3:12 PM<br><br><div class="plainMail">On 10-10-09 18:09, Laskey, Ken wrote:<br>><br>> What I am missing is how to say a given description<br>> element in one controlled vocabulary, e.g. a SKOS Concept<br>> Scheme, can be constrained to a list of values, e.g. a<br>> SKOS Collection. I was considering rdfs:range but I’m not<br>> sure that is applicable.<br><br>What about making a subclass of skos:Concept for
the<br>concepts in your controlled vocabulary and then making<br>rdfs:range be that subclass? You wouldn't have to use<br>skos:Collection at all.<br><br>So,<br><br> eg:Colour rdfs:subClassOf skos:Concept .<br> eg:colour a owl:ObjectProperty ;<br> rdfs:range eg:Colour .<br><br> eg:red a eg:Colour ;<br> skos:notation "red" .<br> eg:green a eg:Colour ;<br> skos:notation "green" .<br> eg:blue a eg:Colour ;<br> skos:notation "blue" .<br><br>Cheers,<br>-w<br>-- <br>William Waites <<a ymailto="mailto:ww@styx.org" href="/mc/compose?to=ww@styx.org">ww@styx.org</a>><br>Mob: +44 789 798 9965<br>Fax: +44 131 464 4948<br>CD70 0498 8AE4 36EA 1CD7 281C 427A 3F36 2130 E9F5<br><br></div></blockquote></td></tr></table><br>
--0-519338044-1286656804=:90423--
Received on Saturday, 9 October 2010 20:43:35 UTC