A browserless world via chat apps?

Just when the content market gains parity with full web 2.0 integration, new apps and functionality are shaping the way we manage and distribute content to consumers. An emerging trend: a shift away from open accessibility browsers to proprietary chat apps.

In Facebook's Spring 2016 announcement of expanded functionality in its Messenger app, one of the benefits emphasized by the social media giant was new content publishing capabilities. Facebook invites developers to build bots that use the Messenger Send / Receive API, which now supports, "…not only sending and receiving text, but also images and interactive rich bubbles containing multiple calls-to-action." The company also announced integration of Wit.ai's Bot Engine, which allows for developers to build more "complex" bots around machine-learning algorithms that can process natural language patterns. 

"80 percent of user time is spent on just five applications."

Too much to surf
While it's difficult to speculate as to its full impact, the expansion of chat app functionality may in fact signal that consumers are looking for a more direct way to receive and transmit data by way of content.

"Today, we no longer surf the web because there's too much to surf," writes Chris Moore is Chief Revenue Officer of Nexmo for The Content Wrangler. "Now, the bottomless ocean of information and data at our disposal has arguably become the Internet's biggest weakness. That reality, combined with the rise of smartphones as mainstream consumer devices, has ushered in an app economy where chat apps are fast becoming the new default destination for web-bound consumers."

Moore goes on to say that, according to a recent Forrester report, 80 percent of user time is spent on just five applications, with the closed-system of social media and messaging being the primary places spent. This could effectively mean that chat isn't just the web of tomorrow – it's essentially the web of today. 

An evolutionary essential 
So what does this mean for content managers? Simply, it means that chat- and social integrated-content management tools are a growing necessity. The ability to aggregate content and data, and apply learning algorithms in the forums where the most communication is occurring is the next evolutionary step for the content management and hypertext market. This means, too, that XML content management systems cannot hope to stay relevant in a market where content consumers are looking to bypass browser-oriented portals in favor of direct-from-the-vendor apps driven by user-configured bots.

According to Daniel Nations, a trend expert for About Tech, the "browsers of tomorrow" will likely be each website offering unique, proprietary apps and creating a seamlessly integrated browsing experience.

"I imagine it would be like merging our current browsers, ActiveX, and Java to create something that can be both a mini-operating system and a development platform," speculates Nations.

Mr. Nations may be showing his age, since ActiveX and Java in the browser are falling out of favor for their nearly innumerable security weaknesses.  Nevertheless, his core point is worth noting, "For you and me, it would be like loading up our office application, seamlessly switching between a word processor and a spreadsheet, and just as seamlessly switching to a massively multiplayer online roleplaying game."

House Speaker Paul Ryan proposes future legislation converted to XML

A recent measure by House Speaker Paul Ryan will see "all legislative measures" converted to XML. Ryan announced this proposal at the 2016 Legislative Data and Transparency Conference, saying it would be the continuation of work started by the creation of the Bulk Data Task Force in hopes of making "the House more open and transparent" – giving developers to opportunity to scrape data and make it more publicly searchable.

"All legislative measures will now be converted to XML."

"Now we're working to go further, and publish even more current and past documents in XML," Ryan told the assembled conference-goers. "I've asked our team to keep moving ahead by publishing all legislative measures in a standard format. That means enrolled measures, public laws, and statutes at large."

The Bulk Data Task Force was the work of Ryan's predecessor, John Boehner, and was designed to convert documents in bulk to digital markup languages. This led to the creation of the United States Legislative Markup Language, an XML vocabulary used to encode all versions of the United States Code created on or after July 30, 2013.

"We want to have a project we can start and complete in a fairly short time frame," Lisa LaPlant, Federal Digital System program manager for the Government Publishing Office, the government group initially funding the project, told FedScoop. 

In addition go improving transparency, Ryan stated that the conversion would help lawmakers make more informed decisions when proposing or arguing legislation. By entering laws into XML, the ease in searching and keywording historical legislation will, according to Ryan, guide lawmakers away from "making or repeating the mistakes of the past."