requirements summary

I'd like to try to summarize some of the recent discussion as it
relates to requirements. I have at least seen some clear preferences 
emerge, although all of them may not be shared universally .. in fact 
I'd be surprised if they were. But it may help to try to write down some 
of the expressed positions, especially those that appear to have wide 
support.  N.b. I'm not going to define all my terms: that's another
thread.

1. External vs. internal: as Martin mentioned at the end of the F2F,
at least participants seem to agree that modelling an "external" view
of interactions is necessary. Whether an "internal" view is also
needed is TBD.

2. Multi-party vs. bilateral choreography: there is some skepticism
that modelling bilateral interactions is sufficient.

3. There also seemed to be agreement that dynamic participation is a
required feature (i.e., not all participants in a choreography may be
known in advance).

4. There is an expressed preference not to require a dependency on
WSDL (although as Martin noted there is a requirement in the charter
that WSDL 1.2 be supported). (Maybe abstract WSDL is ok?)

5. Declarative vs. executable model. Related to point 1, and also to
the discussion re context-free vs Turing-complete models at the F2F.
This is an area where I see continued disagreement. However, I think 
this is not so much a requirements issue as a decision that will result 
out of other requirements. I.e. other requirements and use cases will 
drive the group to take one or another approach, when it comes to the 
specification phase.

--Jon

Received on Monday, 24 March 2003 16:33:00 UTC