[EDI-L Mailing List Archive Home] [Message List] [Reply To This Message]

RE: The Ubiquity of XML - again.

From: "Morrison, Martin" <Martin.Morrison@...>
Date: Fri Feb 4, 2005  8:13 pm
Subject: RE: [EDI-L] The Ubiquity of XML - again.
Earl

> Tools already exist to check HTML which is already very similar.

Then there's that nasty "well-formed" clause.
I've tried some of the online stuff with results that are all over the
board.

> Yes. So it's time to upgrade your hardware.

I had to work with an 837 file a few weeks back that was almost 300
megabytes.
UltraEdit was the tool of choice, did get the job done, but took a while.
Let's bump that file up to XML (Using the most conservative "X12 look-alike"
schema) and you're looking at roughly a 9 gig file.
How much memory do you have?

Martin


-----Original Message-----
From: Earl Wertheimer [mailto: Sent: Friday, February 04, 2005 11:44 AM
To: Subject: RE: [EDI-L] The Ubiquity of XML - again.


Martin

> We see this kind of corruption, usually related to intersystem
> communication, in most all the traditional EDI file types in use
> today. When the data gets corrupted in one of the traditional formats,
> it's usually a simple matter to open it and see what went awry. If an
> XML file is no longer "well-formed", what is the procedure for
> identifying the problem? (Assuming none of the XML
> parsers/viewers/editors are able to work with it).

I would assume (already I'm treading on thin ice here), that the editor
could
point out where the error is possible located. It would actually be easier
than in an X12 document, since all the data is surrounded by <tag> </tag>.
The error would be found at the location of the first mismatched set of
tags.

Tools already exist to check HTML which is already very similar.

> Many of the text editors I've used work acceptably on traditional
> files, but start to labor on the larger ones. They'd be brought to
> their knees on the same files represented in XML.

Yes. So it's time to upgrade your hardware.

"Processing requirements expand to fill existing hardware capabilities" ;-)

Earl Wertheimer
http://www.spe-edi.com



 
EDI to XML Mapping for EDIFACT/X12 Convert EDIFACT/X12 Schemas to XML Schema Legacy Data Conversion Tools Access Relational Data as XML Visual XSLT and XQuery Mapping Tools Simplify EDI Data Integration with Stylus Studio XML Enterprise Suite - Free Download!
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2007 All Rights Reserved.