Aaron Bartell wrote:
When I create my own XML it is pretty lean. I had XML that looks more like
sentences than data delimiters (i.e
<ProductionCompanyCustomerNumber>12</ProductionCompanyCustomerNumber>)

I haven't delved into JSON much yet, though it is something I definitely
need to review moving forward.
Well, your XML looks to be leaner than some, primarily because you use a lot of attributes. Many XML implementations are little more than nested tags with CDATA, and of course CDATA requires a beginning and ending tag, whereas a tag with just attributes can be opened and closed in the same tag (using the /> syntax).

So I wouldn't waste a ton of time on it, just recognize that it's an option to review during your design phase. The nice thing about JSON is that it's well suited for JavaScript, which makes it easy to implement an entirely browser-based rich user interface. They're typically not as robust as a thick client, but they have the obvious benefit of being zero-footprint (requiring no installed software).

Joe

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.