RE: Back to Requirements (was RE: Web Service Definition [Was

I think this is the right path. Making a definition without
sketching out all the requirements and without knowing the
properties of what we are going to build, is imho quite risky
since words could have different meanings for many people.

As you say, we are not dealing with something "already known",
for which a definition could be easily and unambiguosly found.
Let's explore what we are dealing with and, based on the findings,
let's later give a concise definition.

/stefano

» -----Original Message-----
» From: www-ws-arch-request@w3.org [mailto:www-ws-arch-request@w3.org]On
» Behalf Of Champion, Mike
» Sent: 06 March 2002 14:17
» To: www-ws-arch@w3.org
» Subject: RE: Back to Requirements (was RE: Web Service Definition [Was
»
» 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.
»
»

Received on Wednesday, 6 March 2002 08:26:53 UTC