RE: endpoint terminology confusion

WS-Terminology? Did I miss the announcement of a new standard? :-) (sorry)
 
I'd suggest that each standard is defining words like endpoint in ways that suit their own purposes. Even though two standards may use the same words, that doesn't mean that they are using them to mean the same thing. One way to think of it is to imagine that words like endpoint are qualified. So the first definition you quote is defining "endpoint-WS-Addressing", while the second is defining "endpoint-WSDL".
 
So there isn't a single thing called an endpoint. There are just a stack of definitions (unintended pun), each defining something different. Oh, there are some commonalities, but there are plenty of differences.
 
So yeah, I think it's apples and oranges (or maybe Apples and Sonys...)
 
Tony Rogers

	-----Original Message----- 
	From: public-ws-addressing-request@w3.org on behalf of Dan Diephouse 
	Sent: Sat 07-May-05 2:57 
	To: public-ws-addressing@w3.org 
	Cc: 
	Subject: endpoint terminology confusion
	
	


	I am becoming a little bit confused by WS-Terminology as of late, and I
	am hoping to clear up some confusion as to what exactly is meant by an
	"endpoint".  I'm not sure if this list is the best place to ask, but I
	don't know of a better one at the moment..
	
	In the WS-A proposal, an endpoint is defined as: "A Web service endpoint
	is a (referenceable) entity, processor, or resource where Web service
	messages can be targeted."
	
	And allow me to bring in the WSDL 2.0 definition for my question: "An
	endpoint associates a network address with a binding."
	
	I am confused about where the endpoint actually is in the stack. For
	example, SOAP is theoretically transport independent. I would define an
	endpoint as the transport agnostic part which processes the Envelope.
	Then I could theoretically share my soap service over many transports
	(http, smtp, etc).  But I could see how an endpoint could also be
	defined in such a way that it only has one address? Or does WS-A not
	even care - just as long as its referencable? Or am I comparing apples
	to oranges with the above definitions?
	
	Cheers,
	
	- Dan
	
	--
	Dan Diephouse
	Envoi Solutions LLC
	http://netzooid.com