 |
 |
 |
http://www.w3.org/TR/2007/WD-exi-20070716/ has been published; now it's time for the rest of the world to take a look at what W3C has come up with and evaluate whether it meets a real world need. Elliotte Harold http://www.cafeconleche.org/oldnews/news2007July18.html has the only post I have seen so far that expressed an opinion: "The Efficient XML Interchange Format is neither efficient nor XML nor interchangeable." I'm particularly interested in thoughts on what the WG came up with in the light of the TAG opinion http://lists.w3.org/Archives/Public/public-xml-binary/2005May/0000.html . Specifically, how much of a performance / compresison gain would it take to outweight the disruptive effects the TAG
noted? It would be interesting to have that discussion before the EXI WG publishes their report on how much actual improvement they see for which scenarios. For the record, Microsoft has expressed considerable skepticism that a single efficient XML format could cover enough use cases with sufficient improvement to justify a W3C Recommendation, but we are waiting for the hard evidence.
|
 | 

|  |
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.
|  |
| |
 |
 |
 |