W3C home > Mailing lists > Public > www-ws-arch@w3.org > April 2003

RE: The stack diagram (was RE: Discussion topic for tomorrow's call)

From: Newcomer, Eric <Eric.Newcomer@iona.com>
Date: Thu, 3 Apr 2003 13:30:40 -0500
Message-ID: <DCF6EF589A22A14F93DFB949FD8C4AB20138E05A@amereast-ems1.IONAGLOBAL.COM>
To: "Champion, Mike" <Mike.Champion@SoftwareAG-USA.com>, <www-ws-arch@w3.org>


I'd really like to adopt Mario's version of the current stack diagram as the way we visually represent the relationship among the various specifications we include in the architecture.

The other three-stack diagram is useful more for the purpose of representing some kind of flow between the major functional areas during execution.  And I'd like to try to postpone that kind of diagram for a later exercise, after we can gain agreement on the current stack diagram proposal.

Does that make sense?  The original three-stack diagram includes flow arrows, which I interpret as indicative of execution flow, or execution time relationships.  This is something different to me than an architectural layering diagram that is meant to depict layers of abstraction rather than execution time relationships.

Neither one can show everything, and neither probably can do the entire job.  What I'd like to propose therefore is concentrating on the abstract layering diagram initially, and then coming back to the three-stack diagram in the context of how to represent the execution time relationships.


-----Original Message-----
From: Champion, Mike 
Sent: Thursday, April 03, 2003 9:51 AM
To: www-ws-arch@w3.org
Subject: The stack diagram (was RE: Discussion topic for tomorrow's

> -----Original Message-----
> From: Hugo Haas [mailto:hugo@w3.org]
> Sent: Wednesday, April 02, 2003 10:33 AM
> To: Newcomer, Eric
> Cc: Jeckle, Mario; www-ws-arch@w3.org
> Subject: Re: Discussion topic for tomorrow's call
> * Newcomer, Eric <Eric.Newcomer@iona.com> [2003-04-02 10:01-0500]
> > Regarding security, it was positioned as an "orthogonal" 
> (maybe not exactly the right term) concept, meaning it 
> applies to all layers, as does management.
> > 
> > I am not sure it is helpful to additionally list it in any 
> of the layers since the right hand security box is intended 
> to imply that security applies to all layers.  This would 
> have to be explained in accompanying text.

We had a "3 stack"  diagram in an earlier version of the WSA document:
http://dev.w3.org/cvsweb/~checkout~/2002/ws/arch/wsa/3Stack.gif that I think
provides a better visual framework than what we are talking about here.
http://lists.w3.org/Archives/Public/www-ws-arch/2003Apr/0002.html  I agree
with the comments about security and management being orthogonal, but I like
the way the old diagram strung messaging, description, etc. horizontally.

I also like the suggestion that the XML Base Technology be a "backplane" or
"foundation" (depending on how we draw the diagram) behind or under

I'll see if I can somehow render my thoughts ...

Anyway, for the telcon today, it would be very good if people who want to
propose a picture have one prepared and on the web (or in the archive, of
course) so that they can paste the URL into IRC so that we can look at them
in real time.  
Received on Thursday, 3 April 2003 13:31:02 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:41:06 UTC