[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: [ebxml-dev] Core Components
Thanks all, I am designing our process to use ebXML to transport, route, package BODs (as payload) and was curious if that was overkill. Tony -----Original Message----- From: Andrzej Jan Taramina [mailto:andrzej@chaeron.com] Sent: Wednesday, November 20, 2002 2:00 PM To: ebxml-dev@lists.ebxml.org Subject: Re: [ebxml-dev] Core Components Farrukh said: > Again lay opinion to be used with care... > > cc are not based directly on OAG BODs though I suspect that the BOD work > was part of the rich experience base that the CC team built upon. The way I've understood it is that OAG BOD's are one level up in the "ebXML evolutionary scale", since they are complete payload definitions (business document definitions like Purchase Orders, ASN's, etc.). Core Components would typically be finer grained, more like field definitions, and be used in a mix 'n match fashion to create new payload document definitions (eg. Amount field, Tax field, etc...) So in a sense, CC's would be the "raw" ingredients that could be used to create new BOD's. Note: Current OAG BOD's do not use ebXML CC's. This example is just for illustration. Andrzej Jan Taramina Chaeron Corporation: Enterprise System Solutions http://www.chaeron.com ---------------------------------------------------------------- The ebxml-dev list is sponsored by OASIS. To subscribe or unsubscribe from this elist use the subscription manager: <http://lists.ebxml.org/ob/adm.pl>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC