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

Re: Artifacts in Requesters -- Simple Conventions for Diagrams

From: David Booth <dbooth@w3.org>
Date: Mon, 21 Oct 2002 01:28:18 -0400
Message-Id: <>
To: Heather Kreger <kreger@us.ibm.com>, www-ws-arch@w3.org

There are a couple things I find unclear about that diagram:

1. I think of "artifacts" as documents, or pieces of data -- not actors or 
components.  (This could just be confusion about terminology.)

2. I think it would be helpful to use different geometric symbols to more 
clearly distinguish between the actors (or roles or components) and the 
artifacts (or documents or data).  In particular, to distinguish between 
the Service Description (which is an artifact or document) and the Service 
(which is an actor).

I suggest using some simple conventions:

We don't have to use those particular conventions if people don't like 
them, but I do think: (a) we would achieve greater clarity by following 
SOME kind of conventions; (b) clarity is helpful; and (c) it isn't worth 
spending a lot of time selecting the conventions.

At 12:40 PM 10/16/2002 -0600, Heather Kreger wrote:
>It has come up in the Management Task Force calls that there is a need for
>an artifact in the
>Requester role to represent the 'code' that invokes the 'service' artifact
>in the Provider.
>I would like to propose that we add a new artifact called 'client' and
>place it with the Requester Role
>like Service is an artifact of Provider.
>So the triangle would look like:
>(See attached file: TriangleClient.jpg)
>Heather Kreger
>Web Services Lead Architect
>STSM, SWG Emerging Technology
>919-543-3211 (t/l 441)  cell:919-496-9572

David Booth
W3C Fellow / Hewlett-Packard
Telephone: +1.617.253.1273
Received on Monday, 21 October 2002 01:26:47 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:05:42 UTC