Its most well-known and deployed API is the Payment Request API, which streamlines the Web checkout process: browsers take charge of collecting and managing users' payment information, bringing less typing and more consistency in that experience w3.org/TR/payment-request/
The @w3payments Working Group released yesterday its roadmap of work for 2018 lists.w3.org/Archives/Public… . This is the group developing new features to facilitate and improve payments in Web browsers.
The PAB just got started, Mozilla has been at this for 12 years - the discussion on the URL of the site (which was actually brought up at our face-to-face meeting) was evaluated as not time critical for the moment…
The MDN Product Advisory Board has representatives from @w3c, @mozilla, @googledevs, @MSEdgeDev and @samsunginternet precisely to make it clear this is no longer a single-vendor project (even though @mozilla is clearly putting a lot more resources in it atm)
The group is actively looking for feedback on this new approach, which is meant to help managing multiple sensors simulatenously, bring a stronger privacy and security story for them and enable high-performance use cases and sensor fusion
The Device and Sensors Working Group is close to bringing it to Candidate Recommendation - the API is available as an origin trial in Chrome nitter.vloup.ch/anssik/status/93… and there is a polyfill for turning the existing into the new model APIs
And in the longer term, we hope MDN can serve as a conduit to getting more input and contributions from developers to our specs - ultimately for better specs and a better Web.
We are just getting started, but this meeting was a great start!
Hopefully we can facilitate the adoption of these explainers as seed to future MDN content.
Some groups have also developed dev-focused material that might usefully migrate to MDN github.com/w3c/payment-reque…
For instance, the @w3ctag has been pushing @w3c groups developing specs to develop at the same time explainer docs, which puts features in the context of their expected usage by developers docs.google.com/document/d/1…
WebSub (formerly PubSubHubbub) is now a W3C Recommendation, much thanks to editors @aaronpk and @julien51. Now a standard way to request notification when a web page changes. Check it out. w3.org/TR/websub/
ActivityPub is now a W3C Recommendation, after epic work by @dustyweb. Used by Mastodon and other systems to create a decentralized social web. Congrats to the now completed Social Web WG. w3.org/TR/activitypub/