No, what you're reading is not the schema but very ugly, very bad XML. It has not only the values conveyed in the native X12 representation, but also the X12 metadata, i.e., the contents of X12 transaction set directory, segment directory, and element dictionary. The essential structure is something like:
<SegmentRef Pos="num" ID="tag" Description="la la la"> <Element Pos="num" ID="id" Description="la la" Type="data type" MinLength="num" MaxLength="num" Value="00"/> IMHO no one in their right minds would use this. Encode the essential, minimal metadata in the element or attribute names and just encode the values. A much more reasonable isomorphic representation (and there are dozens out there) would be something like: <?xml version="1.0" encoding="ISO-8859-1"?> <ISA> <ISA01>00</ISA01> <ISA02> </ISA02> <ISA03>00</ISA03> <ISA04> </ISA04> and so on. Contrast this with: <?xml version="1.0" encoding="ISO-8859-1"?> <EDI-X12-4010><Interchange-Control> <SegmentRef Pos="0" ID="ISA" Description="Interchange Control Header"> <Element Pos="01" ID="I01" Description="Authorization Information Qualifier" Type="ID" MinLength="2" MaxLength="2" Value="00"/> <Element Pos="02" ID="I02" Description="Authorization Information" Type="AN" MinLength="10" MaxLength="10" Value=" "/> <Element Pos="03" ID="I03" Description="Security Information Qualifier" Type="ID" MinLength="2" MaxLength="2" Value="00"/> <Element Pos="04" ID="I04" Description="Security Information" Type="AN" MinLength="10" MaxLength="10" Value=" "/> Not to keep beating this dead horse, but we should at least know we're beating something that was ready for the glue factory anyway instead of a Secretariat. ----------------------------------------- Michael C. Rawlins, Senior Software Engineer, GXS Sent from personal account On 7/1/2011 10:21 AM, socal_ediguy wrote: > > One other thing, though, to remember about the "length" of the > documents - the character counts... > > It appears that the original XML portion of the post shows the Schema > (needed to translate the data) and not just the data, and the EDI > shows only the data - not the mapping/translation guide.... > > >From what I remember about working with XML, you don't have the > Schema built into the data, but rather a second document (much like a > map)... > > Just two more cents... > > Craig Dunham > EDI Sherpa > SoCal EDI Guy > > --- In [email protected] <mailto:EDI-L%40yahoogroups.com>, "John" > <jmeyer2@...> wrote: > > > > Thanks for showing us that comparison, Neeraj. I don't think that I > have ever seen a clearer example of why XML will not and should not > replace EDI. Really... 3,172 characters to replace 165 in the EDI? (by > the way, I counted all 106 characters in the ISA, not just the ones > you typed). > > > > John Meyer > > CompuSolv > > > > ------------------------------------ ... Please use the following Message Identifiers as your subject prefix: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> Job postings are welcome, but for job postings or requests for work: <JOBS> IS REQUIRED in the subject line as a prefix.Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/EDI-L/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/EDI-L/join (Yahoo! ID required) <*> To change settings via email: [email protected] [email protected] <*> 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/
