D-AR004.1 proposal

Following up on the proposed D-AC004 [1]: 
'does not preclude any programming model'

I propose the following requirement:
'D-AR004.1 Publish a wide range of usage scenarios which 
demonstrate architectural neutrality relative to well-known 
Web Services interaction models.'

Note: I am not overall happy with the verbiage. Perhaps someone 
can clean up the text.

For contrast, XMLP handled this issue as requirement R500:
'The specification will make reasonable efforts to support (but not define)
a broad range of programming models suitable for the applications intended
for XP.'

The XMLP requirement was handled as described below [2]:
'The introduction to the SOAP specification states that: SOAP provides 
a simple and lightweight mechanism for exchanging structured and typed 
information between peers in a decentralized, distributed environment 
using XML. SOAP does not itself define any application semantics such 
as a programming model or implementation specific semantics; rather it 
defines a simple mechanism for expressing application semantics by providing 
a modular packaging model and encoding mechanisms for encoding data within 
modules. This allows SOAP to be used in a large variety of systems ranging 
from messaging systems to RPC. Therefore the SOAP 1.1 specification mainly 
supports R500. Issue: There is a common belief that SOAP is intended for, 
and only supports the RPC programming model. The XP WG should emphasise the 
neutrality of its specification to programming models and illustrate its 
applicability to them via a wide range of use cases.'

Comments?
BR, Mike

[1] http://lists.w3.org/Archives/Member/w3c-ws-arch/2002May/0168.html
[2] http://www.w3.org/2000/xp/Group/xmlp-issues#x49

Received on Thursday, 6 June 2002 10:33:40 UTC