W3C home > Mailing lists > Public > public-swd-wg@w3.org > January 2007

[SKOS] structuring f2f discussion

From: Alistair Miles <a.j.miles@rl.ac.uk>
Date: Tue, 16 Jan 2007 17:20:38 +0000
Message-ID: <45AD0966.8040100@rl.ac.uk>
To: SWD WG <public-swd-wg@w3.org>


Some rough thoughts on how to structure SKOS discussion at the f2f ...

At a higher level, we could start developing an overview of the different *types* of 
application described in the use cases we have. This could help us to define some 
application "patterns" i.e. general scenarios that illustrate our expected application 
context for SKOS - these general scenarios could even be used as a preface to the 
requirements in the UCR doc?

This could also help us to highlight patterns we expected to find but that aren't yet 
represented by the use cases we have.

E.g. an application pattern might be something like: retrieval of multimedia objects, 
manually indexed using a controlled structured vocabulary.

At the lower level, we could start working towards a set of representational test cases 
for SKOS. I imagined that the extracts of vocabularies taken from the accepted use cases 
could provide the basis for a set of test cases - i.e. if it is possible to generate the 
extract from a SKOS representation then the test is passed.

This means that we would need vocabulary extracts to cover all of the major vocabulary 
features and styles we expect SKOS to be able to represent. This discussion might help us 
highlight where we need to return to use case submitters and ask for more detail, and/or 
where we need to approach specific vocabulary owners how haven't submitted a use case, for 
permission to use an extract from their vocabulary.

That's all, cheers for now.


Alistair Miles
Research Associate
CCLRC - Rutherford Appleton Laboratory
Building R1 Room 1.60
Fermi Avenue
Oxfordshire OX11 0QX
United Kingdom
Web: http://purl.org/net/aliman
Email: a.j.miles@rl.ac.uk
Tel: +44 (0)1235 445440
Received on Tuesday, 16 January 2007 17:21:03 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:07:48 UTC