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
- headers can have roles that the header is targetted at
- headers can be optional or mandatory
- 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.
- want to say anything about encodings?
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
>
>