W3C home > Mailing lists > Public > www-ws-arch@w3.org > October 2002

Re: what is discovery - One concrete proposal

From: Jeff Mischkinsky <jeff.mischkinsky@oracle.com>
Date: Wed, 09 Oct 2002 20:32:57 -0700
Message-Id: <4.3.2.7.2.20021009203248.01d5d910@gmamerimap.oraclecorp.com>
To: Dave Hollander <dmh@contivo.com>, www-ws-arch@w3.org

+1
    jeff

At 11:18 AM 10/9/2002, 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 Wednesday, 9 October 2002 23:34:50 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 3 July 2007 12:25:09 GMT