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: Wed, 9 Apr 2003 16:42:13 -0400
Message-ID: <DCF6EF589A22A14F93DFB949FD8C4AB201074254@amereast-ems1.IONAGLOBAL.COM>
To: "Hugo Haas" <hugo@w3.org>
Cc: "Jeckle, Mario" <mario@jeckle.de>, "Champion, Mike" <Mike.Champion@SoftwareAG-USA.com>, <www-ws-arch@w3.org>, <Savas.Parastatidis@newcastle.ac.uk>, <RogerCutler@chevrontexaco.com>


I agree completely that we need to include clarifying text with the diagram to address issues such as the relationship between SOAP and HTTP and why HTTP is placed in the transport box, absolutely.

No diagram is going to be perfect so yes, the accompanying text will be very important to the success of any diagram.  In that context we probably will not be able to completely agree on the diagram until we see it in the document with the accompanying text.  

We will certainly have more opportunities to review/comment/propose changes in that context.


-----Original Message-----
From: Hugo Haas [mailto:hugo@w3.org]
Sent: Wednesday, April 09, 2003 12:26 PM
To: Newcomer, Eric
Cc: Jeckle, Mario; Champion, Mike; www-ws-arch@w3.org;
Savas.Parastatidis@newcastle.ac.uk; RogerCutler@chevrontexaco.com
Subject: Re: The stack diagram (was RE: Discussion topic for tomorrow's

* Newcomer, Eric <Eric.Newcomer@iona.com> [2003-04-09 11:08-0400]
> This would be much clearer and more useful without the protocol binding box extending into the SOAP area.  Representing the major concepts clearly in a diagram should be the goal rather than including every detail in the diagram.  
> We want to provide someone with a visual understanding of the architectural framework, meaning primarily what is included within it, and represent *to some extent* the relationships among the major pieces.  
> Drawing the line between what is clear and general and specific and confusing is never easy, and no doubt we will have many opinions.  
> I'd like to propose that we adopt this version of the diagram, without the protocol binding part, and move on.

I think that it all comes down to knowing how many diagrams we need to
represent our space, so that each diagram is reasonnably simple and

We need to address the fact that HTTP without SOAP may be used to do
some requests, such as with the SOAP 1.2 HTTP GET binding.

This is why I am worried about showing HTTP in the transport box
without any link to the message box. I think that I could live with
this diagram if there was some text accompanying it talking about

And in this case we should also add some explanation about why HTTP is
in a box called transport, otherwise I foresee comments about that.



Hugo Haas - W3C
mailto:hugo@w3.org - http://www.w3.org/People/Hugo/
Received on Wednesday, 9 April 2003 16:42:42 UTC

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