A group of representatives from Stack Exchange, GitHub, Reddit, and others have started to standardize and enhance Markdown under the name Standard Markdown. Their efforts have met the opposition of John Gruber, the syntax’s creator, who does not want to see Markdown used in other projects, so the project was eventually renamed CommonMark.
Ecma International has standardized the first edition of Dart, ECMA-408.
David Wheeler has proposed a standard URI format for database connections. This proposal would allow applications built on different technologies to share the same connection string. That would be beneficial for a wide variety of tools including report builders, automated build and deploy tools, and ORMs.
The Internet of Things is hear today and the IETF has begun a number of standardisation efforts in this area. Notable amongst them is the Constrained RESTful Environments (CoRE) working group, which is looking to provide REST approaches to constrained devices. There's also a Java project to support this work.
The state of standards compliance with Visual C++ has long frustrated developers looking to use the newest (C++11) and not so new (C99) language features. Microsoft has now announced a road map that indicates when developers can expect to have these features available in a Visual Studio release.
This month’s release of the Java EE 7 platform includes a specification for a batch processing programming model that is heavily derived from Pivotal’s Spring Batch project.
The fourth version of OData, the Microsoft-backed standard for querying data using REST conventions, has been accepted by the OASIS committee. The public review period will run thru June 2 and Microsoft expects OASIS to adopt the standard later this year.
Microsoft CU-RTC-Web is an alternative approach to WebRTC meant to show some of WebRTC’s weaknesses and to push it forward.
HTML5 and Canvas 2D have reached Candidate Recommendation status, High Resolution Time and Navigation Timing are Recommendation, while HTML 5.1 and Canvas 2D Context Level 2 are Working Drafts.
The editors of the HTTP specification have published an initial draft of v2 which is a straight copy of SPDY and will be used as a base for diffs going forward. Many changes are expected to be done like adding new features, removing existing ones, changing the bytes on the wire, etc. A draft ready for test implementations is expected to be published early next year.
The Open Group recently announced that their SOA Governance Framework was accepted as an international standard following a vote by the International Organization for Standardization (IOC) and International Electrotechnical Commission (IEC). The ratification came at the end of a six month review period and marks a continued relevance of SOA principles in today’s technology solutions.
IETF has discussed the future of HTTP, and the next version is to be using SPDY as a starting point. There is a controversy though: Microsoft claims SPDY is no better than HTTP/1.1 with all optimizations turned on, while SPDY’s inventor says Microsoft’s tests actually confirm SPDY’s advantage in a real world scenario.
Rackspace's Mark Nottingham, discusses the recent HTTPbis Working Group meeting, clarifications to the HTTP/1.1 specification, and the influence of SPDY on the group that have resulted in a change to its charter enabling them to begin considering HTTP/2.0.
With WebSockets now a W3C Candidate Recommendation and a new JSR about to start in the JCP, the question arises about how and if WebSockets work with the principles of REST? Do they compliment each other, or will WebSockets, as some people believe, divert attention away from REST and towards a new style of interaction for the Web? There is even the suggestion that WebSockets "breaks the Web".