Stella Dextre Clarke wrote: > I share the reservations expressed by Tiago and Sue Ellen Wright. My > worry is that a jack of all trades tends to be master of none. Trying to > meet everyone's objectives with one tool may reduce the effectiveness of > the tool for the core jobs it should be designed for. I must say I do not share your worries, and for a simle reason - SKOS is an enabling technology, not a policy standard. SKOS allows for the *expression* of certain kinds of information structures - but it wisely avoids policy questions of the kind: * how permanent/controlled should terms be? * how disjoint should terms be? * how should vocabularies be revised? etc. SKOS will let you use the policy that fits your use case. Saying that SKOS would fail because it allows too many scenarios would be similar to claiming XML is doomed to failure because it allows many kinds of validation, support different forms of extensibility, etc. Just as each XML language would specify what kinds of extensions are allowed, each SKOS concept scheme will specify what policy rules it follows. It's just a technology. So I do agree that folksonomies, at least the kind where "categories" are more that just plain keywords, could/should use SKOS, and SKOS should support that (through not caring about policy). /Mikael -- Plus ça change, plus c'est la même chose
Received on Sunday, 9 October 2005 20:30:33 UTC