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 [EMAIL PROTECTED] http://www.spe-edi.com . Please use the following Message Identifiers as your subject prefix: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> Access the list online at: http://groups.yahoo.com/group/EDI-L Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/EDI-L/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
