RE: Issue i020, subissue iv: resolution proposal

>-----Original Message-----
>Sent: Friday, Feb 11, 2005 16:44 PM
>Subject: Issue i020, subissue iv: resolution proposal
>I took an action during last week's call to send wordings that can be 
>added to the core spec to resolve issue i020, subissue iv.
>Based on last week's call here is the information I have tried to 
>capture in the paragraph at the end of this email:
>1) WSDL 2.0 and WS-Addressing uses the same term "endpoint" which can 
>cause confusion (a WSDL endpoint can also be used to provide 
>2) Jonathan's explanation that there are three different thing: an 
>endpoint, description of an endpoint and a reference to an endpoint.
>3) An endpoint can have multiple descriptions
>4) Multiple EPRs can point to the same endpoint (this was not 
>during the call, but I see this as a logical conclusion from 
>the discussion)
>5) An EPR and a Description are optimized to do different things. I 
>don't think there was an agreement that an EPR is optimized 
>for runtime 
>use and description for static use (suggested by Paco). Instead I have 
>used wordings which say that an EPR is optimized to convey addressing 
>information and WSDL is optimized to describe the service.
>I would like to propose that we add the paragraph at the end of this 
>email in the Introduction section of core right after:
>"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."
>New text to be added:
>"Note that WSDL 2.0 has an Endpoint component [ref] which along with 
>other WSDL 2.0 components can be used to describe a Web service 
>endpoint. A Web service endpoint may in fact have multiple such 

> Similarly multiple EPRs can be used to convey 
>needed to address a particular Web service endpoint. An EPR is 
>to convey information required to address a Web service 
>endpoint whereas 
>a WSDL 2.0 description is optimized to describe a Web service."
>Please suggest alternatives/changes if you don't like the exact text.

I support the text you have added. It clarifies a lot of the confusion
wrt the relationship between Endpoints, WSDL Endpoint components and




Received on Monday, 14 February 2005 19:55:41 UTC