RE: what is discovery - One concrete proposal

test clients are one example.
another example are work flow engines that invoke a service as an activity.

another one is the well defined, limited operation case... i.e. an
operation/message is supported
in many different portTypes and that is the only one that the client is
interested in.  The portType
changes depending on the target service, but the message sent doesn't. For
example...
getPriceQuote(item_upc_number, quantity) returns a float.  This operation
could be supported by
groceryStoreService, hardwareStoreService, carDealerService,
medicalSuppliesServices... etc.

Heather Kreger
Web Services Lead Architect
STSM, SWG Emerging Technology
[email protected]
919-543-3211 (t/l 441)  cell:919-496-9572


Ricky Ho <[email protected]>@w3.org on 10/11/2002 01:02:26 PM

Sent by:    [email protected]


To:    Ugo Corda <[email protected]>, Heather Kreger/Raleigh/IBM@IBMUS
cc:    [email protected]
Subject:    RE: what is discovery - One concrete proposal




Imagine the client application to be a web services browser that allows a
*human* to lookup what web service is available, pick one and invoke
it.  The naming convention, verbs .. etc is up to the human user to
interprete.

Ricky

At 09:01 AM 10/11/2002 -0700, Ugo Corda wrote:

> >2. The client discovers the interface specifics and the service instance
> >during runtime. In the deployments of this that I know of, they use a
DII
> >style interface, like the JAXRPC call object or the WSIF apis to figure
out
> >what message to create, create it and process the results.  There are
not
> >many of these out there.
>
>I am not surprised that there are not many of those out there. What
>surprises me is that there are any at all. How does a client application
>figures out the semantics of an interface it has never encountered before?
>It has to be something about very well delimited domains and very well
>defined naming conventions for verbs and parameters (or very familiar
>namespaces) ...
>
>Ugo