Re: How to Create an ebXML Order (EDI 850 transaction set)

[Duane Nickull <duane@xmlglobal.com>]

John:

It does accomplish some of what you say however it falls short of
providing full ebXML complaint transaction sets.

On order to make use of the methodologies of ebXML,  such transaction
sets should facilitate a methodology whereby each component can
reference a metadata component in an ebXML Registry system.  XEDI fails
to make the grade here as do most other XML/EDI formats.  

The only way to build these transaction sets is to start with the Core
Components group then expand to define the messages built upon these
components.  This is the focus of a group lead by Jon Bosak with
deliverables of a stock set of business transactions.  The transactions,
in phase two, will also facilitate some degree of context derived
modifications at design time (and possibly at run time???).

For those wishing to transform X12 EDI 850 to XML, the process is easy. 
In fact,  XML Global publishes this as a simplistic web service.  We
also have an interface built over a server based system which can be
used today if you have the correct template and a valid input document.

http://demo.xmlglobal.com/transform/

I am working n a version that uses XMLG components to buidlthe output. 
If you want to give it a try,  ask me and I will post the two documents
to the list.

Duane Nickull 


John Evdemon wrote:
> 
> On Thursday, July 12, 2001 10:52 AM Bob Haugen  wrote:
> >
> > You can either use the X12 850 documents
> > with ebXML messaging service and business process specification,
> > or adopt an XML order document from one of the groups that is
> > closely related to ebXML, e.g. RosettaNet, Commerce One's xCBL,
> > OAG BODs, etc.  Check out the Catalog of Common Business Processes
> > for others:
> > http://www.ebxml.org/specs/bpPROC.pdf
> >
> Courtney,
> 
> You can also use the XEDI representation (www.xedi.org) since it includes
> every transaction, segment, element, loop, etc defined by every version of
> both EDIFACT and X12.  The other XML-based initiatives (listed above)
> provide adequate support, but are unable to represent all of the structures
> or elements that may appear within a typical 850 (making the mapping process
> somewhat difficult).   Mapping other transactions could prove to be even
> more difficult since these approaches might not provide a suitable XML
> representation.
> 
> The XEDI approach restores the human readable metadata defined by X12 (or
> EDIFACT) and provides an XML representation for any transaction, any version
> (again, X12 or EDIFACT).
> 
> ------------------------------------------------------------------
> The ebxml-dev list is sponsored by OASIS.
> To unsubscribe from this elist send a message with the single word
> "unsubscribe" in the body to: ebxml-dev-request@lists.ebxml.org

-- 
Duane Nickull, CTO - Founder
XML Global Technologies, Inc.
-----------------------------------
http://www.xmlglobal.com
http://www.goxml.com
http://www.xslt.com
-----------------------------------