- 1 Transition Request
- 1.1 Document title, URIs, and estimated publication date
- 1.2 The document Abstract and Status sections
- 1.3 Decision to request transition
- 1.4 Changes
- 1.5 Requirements satisfied
- 1.6 Dependencies met (or not)
- 1.7 Wide Review
- 1.8 Issues addressed
- 1.9 Formal Objections
- 1.10 Implementation
- 1.11 Patent disclosures
- 2 News Item
- 3 News Item
To: the group (optionally), the acting Director, the domain lead, W3C Comm Team <firstname.lastname@example.org>, "email@example.com" <firstname.lastname@example.org>
This is a transition request to Candidate Recommendation.
Document title, URIs, and estimated publication date
- Latest Published: https://www.w3.org/TR/micropub/
- Editor's Draft: http://micropub.net/draft/
- Staged Draft: Not yet staged
- Publication Date: 2016-08-16
The document Abstract and Status sections
- 'Micropub is an open API standard used to create posts on one's own domain using third-party clients. Web apps and native apps (e.g., iPhone, Android) can use Micropub to post short notes, photos, events or other posts to your own site.'
- Standard Respec
Decision to request transition
No formal requirements. The charter refers to "Social API" and "Federation Protocol" in a way the group found ambiguous. We eventually settled into thinking of the "Social API" as a RESTful API that Web clients can use to speak to servers managing 'social' data. Micropub is one such API. There is at least one other expected from the WG (ActivityPub).
The group produced:
Dependencies met (or not)
Normative References are all W3C Rec or RFC, except Microformats-2 and h-entry, which the Director has previously indicated are sufficiently open and stable.
Charter Dependencies appear not relevant, except horizontal review in progress.
Micropub was first developed in the IndieWebCamp community. Its page there lists independent implementations, reported by the implementors. These implementations act as implicit reviews, and still largely apply since the changes have been to clarify edge cases and are intended to be entirely backward compatible.
Since coming to W3C, 26 issues on github have been opened (by 6 different people, not counting the editor) and addressed.
See issue tags and history
The 15 earlier indieweb implementations stand largely in support of the current spec, and have been tested in an ad hoc manner with each other. Now that the spec is more formal, has a test suite (and minor additions), we are gathering new implementation reports with test results.
The W3C Social Web Working Group is calling for implementations of Micropub, which is now a Candidate Recommendation. Micropub provides a mechanism for communication between independently developed clients and servers to allow creating, updating and deleting social content. For users, an immediate benefit is the possibility to change between or use multiple third-party posting clients with their own data storage. Before being brought to W3C for standardization, Micropub already had over a dozen independent implementations in the IndieWebCamp community.
Micropub Helps ___ the Web
The W3C Social Web Working Group is calling for implementations of Micropub, which is now a Candidate Recommendation. Micropub provides a mechanism for applications to create posts..... This mechanism is a core building block for a decentralized (social) Web, because it allows..... Before being brought to W3C for standardization, Micropub already had fifteen independent implementations in the IndieWebCamp community.