Re: what is discovery - One concrete proposal

+1

Mark Jones
AT&T

	From [email protected] Wed Oct  9 14:24 EDT 2002
	Delivered-To: [email protected]
	X-Authentication-Warning: mail-red.research.att.com: postfixfilter set sender to [email protected] using -f
	Resent-Date: Wed, 9 Oct 2002 14:24:19 -0400 (EDT)
	Resent-Message-Id: <[email protected]>
	From: Dave Hollander <[email protected]>
	To: [email protected]
	Date: Wed, 9 Oct 2002 11:18:49 -0700 
	MIME-Version: 1.0
	Subject: what is discovery - One concrete proposal
	Resent-From: [email protected]
	X-Mailing-List: <[email protected]> archive/latest/2932
	X-Loop: [email protected]
	Resent-Sender: [email protected]
	List-Id: <www-ws-arch.w3.org>
	List-Help: <http://www.w3.org/Mail/>
	List-Unsubscribe: <mailto:[email protected]?subject=unsubscribe>
	X-Spam-Status: No, hits=0.0 required=5.0 tests= version=2.20



	To try to get temporary closure on the discovery,triangle, 
	and cloud, let me try to state one position.  

	Recommendation:
	1. Leave it in the spec dract as is or ammended with axioms 
	   from below.

	2. Add an example where "discovery" is a trivial role because
	   there are two parties directly exchanging information that
	   is hardwired into the service.

	3. Label the node "Discovery Agencies"

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

	Discovery = exchange of the service description details necessary 
	to make a conncection.

	Discovery Axioms: 

	1) discovery need not rely upon formal documents.
	 
	2) discovery occurs regardless of when the discovered 
	    information is bound into the connection (early or late).
	 
	3) discovery is discovery regardless if the provider or 
	    requestor does the advertising.

	4) discovery is discovery even if the data discovered was
	    already known. All that needs to be true is the potential
	    that the data *may* be different or new.

	5) discovery is discovery even if there are only two parties,
	    requestor and provider.


	I believe that "discovery", as defined above, exists as a 
	role in all of the scenarios that have been presented here.

	So that leads to the question: is "discovery", as defined above,
	relevent enough to be included in our base architecture?

	I believe discovery is relevent and should be in the
	base architecture for the following reasons:

	1. the distinction between hypertext and web services
	   web has hypertext links to create a network, web
	   services currently do not have a mechanism for defining
	   a newtwork.

	2. good for the "ilities" (scalability, reliability, etc)

	3. it always happens, just sometimes it is done outside
	   of the system.

	4. Most people expect to see it. If it is not there, our
	   audience will either be disappointed or will try to find
	   it. Either way confusion and mixed understanding will result.