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

RE: Top cloud in triangle/rectangle diagram

From: Cutler, Roger (RogerCutler) <RogerCutler@ChevronTexaco.com>
Date: Mon, 7 Oct 2002 10:04:58 -0700
Message-ID: <7FCB5A9F010AAE419A79A54B44F3718E016245A7@bocnte2k3.boc.chevrontexaco.net>
To: "'David Booth'" <dbooth@w3.org>, "Sedukhin, Igor" <Igor.Sedukhin@ca.com>, www-ws-arch@w3.org
cc: "Cutler, Roger (RogerCutler)" <RogerCutler@ChevronTexaco.com>

Ah, now I see how my name got associated with this.

In fact -- yes, I strongly agree that the scenario that David describes in
http://lists.w3.org/Archives/Public/www-ws-arch/2002Oct/0072.html is likely
to be a VERY common, or even dominant one for businesses like us.  We tend
to know our business partners and deal directly with them, but
standardization of that interaction would be very helpful.  Discovery is not
an issue that keeps us awake at night very often, at least when one is
talking B2B interactions.  Now inside our intranet there might be a
different story.

-----Original Message-----
From: David Booth [mailto:dbooth@w3.org] 
Sent: Friday, October 04, 2002 8:06 PM
To: Sedukhin, Igor; www-ws-arch@w3.org
Cc: Cutler, Roger (RogerCutler)
Subject: RE: Top cloud in triangle/rectangle diagram


At 05:53 PM 10/4/2002 -0400, Sedukhin, Igor wrote:
>When a Service advertises itself to the Requestor, does it not play a 
>role
>of an Advertiser? Roles can collapse into one compound role, but from the 
>logical point of view they are still atomically separate in the
architecture.
>
>So, it seems that Slide 4 [at
>http://lists.w3.org/Archives/Public/www-ws-arch/2002Oct/0062.html ] says 
>that roles of Service and Advertiser are collapsed, and if the right 
>circle said Service/Advertiser it would be very valid interpretation of 
>the triangle. I don't think there is a contradiction with the triangle and 
>three roles in it.

Yes, I see what you mean.  You could describe it that way, but that's still 
assuming that the role of "Advertiser" is required as a significant 
architectural component.  It could be for a particular EXTENDED 
architecture, but I don't think it's needed or desirable for our BASIC 
architecture.  I think the scenario described in 
http://lists.w3.org/Archives/Public/www-ws-arch/2002Oct/0072.html helps 
make this clearer.  (That scenario was actually inspired by the business 
need that Roger Cutler described at our last F2F, incidentally.)


-- 
David Booth
W3C Fellow / Hewlett-Packard
Telephone: +1.617.253.1273
Received on Monday, 7 October 2002 13:05:15 GMT

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