Socialwg/Micropub CR

From W3C Wiki

To: the group (optionally), the acting Director, the domain lead, W3C Comm Team <w3t-comm@w3.org>, "chairs@w3.org" <chairs@w3.org>

Archived at:

Transition Request

This is a transition request to Candidate Recommendation.

Document title, URIs, and estimated publication date

The document Abstract and Status sections

Abstract:

  • '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.'

SOTD:

  • Standard Respec

Decision to request transition

RESOLVED:

Changes

See http://micropub.net/draft/#change-log

Requirements satisfied

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.

Wide Review

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.

Issues addressed

See issue tags and history

Formal Objections

None.

Implementation

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.

Patent disclosures

None

News Item

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.

News Item

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.

Retrieved from "https://www.w3.org/wiki/index.php?title=Socialwg/Micropub_CR&oldid=99198"