Interesting idea, and very valid points. However I would consider a few other things before deciding on JSON over XML.
XML simply has too much stamina and support, including tools and software support. Also consider some of the technologies such as XQuery and XML Databases. If you were setting up an ESB type hub, and converted all your EDI messages to XML in the hub. Then you could easily save each of these documents to an XML Database as they passed through, and use XQuery for reporting, querying, etc. Even if you do not use and XML Database there are many tools that can do the XML à Relational DB conversion. JSON is ideal for a data-interchange language, and I have always only thought of it as being used in web-development. Passing JavaScript objects vs. XML in an AJAX programming model. I think it would really matter what the ultimate use would be. My opinion is that if you were to use JSON as the internal data exchange format in a tool such as BOTS, this would be very good. However if you are using the format in-house to exchange data with other applications, stick with XML. Hope that helps. Brian From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of eppyebots Sent: Sunday, October 28, 2007 11:46 AM To: [email protected] Subject: [EDI-L] use JSON as a inhouse format? 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 [Non-text portions of this message have been removed] ... 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/
