RE: Action 2003-01-21 for Umit

> -----Original Message-----
> From: Umit Yalcinalp [mailto:umit.yalcinalp@oracle.com] 
> Sent: 27 February 2003 17:29
> To: Martin Gudgin
> Cc: www-ws-desc@w3.org
> Subject: Re: Action 2003-01-21 for Umit

<SNIP/>

> Before starting to debate the rest, lets agree on the common 
> assumptions first. 
> 
> In the January f2f, the idea explored was that when a single 
> schema replaces the message construct, the concept of parts 
> was going to be moved from the abstract to the concrete 
> binding. For some of us, having *multiple* parts is necessary 
> in the binding. 

By which you mean what? Surely a binding just describes concretely what
a message looks like on the wire... Are you just asking for the ability
to say 'this element goes in the body, that element goes in a header'?
Or 'this element goes in the body, that element goes as an attachment'?
Or are you asking for more than that?

> So the exercise was to come up with schema 
> examples and explore how they will exhibit themselves in the binding!

That much I understood, but the discussion of 'parts' confused me.


> 
> Given this assumption, the idea is to explore how the parts 
> are going to reappear in the binding as they would be 
> dissappearing from the abstract. So a "mapping" is necessary.

So, hopefully, by 'mapping' you mean specifying which
elements/attributes go where...

> 
> My task was to present complex schema examples. You guys were 
> going to show the mapping in the binding. Am I missing something?

Obviously I was... 

Gudge