Re: Counterproposal for service references

I reviewed Roberto's counterproposal for describing service references. 
Thanks for the detailed spec. 

Roberto's approach is to put all interface and binding information in the 
XML Schema for the messages. Unfortunately, this leads to interfaces that 
are no longer abstract. I pointed this out to Roberto since it was one of 
the main considerations behind the <wsdl:reference> design [1]. However, 
Roberto claimed that this was not a valid requirement. I have therefore 
created a realistic but simple use case which shows why it is important 
not to put the binding information of a service reference in the 
interface. Doing so makes it non-reusable for other bindings.

The use case is posted at [2]. I am asking the WG to consider if my use 
case should be supported by WSDL 2.0. If so, then the counterprosal cannot 
be accepted. The <wsdl:reference> proposal satisfies all the known 
requirements. Roberto's counterproposal was an attempt to rework it in the 
context of XML Schema instead of WSDL. 

[1] http://lists.w3.org/Archives/Public/www-ws-desc/2003Sep/0187.html
[2] http://lists.w3.org/Archives/Public/www-ws-desc/2003Nov/0037.html

Arthur Ryman,
WebSphere Studio Development Lead,
Web Services/XML/Data Tools
Performance SWAT Team

phone: 905-413-3077, TL 969-3077
assistant: 905-413-2411, TL 969-2411
fax: 905-413-4920, TL 969-4920
intranet: http://w3.torolab.ibm.com/~ryman/