- From: Colleen Evans <cevans@sonicsoftware.com>
- Date: Fri, 14 Feb 2003 09:32:36 -0700
- To: "Champion, Mike" <Mike.Champion@SoftwareAG-USA.com>
- Cc: www-ws-arch@w3.org
Mike, While I agree there's value in doing this for ebXML users and the community at large, I am concerned about the timing and scope. Where do we stop with the analysis of ebXML and WSA layering? Do we dig into BPSS and choreography as well? If we head in this direction we should carefully define and bound the exercise, or we'll get into the weeds and slow down our work on the architecture. I don't believe now is the right time to start this. Our document is in transition and we should get the core parts we've identified solid before we branch off onto something else. Can we put it on the list and prioritize? Thanks, Colleen "Champion, Mike" wrote: > I for one am a bit overwhelmed by the "layers" thread. What we need, and > which I think someone out there must have the ability to summarize, is a > paragraph or two on how messaging works in ebXML (all these acronyms such as > CPA are foreign to many of us!) and how that differs from the more typical > "stack" conception in various Web services architectures. > > I don't see any responses to Roger's > http://lists.w3.org/Archives/Public/www-ws-arch/2003Feb/0073.html > I'm especially interested in observations on his assertion that ebXML is > heavily oriented toward early-bound, "heavy" B2B/EDI operations whereas > typical Web services architectures are oriented toward late-bound and light > operations. This sounds plausible to me, is it more or less correct? > > Finally, I'd like to see suggestions for how to discuss this in the WSA > document. What properties, relationships, and constraints characterize ebXML > messaging? > > Thanks for helping to direct this very informative discussion in a direction > that is more useful to the WSA WG. > > Mike Champion
Received on Friday, 14 February 2003 11:31:02 UTC