|
[EDI-L Mailing List Archive Home]
[Message List]
[Reply To This Message]
RE: X12 vs: XML File Sizes
Bill,
There are real world implementations of XML for data transport beyond
its use for web applications. Microsoft BizTalk needs XML schemas to
convert X12 to a usalble form, SAP has an XML interface, and a number of
companies are implementing the OAGIS schema. Yes, there are many XML
'standards' but no different from EDI.
Regards,
David Frenkel
Business Development
GEFEG USA
Global Leader in Ecommerce Tools
www.gefeg.com
425-260-5030
-----Original Message-----
From: Bill Chessman [mailto:
Sent: Friday, December 20, 2002 1:35 PM
To:
Subject: RE: [EDI-L] X12 vs: XML File Sizes
I agree with Rachel.
Which leads me to some other XML-related thoughts...
As far as XML "standards" are concerned, I would wonder exactly which
"standard" a person would convert X12 data to...? There is no approved
"standard" X12 XML definition as of yet (unless I'm hopelessly out of
touch...it could happen!).
There's a great quote that I think of often though I don't know the
original
source. It goes like this (approximately): "The best thing about
standards
is that there are so many to choose from." Whoever came up with the
remark
must have been thinking of XML. Everybody and their brother appears to
be
creating new XML "standards" though in reality the word "specification"
might be more accurate if perhaps overly optimistic. Anybody who
creates a
DTD can call it a "standard" and many do.
Having said that, the size of the expansion is going to depend in large
part
on your chosen "standard" design. Do you use long, "human readable"
tags?
Do you replace codes with human readable text? Do you rearrange the
data in
a way that makes it more "human readable" from a logical flow
perspective?
Do you use attributes to give enhanced meaning? I could go on and on...
Depending on which design features your "standard" has, the increase
could
be 2X, 10X, 50X...etc.
As a final question, assuming you're not using XML to transmit your
HIPAA
transactions, what are you using the XML for? Pretty displays?
Database?
Troubleshooting? The ability to claim bleeding-edge technology
adoption?
Okay, I guess this borders on a rant. But I feel better. Don't you?
8-)
Best regards,
Bill Chessman
Inovis(tm), Inc. (formerly Harbinger and Extricity)
(Insert standard disclaimer with respect to opinions expressed here.)
-----Original Message-----
From: Rachel Foerster [mailto:
Sent: Friday, December 20, 2002 1:10 PM
To:
Subject: RE: [EDI-L] X12 vs: XML File Sizes
Just keep in mind that the only "legal" data exchange format between
covered
entities for HIPAA transactions is according to the X12 specifications
embodied in the HIPAA guides adopted by the Department of Health and
Human
Services. No other exchange format, including XML, is allowed under
HIPAA.
So the issue of transaction volume bloat is a non-issue as far as HIPAA
transactions go.
Rachel Foerster
Principal
Rachel Foerster & Associates, Ltd.
Professionals in EDI & Electronic Commerce
39432 North Avenue
Beach Park, IL 60099
Voice: 847-872-8070
Fax: 847-872-6860
eMail:
http://www.rfa-edi.com
-----Original Message-----
From: OLIVOLA Peter [mailto:
Sent: Friday, December 20, 2002 2:16 PM
To:
Subject: RE: [EDI-L] X12 vs: XML File Sizes
Our experience in writing XML standards for a group of transactions,
using
the most efficient XML techniques, is that a document grows by a factor
of
10. This can be reduced a bit if you forego all visual formatting of
the
raw document and rely exclusively on screen/print templates for visual
presentation. However, at some point, it will be necessary to debug
document contents in raw form so this isn't a practical approach and it
creates documents that can be as arcane to read as X12.
If you are in any way bandwidth bound XML will be a major headache. If
you
have the bandwidth and don't already have a large investment in X12 it
will
be a faster implementation than trying to do X12. Converting from X12
to
XML is not easily cost justified. It usually happens for the same
reason
most people got into EDI in the first place; customer or regulatory
requirements.
Peter G. Olivola
Effective Data, Inc.
1515 E. Woodfield Rd.
Suite 770
Schaumburg IL 60173
847 969 9300
708 829 3185 (cell)
847 969 9350 (fax)
-----Original Message-----
From:
[mailto:
I know I've seen some posts in this forum, on this (way back), but am
looking for any real-world metrics now that we have more experience in
the
XML sub-genre.
I'm looking for information about how much, on average, a typical X12
file
grows when converted to XML. Specifically, for the HIPAA
implementations of
X12 transactions.
I'm hearing unqualified reports of 80% bloat which is a far cry from the
3000 percent growth I seem to recall from the previous discussions.
I think those earlier figures were based on ordered pair
implementations.
Any information would be greatly appreciated.
If you could qualify the information with which XML
implementation/schema/DTD is involved, that would be helpful.
To unsubscribe from this group, send an email to:
Message Identifiers: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>,
<OFF-TOPIC>
Access the list online at: http://groups.yahoo.com/group/EDI-L
Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/
To unsubscribe from this group, send an email to:
Message Identifiers: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>,
<OFF-TOPIC>
Access the list online at: http://groups.yahoo.com/group/EDI-L
Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/
|
 |
Subscribe in XML format
| RSS 2.0 |
|
| Atom 0.3 |
|
|
Cart
