W3C home > Mailing lists > Public > public-esw-thes@w3.org > October 2004

RE: [Proposal][SKOS-Core] revised proposal for subject indicators

From: Carl Mattocks <carlmattocks@checkmi.com>
Date: Thu, 21 Oct 2004 11:41:02 -0400 (EDT)
Message-ID: <15729.216.163.247.1.1098373262.squirrel@webmail.netcarrier.com>
To: "Miles, AJ \(Alistair\)" <A.J.Miles@rl.ac.uk>
Cc: "'public-esw-thes@w3.org'" <public-esw-thes@w3.org>

I support this idea ..
and propose that something like dc:creator also be a sub-property of
'skos:resolveTo' .. Which would help folks like myself (and my
machine-agent) to make decisions on the acceptability of an URI'd concept.

carl

<quote who="Miles, AJ (Alistair)">
>
> Thinking about this some more, I would like to extend this proposal to
> include another property:
>
>  - skos:resolveTo
>
> With 'skos:resolveTo' you can simply specify the URL of a web resource, to
> which you would like the URI of a concept to be resolved.  There are no
> constraints on the nature of that resource or its content.
>
> Then 'skos:subjectIndicator' is defined as a sub-property of
> 'skos:resolveTo'.
>
> An alternative would be to use 'foaf:homepage', instead of
> 'skos:resolveTo'
> as described above.
>
> Any thoughts on this?
>
> Al.
>
>> -----Original Message-----
>> From: public-esw-thes-request@w3.org
>> [mailto:public-esw-thes-request@w3.org]On Behalf Of Carl Mattocks
>> Sent: 13 October 2004 19:28
>> To: Miles, AJ (Alistair)
>> Cc: 'public-esw-thes@w3.org'; 'Bernard Vatant'
>> Subject: Re: [Proposal][SKOS-Core] revised proposal for subject
>> indicators
>>
>>
>>
>> et Al :
>> ++ 1
>> on (1) & (2)
>>
>> carl
>>
>> <quote who="Miles, AJ (Alistair)">
>> >
>> > Hi,
>> >
>> > Here is a revised proposal for handling subject indicators
>> in SKOS Core,
>> > based on Bernard's suggestion:
>> >
>> > Add the following property:
>> >
>> >  - subjectIndicatorRef
>> >
>> > Additionally:
>> >
>> > (1) the property skos:subjectIndicatorRef is defined by reference to
>> > appropriate OASIS / TM specs (Bernard can you help me out here?)
>> >
>> > (2) skos:subjectIndicatorRef is an owl:InverseFunctionalProperty.
>> >
>> > The reason for supporting (2) is that it allows description
>> of concept
>> > schemes via their indicators (i.e. without URIs) so you can
>> have e.g. ...
>> >
>> > <skos:Concept>
>> >   <skos:prefLabel>Fruit</skos:prefLabel>
>> >   <skos:subjectIndicatorRef
>> rdf:resource="http://foo.com/Fruit.html"/>
>> >   <skos:narrower rdf:parseType="Resource">
>> >     <skos:subjectIndicatorRef
>> rdf:resource="http://foo.com/Bananas.html"/>
>> >   </skos:narrower>
>> >   <skos:related rdf:parseType="Resource">
>> >     <skos:subjectIndicatorRef
>> > rdf:resource="http://foo.com/Vegetables.html"/>
>> >   </skos:related>
>> > </skos:Concept>
>> >
>> > That's all.
>> >
>> > Al.
>> >
>> > ---
>> > Alistair Miles
>> > Research Associate
>> > CCLRC - Rutherford Appleton Laboratory
>> > Building R1 Room 1.60
>> > Fermi Avenue
>> > Chilton
>> > Didcot
>> > Oxfordshire OX11 0QX
>> > United Kingdom
>> > Email:        a.j.miles@rl.ac.uk
>> > Tel: +44 (0)1235 445440
>> >
>> >
>> >
>>
>>
>> --
>> Carl Mattocks
>>
>> co-Chair OASIS (ISO/TS 15000) ebXMLRegistry Semantic Content SC
>> co-Chair OASIS Business Centric Methodology TC
>> CEO CHECKMi
>> v/f (usa) 908 322 8715
>> www.CHECKMi.com
>> Semantically Smart Compendiums
>> (AOL) IM CarlCHECKMi
>>
>
>


-- 
Carl Mattocks

co-Chair OASIS (ISO/TS 15000) ebXMLRegistry Semantic Content SC
co-Chair OASIS Business Centric Methodology TC
CEO CHECKMi
v/f (usa) 908 322 8715
www.CHECKMi.com
Semantically Smart Compendiums
(AOL) IM CarlCHECKMi
Received on Thursday, 21 October 2004 15:41:05 UTC

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