Peer to Peer Goal

This message posits a new goal for WS Reqs, with some supporting CSFs 
and requirements

There is a major opportunity for supporting the interworking of systems 
where a sustained bi-directional relationship is required. If this is 
not WEB services then another core paradigm will be co-opted to support 
this kind of business as it is critical.


D-AG007 Peer to Peer interoperability
    The Web services architecture must support interoperability between 
peers as well as client-server architecture. Many business processes are 
not easily modeled as straightforward client/server architectures, 
especially in the context of the Internet. While the customer/supplier 
relationship is
still dominant, this does not imply that all (or even most) interactions 
between them can be accurately captured using client/server architecture.


   Critical Success Factors for this goal:

AC023, AC024

D-AC023
   Web services and clients must support modes of interaction where both 
have a permanent presence

D-AR023.1
   Clients and servers must support asynchronous messaging, such as event 
notification. I.e., a supplier must be able to notify a customer of an 
event.
D-AR023.2
   It must be possible for the architecture to model extended 
conversations between peer web services
D-AR023.3
   It must be possible for peers to volunteer information as well as 
invoke methods

D-AC024
   Web services such be able to support N party interactions, such as 
auctions, escrow services, proxy services, broker services.

D-AC024.1
   It must be possible to quote, verbatim and modified, messages within 
top-level messages, to an arbitrary depth.
D-AC024.2
   It must be possible to `anonymize' (sic) messages to elide the 
intended recipient
D-AC024.3
   It must be possible to express multiple receivers and to express 
`wait' points in service orchestration