- From: Miles, AJ (Alistair) <A.J.Miles@rl.ac.uk>
- Date: Tue, 24 Aug 2004 13:48:55 +0100
- To: Danny Ayers <danny.ayers@gmail.com>
- Cc: public-esw-thes@w3.org
Danny wrote: > Most of the constructs aren't really tied to Concepts, it might be > worth considering breaking these out into another namespace as a > utility vocabulary, perhaps having skos:inCollection and > skos:viewUnder as specializations of properties with a more general > domain/range. I'm not sure - might the collections be useful elsewhere > in SKOS, say for expressing lists of top concepts? Yes absolutely. Here are two other places where a general collection vocab is required: (1) In conjunction with the SKOS Mapping vocab - often a concept in a source scheme maps to more than one concept in a target scheme (i.e. to some combination of concepts). Currently SKOS Mapping uses containers (i.e. rdf:Bag) to build mapping targets, but I think that should be changed. (2) To use SKOS Core for describing web browser bookmark schemes ... I spoke to Jose Kahan about this earlier this year - he is developing the feature for W3C's Amaya browser [1] (which is very cool btw and certainly the best html editor I've ever come across) that allows you to export your bookmark scheme and bookmarks as RDF. He has a strong user requirement for the order of both the bookmarks and the bookmark folders to be preserved between sessions - so he needs to be able to express the ordering of a set of children under a parent node. However, these collections don't necessarily have to have a label. So I think Danny's right to suggest a general collection vocabulary which can be extended and applied to things like arrays of concepts, concept mapping, browser bookmarks etc. Whether to put this in a different namespace or not I don't know. As always, whatever we do, I think we should make a strong effort to keep things as simple as possible :) Al. [1] http://www.w3.org/Amaya >
Received on Tuesday, 24 August 2004 12:49:31 UTC