- From: Youenn Fablet <youenn.fablet@crf.canon.fr>
- Date: Wed, 13 Dec 2006 14:43:09 +0100
- To: www-ws-desc <www-ws-desc@w3.org>
Reading section 5.1 in the primer, it is written that assigning unique
QNames of GED as inputs within the interface of the service is
sufficient to disambiguate the types of the messages that are received.
While this is certainly true for a typical SOAP service that uses the
Request/Response mep, this is not the case when the SOAP/Response mep is
used.
In that case, the GED QName is not sent in the message, only the
subchildren local names are sent in the url.
It would be easy to have two different GED QNames with the same
subchildren local names.
I do not know whether we should improve the primer, but this might be
worth noting it anyway.
The same kind of issue also arises with the HTTP binding.
In this case, the dispatching may be done according the url, the method,
the content-type and possibly other bits of information.
This flexibility is good if we are going from a service to a WSDL document.
In a typical WSDL first situation, it may however be hard for authors
and tools to check that message dispatching will never be ambiguous.
A few guidelines may help with that respect.
Any thoughts?
Youenn
Received on Wednesday, 13 December 2006 13:43:39 UTC