Re: what is discovery - One concrete proposal

A SOAP client may use a service where the service information is 
obtained out of band (e.g. it may be precompiled into the 
client). Is this supported by your current definition or are you 
implying that discovery is mandatory (I don't read anything like 
discovery is optional)?

Jean-Jacques.

Dave Hollander wrote:
> 
> 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.
> 
> 
> 
>

Received on Friday, 11 October 2002 02:42:28 UTC