[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Fwd: RE: FW: [ebxml-msg] UN/CEFACT Standard Business DocumentHeader Technical Specification Working Draft
>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 > > >-----Original Message----- >From: Aerts, John F. [mailto:jfaerts@lasd.org] >Sent: Tuesday, July 29, 2003 1:22 PM >To: emergency-msg@lists.oasis-open.org >Cc: 'emergency-if@lists.oasis-open.org' >Subject: [emergency-msg] FW: [ebxml-msg] UN/CEFACT Standard Business >Document Header Techn ical Specification Working Draft > > >How will this Common Header work effect CAP and the work of the EM TC? > >John Aerts > > >-----Original Message----- >From: Doug Bunting [mailto:Doug.Bunting@Sun.COM] >Sent: Monday, July 28, 2003 9:48 PM >To: ebXML Messaging >Subject: [ebxml-msg] UN/CEFACT Standard Business Document Header Technical >Specification Working Draft > > >This is a memory from our meeting in San Diego. The Common Header work >has progressed to the public comment phase in its development. > >I have not yet reviewed the documents available at [1] but suggest at >least one or two of us do so. We may also wish to submit "official >(agreed) TC" comments rather than individually. The site includes a >specific email address and comment form for submission. > >thanx, > doug > >[1] http://webster.disa.org/cefact-groups/atg/downloads/index.cfm > > > >You may leave a Technical Committee at any time by visiting >http://www.oasis-open.org/apps/org/workgroup/ebxml-msg/members/leave_workgro >up.php > >--------------------------------------------------------------------- >To unsubscribe, e-mail: emergency-msg-unsubscribe@lists.oasis-open.org >For additional commands, e-mail: emergency-msg-help@lists.oasis-open.org
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]