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

RE: Web services Requirement at the client side in Orchestration

From: Assaf Arkin <arkin@intalio.com>
Date: Fri, 20 Dec 2002 08:10:29 -0800
To: "Pae Choi" <paechoi@earthlink.net>, <www-ws-arch@w3.org>
Message-ID: <IGEJLEPAJBPHKACOOKHNCEENCPAA.arkin@intalio.com>

Depends on what you are doing and how you define Web service.

If you are doing a B2B transaction you are probably going to have a Web
service of equal capacity on both the buyer and seller side so you can do
nitfy things like send messages in both directions using a variety of
protocols. (Think peer-to-peer)

But even if you are looking at the simplified B2C scenario where you use a
Web browser to access a shopping site, it still holds true. Your Web browser
and e-mail client are able to exchange XML messages over network protocols
so they can be considered Web services. Probably not as sophisticated,
scalable and hard to maintain as what the merchant is runnin, but still some
form of a Web service.

Basically, whatever you have on the buyer side that is capable of sending an
RFQ request to the seller and receiving an RFQ from the seller is a Web
service. And if it's as simple as an HTML form or e-mail, then you can
download your Web service for free. And if you want to interact with the
seller using SOAP, WS-Security, RM, you'll probably need a bit more than
that.

arkin

> -----Original Message-----
> From: www-ws-arch-request@w3.org [mailto:www-ws-arch-request@w3.org]On
> Behalf Of Pae Choi
> Sent: Thursday, December 19, 2002 12:18 PM
> To: www-ws-arch@w3.org
> Subject: Web services Requirement at the client side in Orchestration
>
>
>
> One quick question in [1]the Web Services Architecture as stated
> under the section, "3.3.3.2.2 Orchestration", as follows:
>
>
> 3.3.3.2.2 Orchestration
>
> <snip>
> "For example, the seller must have web services that receive request for
> quote (RFQ) messages, purchase order (PO) messages and payment
> messages. The
> buyer role must have Web services that receive quotes (RFQ response
> messages), invoice messages and account summary messages."
> </snip>
>
>
> How come the buyer(i.e., client) MUST have "Web services." The
> client should be able to acess and interact with Web sevices
> provided by the seller, i.e., the Web services provider, without
> having Web services at the client side. I cann't think of any
> scenario that the client, i.e., excluding the intermediary, need to
> have Web services. Any comments?
>
> Regards,
>
>
> Pae
>
>
> [1] http://www.w3.org/TR/2002/WD-ws-arch-20021114/#id2616565
>
>
Received on Friday, 20 December 2002 11:11:03 GMT

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