Comments on "SKOS: requirements for standardization"

some comments on
http://isegserv.itd.rl.ac.uk/public/skos/press/dc2006/camera-ready-paper.pdf


On the whole I agree with much of this, though I'm concerned (and 
probably a little confused) about the use of the term 'index' as well as 
some of the underlying assumptions of SKOS.

My background in using SW technologies is pretty much restricted to the 
two use cases identified in the email archive: conceptual hypermedia [1] 
and search [2]. Thus my comments on this paper are driven by the 
requirements and constraints of those use cases.


'2.  Defining the scope of SKOS'
I'm not sure how to match the workflow described in this section with 
the workflows of the two use cases I mentioned above. Neither of the use 
cases appear to have this workflow.

'3.  Anticipated Software Architecture'
This section seems to omit what seems to me will be a requirement: the 
transformation of an existing taxonomy/ontology into a SKOS taxonomy. 
The transformation may be batch or dynamic, but I believe will be 
necessary.

(An aside on the comments on pagerank: AFAIK, pagerank has no effect on 
the performance of precision or recall, it only has an effect on sorting).

'4.2 Maximizing the Profitability of Controlled Vocabularies '
I think it would be useful to state in this section that the adoption of 
SKOS may also increase the profitability of _existing_ vocabularies by 
enabling them to be used by a greater number of applications (if the 
vocabularies can be transformed into a SKOS representation).

regards

Bernard



[1] http://lists.w3.org/Archives/Public/public-swd-wg/2006Oct/0044.html
[2] http://lists.w3.org/Archives/Public/public-swd-wg/2006Nov/0030.html

Received on Thursday, 16 November 2006 12:55:11 UTC