Frank's proposal: http://lists.w3.org/Archives/Public/www-ws-arch/2002Aug/0313.html

(The following wording was reworded by DBooth, Roger and Katya.)


AG037 E-Business Friendly
The Web Services Architecture enables the
potential evolution of business needs 

Critical success factors:
AC033 Peer-to-Peer Interoperability
AC034 Multi-party Interactions
AC035 Service Re-use
AC036 Semantic Descriptions


------------------------
[Addresses choreography]

AC034 Multi-Party Interactions 
Web Services must not preclude the support of N party interactions, such as auctions, escrow services, proxy services, broker services 
AR034.1: Systems must not be precluded from quoting, verbatim and modified, messages within top-level messages, to an arbitrary depth 
AR034.2: Web Services must not be precluded from supporting interactions where one or more parties of the interaction are anonymous 
AR034.3: Systems must not be precluded from supporting multiple receivers and `wait' points in service orchestration 

-------------------

AC035 Service Re-use 
The Web Services Architecture must permit the effective re-use and composition of services 
AC035.1: It must be possible to compose services dynamically, on the fly, as well as statically 
AR035.3: It must be possible to express sequencing and nesting of services, and the flow of information between services 
AR035.4: Must not preclude the possibility for third parties to verify performance of services (where performance includes results as well as timeliness) 

--------------- 
AC036 Semantic Descriptions 
The Web Services Architecture must not preclude the characterization of a 
Web Service that attempts to make its semantics clear to an automatic system 
AR036.1: It must be possible to publish references to an ontology in a Web Service description 
AR036.2 Web Service descriptions must not preclude the characterization
of temporal characteristics of the service.