- CR: https://www.w3.org/TR/micropub/
- ED: https://micropub.net/draft/
- Estimated publication date: 2017-03-23 or 28
Staged draft for publication: https://micropub.net/publish/pr/
The Micropub protocol is used to create, update and delete posts on one's own domain using third-party clients. Web apps and native apps (e.g., iPhone, Android) can use Micropub to post and edit articles, short notes, comments, likes, photos, events or other kinds of posts on your own website.
SOTD: Standard respec
Decision to request transition
Changes since CR
Non-normative editorial changes: https://micropub.net/publish/pr/#changes-from-18-october-2016-cr-to-this-version
Dependencies met: no change
Requirements satisfied: no change
Wide review: Through GitHub issues, all addressed: https://github.com/w3c/micropub/issues?q=is%3Aissue+is%3Aclosed
Formal objections: None
Implementation reports at https://github.com/w3c/Micropub/tree/master/implementation-reports
All features of the spec have two or more independent implementations.
The W3C <a href="https://www.w3.org/wiki/Socialwg/">Social Web Working Group</a> has determined that there are sufficient interoperable implementations of Micropub clients and servers to advance the <a href="https://www.w3.org/TR/micropub/">Micropub specification</a> to Proposed Recommendation. Micropub provides an API standard and extensible way for clients to post, delete, and update social content to servers such as blogs or social media. In particular, we encourage existing implementations of AtomPub (RFC 5023), and the MetaWeblog API (AKA "XML-RPC") to upgrade to Micropub which both supports richer content types, and has additional security & privacy benefits.