Create and deliver personalized experiences across digital properties at scale
Build engaging websites with intuitive web content management
Leverage a complete UI toolbox for web, mobile and desktop development
Build, protect and deploy apps across any platform and mobile device
Build mobile apps for iOS, Android and Windows Phone
Rapidly develop, manage and deploy business apps, delivered as SaaS in the cloud
Automate UI, load and performance testing for web, desktop and mobile
Host, deploy and scale Node.js, Java and .NET Core apps on premise or in the cloud
Optimize data integration with high-performance connectivity
Automate decision processes with a no-code business rules engine
Transform your businesses in order to survive in a completely digitized and connected world driven by software innovation.
Globally scale websites with innovative content management and infrastructure approaches
Content-focused web and mobile solution for empowering marketers
Faster, tailored mobile experiences for any device and data source
UX and app modernization to powerfully navigate today's digital landscape
Fuel agility with ever-ready applications, built in the cloud
Spotted an article on CNET's News.com discussing the possibility of faster XML ahead. It turns out that Binary XML has triggered plenty of chatter on this topic before, and I think it's important to talk about how this reflects against the upcoming Final Recommendation for W3C XQuery.
Whether we end up with one binary XML format, sanctioned most likely by the W3C remains to be seen. Opinion on this appears to divided as to whether one single binary format will emerge or indeed if multiple formats are more appropriate - see Michael Rys' recent posting for his take.
Otherwise, XQuery implementations will likely evolve to cater for the binary format(s) and include some degree of intermediary between the extended set of data sources. Today we already see examples of this whereby XQuery implementations provide a mediation between relational data stores using SQL Views and traditional plain text XML data. The Progress DataDirect XQuery implementation does precisely this.
Although it may be too early to accurately predict, I don't expect binary XML will replace textual XML. In fact I believe it is the express goal of the majority of the supporters of this format. Standard textual XML will remain the mainstay of loosely coupled systems where interoperability is central to their continued successful operation. Binary XML will have it's place, too: the strength in demand for efficient XML transmission particularly in the wireless space will drive that need.
View all posts from Jonathan Bruce on the Progress blog. Connect with us about all things application development and deployment, data integration and digital business.
Copyright © 2016, Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks or appropriate markings.