|
[EDI-L Mailing List Archive Home]
[Message List]
[Reply To This Message]
RE: The Ubiquity of XML - again.
It might be a good idea (just to make sure everyone's on the same page)
to point out that the concept of "well-formed" in the XML world is
purely a syntactical issue. If the <tags> are nested correctly and
balanced correctly by their closing </tags>, and if attributes that are
specified within tags are correctly coded with balanced quotation marks
around the values, then an XML document is well-formed. Once you get to
matching it against a DTD or schema, then you're talking about the
"validity" of an XML document. It is possible for an XML document to be
"well-formed" while at the same time it is not "valid." And if an XML
document does not make reference to a DTD or schema, there is no way to
determine if the XML document is "valid" or not.
Respectfully submitted,
Bill Chessman
Inovis(tm)
-----Original Message-----
From: Morrison, Martin [mailto:
Sent: Friday, February 04, 2005 12:14 PM
To: 'Earl Wertheimer'; Morrison, Martin;
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
.
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
|
 |
Subscribe in XML format
| RSS 2.0 |
|
| Atom 0.3 |
|
|
Cart
