emergency-msg — archive

[Art Botterell]

>Date: Tue, 29 Jul 2003 16:13:04 -0400 >From: "Ham, Gary A" <hamg@BATTELLE.ORG> >Subject: RE: [emergency-msg] FW: [ebxml-msg] UN/CEFACT Standard >Business Document Header Techn ical Specification Working Draft > >Art and Rick, >Please pass to your committees as desired (One day I will actually take the >time to fix my e-mail problem with OASIS.) > >Shall we get all wrapped up in wrappers for our wrapper's wrappers? This >definitely is a infrastructure issue which we should keep far away from CAP >and content issues in general until we better understand our specific >distribution model requirements. This document is very clearly a wrapper >spec ( and yes it would wrap the CAP message wrapper of CAP info elements in >another layer of distribution information). As a wrapper spec for the >general business environment, it provides a standard logical distribution >model that could be used for CAP and other EM-TC message content, so long as >that content works for the "Business Document" domain which basically >involves business transactions and notifications. It looks like it would be >very effective for any of our work that fits in the set of six (unless they >have been extended since I worked on them) basic business communication >patterns that form the foundation for the ebXML and RosettaNet business >communication models. > >Bottom line: I do not believe that it affects any of our content work. As >we get beyond XML Schema content into service definitions we may want to >provide example services that wrap EM-TC standards in Standard Business >Document Header format. > >Respectfully, > >Gary Ham > > >