- From: Bernard Vatant <bernard.vatant@mondeca.com>
- Date: Tue, 21 Sep 2004 08:48:55 +0200
- To: "Miles, AJ \(Alistair\) " <A.J.Miles@rl.ac.uk>, <public-esw-thes@w3.org>
Alistair A quick remark from the former chair of OASIS PubSubj Committee, who has to bite that bait :) Though I would of course welcome the introduction of subject indicator in skos vocabulary, I've never made up my mind about the relevancy of using owl:InverseFunctionalProperty to capture it. Since owl:InverseFunctionalProperty is a subclass of owl:ObjectProperty, having skos:subjectIndicator rdf:type owl:InverseFunctionalProperty would imply considering the object of skos:subjectIndicator as an Individual I'm not sure it's such a good idea. What do you imagine would be the range of skos:SubjectIndicator in that case? Would you leave it open? Or what? Cheers Bernard Bernard Vatant Senior Consultant Knowledge Engineering Mondeca - www.mondeca.com bernard.vatant@mondeca.com > -----Message d'origine----- > De : public-esw-thes-request@w3.org > [mailto:public-esw-thes-request@w3.org]De la part de Miles, AJ > (Alistair) > Envoyé : vendredi 17 septembre 2004 15:05 > À : 'public-esw-thes@w3.org' > Objet : subject indicators ... ? > > > > Just to get some response from this community ... do we like the idea of > introducing a property e.g. 'skos:subjectIndicator' with domain > skos:Concept, and type owl:InverseFunctionalProperty, so that people could > use the URL of a web resource defining a concept as a defacto identifier for > that concept? (i.e. support for OASIS pub-sub paradigm). > > 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 > >
Received on Tuesday, 21 September 2004 06:49:00 UTC