RE: Discussion topic for tomorrow's call

Hugo

I think the "envolope" of XML works well around the stack elements.

About routing  - Routing only aggregates services based on the
interaction and message path not in terms of any construct. It is truly
a "context" just like any other context that establishes a relationship
between participant services in a larger interaction model ( others are
correlation for process or other purposes, reliability, transaction,
security etc.).

Mark

> -----Original Message-----
> From: Hugo Haas [mailto:hugo@w3.org] 
> Sent: Thursday, April 03, 2003 5:18 AM
> To: Savas Parastatidis
> Cc: www-ws-arch@w3.org
> Subject: Re: Discussion topic for tomorrow's call
> 
> 
> * Savas Parastatidis <Savas.Parastatidis@newcastle.ac.uk> 
> [2003-04-02 23:29+0100]
> > You seem to have a separate layer for XML base technology, 
> which may 
> > suggest that only the messaging protocols use it. However, 
> XML schema, 
> > for example, is used throughout.
> > 
> > I would suggest that you either don't include the XML layer 
> at all and 
> > talk about its use by all the layers or make it vertical, like 
> > security and management.
> 
> How about having an XML big box in the background? I have did 
> a quick hack on Mario's diagram that I have attached, and 
> integrated my comments from my earlier email.
> 
> One thing what I was wondering about was the place of 
> routing: it is messaging extension, but it also serves to 
> aggregate services. I would be tempted to leave it out of the 
> picture at this point.
> 
> Regards,
> 
> Hugo
> 
> -- 
> Hugo Haas - W3C
> mailto:hugo@w3.org - http://www.w3.org/People/Hugo/
>

Received on Thursday, 3 April 2003 13:08:06 UTC