- From: Bernard Vatant <bernard.vatant@mondeca.com>
- Date: Fri, 25 Feb 2005 17:03:22 +0100
- To: <public-esw-thes@w3.org>
Alistair > I had thought about something like this, but wasn't sure if it should be done > with new vocab in SKOS Core, or with existing vocab from elsewhere. There is > the dc:isPartOf / dc:hasPart property pair. There is also the option to > declare classes of concepts as OWL restrictions on the skos:inScheme property > (as you did in another email) and declare one class to be a subclass of another. Good remarks. Indeed I'd rather buy the latter solution. BTW do you think it would be a good idea to somehow document such (best) practices when using OWL along with SKOS? And where? In the SKOS-Core guide? or in some other note? Bernard ********************************************************************************** Bernard Vatant Senior Consultant Knowledge Engineering bernard.vatant@mondeca.com "Making Sense of Content" : http://www.mondeca.com "Everything is a Subject" : http://universimmedia.blogspot.com **********************************************************************************
Received on Friday, 25 February 2005 16:03:33 UTC