SKOS REQUIREMENTS

Antoine: We have started the addition of use
cases
... Edited use cases on wiki is growing. There is both a
summary and detailed versions.
... the summary will go into the edited use case document
if the detail is appropriate.
... We have produced something that keeps the key details

Antoine: half of our use cases have been
edited.
...reading the edited use cases is good preparation.
...I can gather them into an html doc so people can read
the summaries.

daniel: different terminologies have different
needs ...
critical information to gather, some people have put it
into use cases, some havent' ...
don't know if we want to go to that level of detail for
meeting?

Alistair: We need to analyze the work going on to
understand how SKOS fits in
...Then there would be another level of detail in which we
determine how to represent vocabularies.
Alistair: The questionnaire was written to gather
understanding of the work as well as get the level
dlrubin: some people aren't providing that level of
detail.
Alistair: we may need to go back to the communities
...I'm not sure the level of detail to focus on at the
meeting
Tom: we need to have guidance for a strategy for reading the
material

dlrubin: two-tiered approach
<guus> but we should also start listing
reqs
dlrubin: I suggest the F2F reviewing the application areas
first and then summarizing the missing detail
Alistair: would be good idea to review the applications in
context before going into detail

Antoine has started a req list on
http://www.w3.org/2006/07/SWD/wiki/CandidateReqList
<guus> brainstorm session on reqs at
ftf, with rough thoughts as input ?!
Guus: If the editors have the initial list, we can
bootstrap the session with these thoughts at the F2F
...would be useful if have initial list, to work from
that
Antoine: I can produce links to the UCs
Alistair: I'll roll out the new SKOS website later this
week