Does anybody have experience with using JSON as a inhouse format? For JSON see http://www.json.org The format is quite close to the data types supported by a lot of programming languages. There are enough libraries to read a JSON file.
In my experience most mapping of edi files is to 'fixed file format' (a sequence of fixed records). But the fixed file format is not very flexible; JSON does seem to be more flexible eg extent a record (they call it 'object') without consequences for the processing application. In a way it reminds of XML but it is much simpler and quite similar to data types of a programming language. In my experience processing XML is not that easy (somebody referred to this as 'doing XML sit-ups'). kind regards, Henk-jan Ebbers bots open source edi translator: http://bots.sourceforge.net ... 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: mailto:[EMAIL PROTECTED] mailto:[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/
