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

RE: SOAP UML diagram

From: Martin Chapman <martin.chapman@oracle.com>
Date: Wed, 4 Jun 2003 12:23:35 -0700
To: "David Orchard" <dorchard@bea.com>, <www-ws-arch@w3.org>
Message-ID: <PEEBJKKCFNCENDPJDEMIGEJGDEAA.martin.chapman@oracle.com>



> -----Original Message-----
> From: David Orchard [mailto:dorchard@bea.com]
> Sent: Wednesday, June 04, 2003 11:16 AM
> To: 'Martin Chapman'; www-ws-arch@w3.org
> Subject: RE: SOAP UML diagram
>
>
> Hey, I like that!  A lot!  Imagine once we get this merged with WSD uml
> diagram, then we'll be playing with gasoline.
>
> Some comments:
> - I believe that a body is a header that is targetted at the ultimate
> receiver

The 1.2 doc doesn't really say that, and makes a point at keeping the header
and body concepts quite separate.
Looking at the rules for the contents, both are identical except that
headers may have role, mustunderstand and relay attributes.
From a modelling perspective this actually makes a header a subclass of
body!!!! Since thats not really how its presented in 1.2 I suggest we
avoid this trout!

> - headers can have roles that the header is targetted at

I will add an attribute in the header class, and if it makes sense (i.e.
adds value without confusing the diagram) the roles can be related to the
node classes.

> - headers can be optional or mandatory

I will add an attribute in the header class

> - As for features, why not start with something simple like:
>   - a feature can be realized as an mep, by a binding, or by an module
>   - a collection of 2 or more messages can be an mep
>   - a module is a header
>   - a message has a binding to a protocol.
>   - not sure quite how to express properties.  Perhaps we could say that
> messages have metadata, and metadata and messages are properties?  There's
> the "extra information items" that can be properties that are a
> little hard
> for me to express.

Thanks for the suggestions.

> - want to say anything about encodings?

Probably!
>
> Cheers,
> Dave
>
> > -----Original Message-----
> > From: www-ws-arch-request@w3.org [mailto:www-ws-arch-request@w3.org]On
> > Behalf Of Martin Chapman
> > Sent: Wednesday, June 04, 2003 10:52 AM
> > To: www-ws-arch@w3.org
> > Subject: SOAP UML diagram
> >
> >
> >
> >
> > I had an action point from the F2F to draw a uml diagram of
> > soap. Here's a
> > first cut at the basics. I need to think about how features
> > and the binding
> > framework fit in (if at all).
> >
> > http://lists.w3.org/Archives/Public/www-archive/2003Jun/att-00
> > 09/Soap_Uml.pn
> > g
> >
> > Martin.
> > _________________________________________________________________
> > Martin Chapman                                 500 Oracle Parkway
> > Consulting Member of Technical Staff           Ms 4op990
> > Oracle                                         Redwood Shores,
> > P: +1 650 506 6941                             CA 94065
> > e: martin.chapman@oracle.com                   USA
> >
> >
>
>
Received on Wednesday, 4 June 2003 15:26:23 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 3 July 2007 12:25:20 GMT