I think there is many aspects of XML that are appealing. I would say that all
in all the benefit of XML at the core from a programmers perspective is the
standardized
agreement to markup the data in ASCII TEXT. While in times past companies would
use a number of proprietary formats that complicated any integration process
enormously.
If a company at least chooses to make there data available in standard XML
markup
at least any entry level programmer could work with and use the data
effectively, using a DOM,SAX or RUPU parser based solution without your
cooperation or specifically customizing the data for each partner.
Mike
Steve Bell wrote:
> Very good point Georges. If XML allows many tags to be inserted into a
> document then you have many standards for many customers, because each
> customer will be different. Can anyone explain how this is a voided? We
> are going to XML for one of our customers. I just dont see the advantage.
>
> Steven Bell
>
> -----Original Message-----
> From: Brigham, Georges [mailto:[EMAIL PROTECTED]]
> Sent: Friday, June 22, 2001 11:36 AM
> To: 'bobcarper'; [EMAIL PROTECTED]; Ben Marchal (Mailing Lists)
> Subject: RE: EDI Messages in XML
>
> Just for the record, you use the 824 - Application Advice to report problems
> with the "contents" of a document. The 997 concerns a "group" of documents
> and, at most, lets you reject one or more documents in the group for
> syntactical reasons. These tend to occur at first use of EDI, but get
> cleaned up quickly. the contents could cause problems any time.
> If a hundred people send you XML documents, what do they use as standards,
> both format and labels? Or do you have fun matching one on one? Doesn't
> sound very practical to me.
> Georges Brigham
>
> -----Original Message-----
> From: bobcarper [mailto:[EMAIL PROTECTED]]
> Sent: Friday, June 22, 2001 12:02 PM
> To: [EMAIL PROTECTED]; Ben Marchal (Mailing Lists)
> Subject: Re: EDI Messages in XML
>
> Hi all .......
>
> Let me put in my opinion's worth on this one, and risk being assailed as
> someone coming from an untried and untested position. I have accumulated a
> good half semester's worth of information, experience, and data elements
> conversion problems related to my client's requirement to be HIPAA compliant
> by the Year 2002. It is my belief that different trading partners need not
> be on the same protocol (Standard, version, etc.). However, there must be a
> data element conversion and formatting analysis performed prior to any data
> interchange, and that this data analysis must reflect the protocol
> regulations, while at the same time preserving the data element meaning and
> coding representation. In other words, it is entirely feasable for Trading
> Partner A to send as an outbound transaction set an ANSI X12 837 (Health
> Care Claim), receive a 997 from Trading Partner B that the transaction set
> was received. Now if the map called for translating the 837 into a
> designated XML schema, then Trading Partner B would have, upon successful
> translation, a Health Care Claim data file in its own XML format. However,
> the data element conversions would have to be addressed prior to the
> mapping operation, complete with all coding representations and formatting
> conventions. Also, any improper translations would have to be conveyed back
> to Trading Partner A in the 997 that would be returned.
>
> It is therefore possible to go from any convention to any convention.
> Trading partners need not be on the same convention, standard, and version.
> The point I am making is that such an analysis be done prior to any
> translation or map, particularly in applications which have their origins
> from very dissimilar sources, such as the healthcare industry.
>
> Now I will stand back on the stage and dodge the brickbats
> .......................
>
> Cheers
> Bob Carper
> ----- Original Message -----
> From: "Ben Marchal (Mailing Lists)" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Friday, June 22, 2001 07:35
> Subject: Re: EDI Messages in XML
>
> > At 01:34 22/06/01, [EMAIL PROTECTED] wrote:
> > >Where you say that using XML is like being part of a community - do you
> > >mean that every organisation with whom you wish to conduct business
> > >electronically needs to also use XML. For example, if I want to exchange
> > >data with others within the Health Industry (ie. medical practitioners,
> > >hospitals, ancillary providers (ie. dentists, physiotherapists etc.) and
> I
> > >want to use an XML protocol, does everyone else have to use XML as well.
> > >Alternatively, can I use XML while my partners continue to use EDIFACT.
> >
> > We're going through a period of transition so it's not uncommon to work in
> > a mixed mode where some partners use XML and others EDIFACT.
> >
> > We see that a lot where a company opens up to new partners or new
> > applications; for reasons I explained previously, they adopt XML but they
> > retain their EDIFACT solution (or build an EDIFACT compatibility mode in
> > the new one) for existing partners/applications.
> >
> > --ben
> >
> > New! XML and the Enterprise at www.marchal.com
> > "The model adds significantly to the technology's understanding and use."
> > -- Bruce Peat, chair; XML/edi Group
> >
> >
> >
> > ------ XML/edi Group Discussion List ------
> > Homepage = http://www.XMLedi-Group.org
> >
> > Unsubscribe = send email to: [EMAIL PROTECTED]
> > Leave the subject and body of the message blank
> >
> > Questions/requests: [EMAIL PROTECTED]
> >
> > To receive only one message per day (digest format)
> > send the following message to [EMAIL PROTECTED],
> > (leave the subject line blank)
> >
> > digest xmledi-group your-email-address
> >
> > To join the XML/edi Group complete the form located at:
> > http://www.xmledi-group.org/xmledigroup/mail1.htm
> >
> >
>
> ------ XML/edi Group Discussion List ------
> Homepage = http://www.XMLedi-Group.org
>
> Unsubscribe = send email to: [EMAIL PROTECTED]
> Leave the subject and body of the message blank
>
> Questions/requests: [EMAIL PROTECTED]
>
> To receive only one message per day (digest format)
> send the following message to [EMAIL PROTECTED],
> (leave the subject line blank)
>
> digest xmledi-group your-email-address
>
> To join the XML/edi Group complete the form located at:
> http://www.xmledi-group.org/xmledigroup/mail1.htm
>
> ------ XML/edi Group Discussion List ------
> Homepage = http://www.XMLedi-Group.org
>
> Unsubscribe = send email to: [EMAIL PROTECTED]
> Leave the subject and body of the message blank
>
> Questions/requests: [EMAIL PROTECTED]
>
> To receive only one message per day (digest format)
> send the following message to [EMAIL PROTECTED],
> (leave the subject line blank)
>
> digest xmledi-group your-email-address
>
> To join the XML/edi Group complete the form located at:
> http://www.xmledi-group.org/xmledigroup/mail1.htm
>
> ------ XML/edi Group Discussion List ------
> Homepage = http://www.XMLedi-Group.org
>
> Unsubscribe = send email to: [EMAIL PROTECTED]
> Leave the subject and body of the message blank
>
> Questions/requests: [EMAIL PROTECTED]
>
> To receive only one message per day (digest format)
> send the following message to [EMAIL PROTECTED],
> (leave the subject line blank)
>
> digest xmledi-group your-email-address
>
> To join the XML/edi Group complete the form located at:
> http://www.xmledi-group.org/xmledigroup/mail1.htm
------ XML/edi Group Discussion List ------
Homepage = http://www.XMLedi-Group.org
Unsubscribe = send email to: [EMAIL PROTECTED]
Leave the subject and body of the message blank
Questions/requests: [EMAIL PROTECTED]
To receive only one message per day (digest format)
send the following message to [EMAIL PROTECTED],
(leave the subject line blank)
digest xmledi-group your-email-address
To join the XML/edi Group complete the form located at:
http://www.xmledi-group.org/xmledigroup/mail1.htm
