Altova Mailing List Archives
>comp.text.xml Archive Home
>Recent entries
>Thread Prev - RFC: thoughts for a "streamlined" XML syntax variant...
>Thread Next - Re: RFC: thoughts for a "streamlined" XML syntax variant...
Re: RFC: thoughts for a "streamlined" XML syntax variant...
To: NULL
Date: 5/11/2012 6:08:00 PM
There have been multiple suggestions for terser syntax, over the years since XML was released to the world. In general, they have failed contact with the real world -- they're harder to work with, and/or they aren't actually significantly more compact (especially when you remember that XML compresses wonderfully), and/or what you'd really want is a custom representation within your application (perhaps straight data structures) and XML only as the export/import interface to the rest of the world. The W3C has looked at a number of "binary XML" representations. I believe there was a working group that was investigating trying to come up with something official. I'm not sure what its status is now; the idea still strikes me as an awkward compromise that is going to face too many conflicting goals. Finally: XML's greatest value is that there are lots of tools already in place that support it. This won't be true of any new syntax. Sorry, but I think there really isn't sufficient value here to make the idea worth pursuing.
Disclaimer
These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

