Minutes of SWSA telecon of 03 July 1

Participants: Mark Burstein, Mike Dean, Tim Finin, Massimo Paolucci

Stuart Williams and Enrico Motta were unable to attend after trying and
failing with the conference call system.  The meeting started 1/2 hr late
due to the technical problems there (no answer).
MB: Main goal is to gather feedback to revise the draft work plan.

MP: How much do we put into the laundry list vs what is covered in 
charter of w3c web services committee? We want to piggy back on what they do.

Mike: milestone 3: submission vs recommendation - submission is what goes into starting a 
w3c working group. Getting some working prototypes adds credibility to submission. 

Mark: Other things for list in 0 (processes in SWS environment)? Do we want item M.
(server process management)? Do we want to remove any others? reword? add?
My intent was that this list be of sws processes that will require
semantics support functions which we will tease out from the use cases.

Tim: Best to keep it open and add to it until we do use cases. We should do tasks 
0 and 1 in parallel. 

Mark: That was the intent of deliverable 1 (Combines Use Cases and Requirements)

Tim: We are missing advertising from the list. (Mark - it got lost - will put it back)

Tim: SWSL list is missing invocation. 

Mark: another one I thought of putting in but didn't was something related
to knowledge services and knowledge queries.  Matchmaking falls under this
as does DQL. This was the use case that Anatas Kiryakov had wanted to
do. DAML-S doesn't handle knowledge provision services well.

Tim: What about outsourcing? (third party services used by primary services)

Mark: Semantics should help to make third party services become more
transparent by reference. It is not that the primary service should
necessarily adopt a protocol of the outsourced service, but its advertised
capability should reflect that functionality. e.g. If service takes
American Express, then Amex should have an advertisement that can be "used
by" the vendor that says what information will be required to buy with
Amex. This is different than saying exactly what values will go into a
message to the vendor. But it would be nice if there was a way to refer to
the concept of the data needed to complete the transaction that was
reflected in some part of the vendors buying protocol.

Mark: Everyone should comment on the draft by email and I will produce
another draft this week. Goal is to finalize it next Tuesday.