Minutes of SWSA Telecon of March 9, 2004

Chris B, Massimo P, Stuart W, Amit S, others?
(Mark B is away this week, Chris leading discussion)

On the draft/outline of the requirements document:

1. Align headings of text with the entries in the table so that there is a
1-1 relationship

We talked about parallelizing the effort to fill in the sections and here
are real and potential assignments:

2. Stuart is going to work on Section 7 a bit. He might structure it into
subsections and does some of the work to fill some of the subsections. One
subsection is going to be management.

3. Section 7, the management subsection of it: Would Carole do it?

4. Section 5: Massimo is interested

5. Section 6: no lead for it yet

6. Section 8: might Tim do it?

7. Section 9: might Carole do it?

8. Amit might add a section on functional and non-functional requirements
for quality of service

9. Section 6: Norman might do it?

On what architecture means
--------------------------
We discussed that we should be 'brave' enough to come up with interfaces
that implement the requirements. Once these interfaces are there in draft
form, we check with the language team if their idea of meaning would be
covered by the interfaces. Any deviation would have to be synchronized by
maybe changing the interfaces. Once we sync up, we have a first draft

Uniqueness of interfaces
------------------------
We discussed that different variants of the same interface might be
proposed. For example, there might be several interfaces for a discovery
component. For example one that does a pure select on web services that
would implement the desired functionality. The return would be a raw list of
web services. And another one that not only selects, but also filters down
the list according to some given criteria (like cost, etc.). Both are valid
discovery interfaces and both can be proposed by us.

I am not sure, but maybe we could have an initial list at the F2F?