On Aug 26, 2010, at 3:54 PM, Patrice Krakow wrote: > First of all, many thanks for your feed-back.
Patrice, You're welcome. > I have also noticed that they were using "UNOA" with lower case characters :-/ Seagate is not the only one who uses lower case characters with UNOA instead of UNOB, something most implementers ignore. > <int:UNA> > <int:UNB> > <int:UNH> > <ORDERS.D.97A xmlns="http://parse-EDIFACT.net/Message/1/> > <BGM> > > What do you think? > > - My philosophy is to name the tag by following exactly the EDIFACT > specifications, the only needed "customization" is the character to be put in > front of simple element, since a XML tag cannot start with a digit, then my > heart balances between "_" and "E" ;-) My philosophy is not to reinvent things, therefore I adopted the basic tag naming rules of ISO/TS20625 which are: The names of the XML structure will be derived from the EDI tags. They will be given a prefix depending on the structure level (segment group, segment, composite data element or data element): „M_“+ message type => Example: M_ORDERS „G_“+ segment group => Example: G_SG36 „S_“+ segment => Example: S_LIN „C_“+ composite data element => Example: C_C082 „D_“+ data element => Example: D_3035 ------- I don't need the segment group tag, within the instant of an interchange. I also reframed from using attributes with in thew XML Tags since that information does not exist in the original EDIFACT interchange, everything that is within the EDIFACT segments is within the XML elements. Your example would than look like this: <INTERCHANGE> <S_UNA>:+.? '</S_UNA> <S_UNB> <C_S001> <D_0001>UNOB</D_0001> <D_0002>2</D_0002> </C_S001> <C_S002> <D_0004>IRONWARE</D_0004> <D_0007>ZZ</D_0007> </C_S002> <C_S003> <D_0010>098533326</D_0010> <D_0007>ZZ</D_0007> </C_S003> <C_S004> <D_0017>011107</D_0017> <D_0019>1500</D_0019> </C_S004> <D_0020>186</D_0020> </S_UNB> <M_ORDERS> <S_UNH> <D_0062>72</D_0062> <C_S009> <D_0065>ORDERS</D_0065> <D_0052>D</D_0052> <D_0054>97A</D_0054> <D_0051>UN</D_0051> </C_S009> </S_UNH> <S_BGM> <C_C002> <D_1001>220</D_1001> </C_C002> <D_1004>123350</D_1004> <D_1225>9</D_1225> </S_BGM> <S_DTM> <C_C507> <D_2005>4</D_2005> <D_2380>20011107</D_2380> <D_2379>102</D_2379> </C_C507> </S_DTM> NOTE: Too bad Yahoo strips leading white spaces from the above example :-( Regards, Klaus ------------------------------------ ... 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/
