Re: Words for the Triangles

On Wed, Sep 25, 2002 at 08:18:47PM +0200, Hugo Haas wrote:
> I wouldn't list UDDI here: it hints that the "common
> program-to-program communication model" is based on a centralized
> registry.

+1!!

> Something is coming back to my mind: I see Web services (you can guess
> here my favorite spelling) spelled [Ww]eb [Ss]ervices. It would be
> good to have a consistent use of those words in the architecture
> document, and elsewhere too actually. Web refers to the World Wide Web
> is therefore "Web"; I think the issue is with "[Ss]ervices".
> 
> I don't mean to start a huge debate here, just raise the issue.

FWIW, I prefer "Web services" too.

> 
> I would just reference the one we agreed upon for now here.
> 
> [..]
> > The Web Services Oriented Architecture Model
> > 
> >    The web service architecture based upon the interactions between three
> >    roles: service provider, service discovery agency, and service
> >    requestor.
> 
> You were saying that you had issues finding a good way to call the
> discovery part. I have the feeling that it actually may not be easily
> described in terms of role.
> 
> In terms of abstract entities here, there is the provider and the
> consumer. The discovery is something which happens between the two of
> them, directly or indirectly. I would therefore suggest simply talking
> about "discovery mechanisms".

Hmm, yes, that seems much better to me.

> I would try to reword this, following my idea, as:
> 
>   Discovery mechanisms: this is a set of mechanism for the service
>   requestor to become aware of the service provider and of how to
>   invoke the service. Service requestors find services and obtain
>   binding information (in the service descriptions) for services
>   during development for static binding, or during execution for
>   dynamic binding.

"in the service descriptions" may not be accurate for dynamic binding.
With dynamic binding, the URI scheme is all the information you need.

> > Operations in a Web Service Architecture
> [..]
> >    The description of your service is used to publish it in a registry,
> >    directory, or repository of service descriptions. After publication,
> >    the registry also has a copy of your service description. At some
> >    later time, a service requestor needs to use a service just like
> >    yours. The service requestor, or client, finds your service in the
> >    registry and retrieves the WSDL from the registry.
> 
> This is a centralized view of the discovery step. I think that this
> could be changed by something like the "requestor somehow has access
> to the service description".

+1

MB
-- 
Mark Baker, CTO, Idokorro Mobile (formerly Planetfred)
Ottawa, Ontario, CANADA.               [email protected]
http://www.markbaker.ca        http://www.idokorro.com