Issue i020 -- restate the subissues in issue i020

During the F2F today I too an action to list the 4 sub issues within 
issue i020 [1] (that are embedded in the email that I had sent earlier [2]).

Subissue i:
WS-Addressing submission [3] section 2 (and now the WSDL binding spec 
[4] section 2) talks about the current limits of WSDL as a justification 
to not reuse WSDL syntactic structures. These limits do not exist and 
therefore the justification should be removed. The same section also 
talks about usecases where WS-Addressing "will" be used. Those usecases 
can also be satisfied without using WS-Addressing.

We resolved this subissue today by making the necessary editorial changes.

Subissue ii:
EPR represents things that the service element in WSDL can represent. 
Why does ws-addressing not reuse existing syntactic structures, where 
they do meet the requirements, instead of inventing new ones?

We decided to drop it, as we have WS-Addressing submission is our 
starting point and there is not a whole lot of support to redesign it.

Subissue iii:
An EPR allows one to include (optionally) a service endpoint/port.
If such an endpoint/port is included in an EPR, what is the relationship
between the value of the [address] property and the URI value in the
[service-port] property? We have said that the [address] property is a 
logical address and not necessarily the physical endpoint where messages 
can be sent and how the mapping between logical to physical takes place 
is an extensibility point. Is that true if a service QName is present in 
the EPR. I.e., should our spec say that if the service QName is present 
then the physical address is what is specified by the wsdl port.

This subissue is not resolved yet.

Subissue iv:
WS-Addressing talks about an Endpoint Reference, but does not say what 
an endpoint is. So what does an EPR refer to? WSDL also has the concept 
of an endpoint. What is the difference between the two, if any.

This subissue is not resolved yet.

-Anish
--

[1] http://www.w3.org/2002/ws/addr/wd-issues/#i020
[2] 
http://lists.w3.org/Archives/Public/public-ws-addressing/2004Dec/0168.html
[3] 
http://www.w3.org/Submission/2004/SUBM-ws-addressing-20040810/#_Toc77464317
[4] http://www.w3.org/TR/2004/WD-ws-addr-wsdl-20041208/#_Toc77464317

Received on Tuesday, 18 January 2005 05:36:52 UTC