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

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

From: Miles, AJ (Alistair) <A.J.Miles@rl.ac.uk>
Date: Mon, 8 Nov 2004 15:06:38 -0000
Message-ID: <350DC7048372D31197F200902773DF4C05E50D05@exchange11.rl.ac.uk>
To: "'public-esw-thes@w3.org'" <public-esw-thes@w3.org>

I think there is enough consensus here to support the addition to SKOS Core
of a 'skos:subjectIndicator' property, and an inverse-functional property,
and defined in relation to OASIS specs.

In addition, I do think there are some more general semantics which could
valuably be captured by a property such as the described 'skos:resolveTo'
below, as a super-property of 'skos:subjectIndicator'.  However, I think
this needs a bit more discussion.

Therefore I propose to add a 'skos:subjectIndicator' property to SKOS Core
immediately, and we can always add a super-property later on after further
discussion.

Yours,

Alistair.

> -----Original Message-----
> From: public-esw-thes-request@w3.org
> [mailto:public-esw-thes-request@w3.org]On Behalf Of Miles, AJ 
> (Alistair)
> Sent: 21 October 2004 16:05
> To: 'public-esw-thes@w3.org'
> Subject: RE: [Proposal][SKOS-Core] revised proposal for subject
> indicators
> 
> 
> 
> 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
> > 
> 
Received on Monday, 8 November 2004 15:25:27 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:38:52 GMT