> -----Original Message-----
> From: Stefano POGLIANI [mailto:stefano.pogliani@sun.com]
> Sent: Wednesday, March 06, 2002 3:54 AM
> To: www-ws-arch@w3.org
> Subject: RE: Back to Requirements (was RE: Web Service Definition [Was
>
>
> I think this discussion, trying to make a concise definition
> of what a w/s is (or should be...), looks like trying to
> define how the result of a building activity looks like
> before having defined the requirements and the properties
> of what we are going to build.
Right. We're engaged in "Extreme Specbuilding". As with Extreme
Programming, one doesn't know what the customers want, so you have to do
some sketching and prototyping to even figure out the requirements, and
accept the fact that the requirements will probably change before you are
done. In the W3C, we are both the "customers" (or representatives of our
companies, who are the customers) and the "programmers". In other words,
we're figuring out the requirements, and even the definition of the problem,
as we go along.
Applying the XP analogy, I think this implies that we need to move forward
-- with requirements, and even sketching the architecture itself -- before
we come to closure on the definition of "web service", complete agreement on
requirements, etc. We basically have to take two steps forward whenever
possible, accepting that we have to take a step back now and then.