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

RE: Discussion topic for tomorrow's call

From: Newcomer, Eric <Eric.Newcomer@iona.com>
Date: Thu, 27 Mar 2003 20:30:50 -0500
Message-ID: <DCF6EF589A22A14F93DFB949FD8C4AB2010740FB@amereast-ems1.IONAGLOBAL.COM>
To: "Jeckle, Mario" <mario@jeckle.de>, <www-ws-arch@w3.org>


Thanks very much for the comments.  I think your suggestions make sense.  But I have one question for you -- what about the transport layer?  Are you implying by omitting them from your diagram that they should be omitted from the stack diagram?  Or perhaps underneath everything?



-----Original Message-----
From: Jeckle, Mario 
Sent: Thursday, March 27, 2003 3:21 PM
To: www-ws-arch@w3.org
Cc: Newcomer, Eric
Subject: Re: Discussion topic for tomorrow's call


The picture looks good!
 From my point of view such a REC normative WSA stack diagram would be 
very useful.

I have only one concern with the placement of XSD. Should we really 
stack XSD above SOAP even when keeping in mind that SOAP's syntactic XML 
representation is described using XSD. This would justify to place SOAP 
on top of XSD.

Furthermore, we should perhaps consider to split the SOAP layer into 
SOAP base and SOAP extensions like sessions etc. which could be defined 
using SOAP's header mechanisms on top of the basis.

I attached a first draft illustrating my idea.


Newcomer, Eric wrote:
> Hi,
> I've been working on organizing principles for the document content, in 
> addition to the refactoring work we've been doing.  One of the ideas 
> that's been debated recently seems to make a lot of sense -- treating 
> Web services as applications of XML.  Focusing on the applications of 
> XML (i.e. SOAP, WSDL, UDDI, etc.) and not on the execution environment 
> (which is vendor specific) allows us to avoid some of the more 
> complicated issues around how Web services are executed, and concentrate 
> instead on describing how the XML applications work together and relate 
> to each other.
> Web services are not executable things per se, they are applications of 
> XML that are transformed and/or mapped to executable things.  Adopting 
> this principle may help organize the technical material better.  Anyway, 
> this is a topic for discussion during the call tomorrow.
> I've attached a draft of a stack diagram for the same purpose, to try to 
> visually depict the major topic areas that we need to address.  This 
> also suggests that we need to create major document sections for these 
> topics.
> During the editors' call today we discussed the following major 
> sections, and solicited volunteers for creating them:
> -- Introduction (David Booth)
> -- Concepts and Relationships (Frank)
> -- Messaging
> -- Management (Heather)
> -- Security (Abbie)
> -- Discovery (David Booth)
> -- Description/Orchestration/Choreography
> Let's talk about this tomorrow, see if there are volunteers for other 
> sections, etc.
> Regards,
> Eric
> Eric Newcomer
> Chief Technology Officer
> eric.newcomer@iona.com <mailto:eric.newcomer@iona.com>
> -------------------------------------------------------
> IONA Technologies
> 200 West Street Waltham, MA 02451 USA
> Tel: (781) 902-8366
> Fax: (781) 902-8009
> -------------------------------------------------------
> */Making Software Work Together/* TM
> ------------------------------------------------------------------------

Prof. Mario Jeckle
University of Applied Sciences Furtwangen
Dept. Business Applications of Computer Science
W3C Representative for DaimlerChrysler Research and Technology

URL: http://www.jeckle.de

My public key: http://www.jeckle.de/marioJeckle.pgp
Received on Thursday, 27 March 2003 20:31:07 UTC

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