New CR Issue: Core Specification is inconsistent with wg resolutions (Issue 20 subissue d)

The CR Core Specification [1] provides a definition of an EPR, but it
appears that it does not reflect the resolution of an Issue [2] subissue
d (decided on 2/14/2005) to indicate that an EPR may have several Web
Service descriptions and multiple EPRs can be used to convey information
needed to address a particular WS endpoint. 
I would have expected this resolution to be integrated in the second
paragraph 
{A Web service endpoint is a (referenceable) entity, processor, or
resource to which Web service messages can be addressed. Endpoint
references convey the information needed to address a Web service
endpoint.}
I argue that the language in this paragraph does not really reflect the
intention of the wg. I also checked the current draft of the WSDL
binding document and it does not contain the resolution. The reason for
this resolution was to illustrate that an EPRs may be expressed via
different WSDL descriptions and for some reason this notion and the
resolution has been omitted from the specification. My review on the
other resolutions did not provide any clues as to why this resolution
was not applied. I suspect that this was a simple omission and the
resolution of the wg should be reflected in the current specification. 
This change will not affect the testing or implementations of the
specification. 
Cheers,
--umit

References: 

[1]
http://dev.w3.org/cvsweb/~checkout~/2004/ws/addressing/ws-addr-core.html
?content-type=text/html;%20charset=utf-8

[2] http://www.w3.org/2002/ws/addr/wd-issues/#i020


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

Dr. Umit Yalcinalp
Architect
NetWeaver Industry Standards
SAP Labs, LLC
Email: umit.yalcinalp@sap.com Tel: (650) 320-3095 
SDN: https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/u/36238

Received on Monday, 16 January 2006 22:30:37 UTC