Micropub, CR TransReq from Social Web WG

Live version at https://www.w3.org/wiki/Socialwg/Micropub_CR 
<https://www.w3.org/wiki/Socialwg/AS2_CR>
See also https://www.w3.org/wiki/Socialwg/AS2_CR 
<https://www.w3.org/wiki/Socialwg/Micropub_CR>
Transition Meeting for both scheduled for 6 July.


      Document title, URIs, and estimated publication date

  * "Micropub"
  * Latest Published: https://www.w3.org/TR/micropub/
  * Editor's Draft: http://micropub.net/draft/
  * Staged Draft: Not yet staged
  * Publication Date: 2016-07-07 or 2016-07-12


      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:

  * https://www.w3.org/2016/06/21-social-irc#T17-34-04


      Changes

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


      Requirements satisfied

No formal requirements. The charter 
<https://www.w3.org/2013/socialweb/social-wg-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:

  * several type of analyses
    <https://www.w3.org/wiki/Socialwg#Social_Data_Syntax>
  * a large enumeration of user stories
    <https://www.w3.org/wiki/Socialwg/Social_API/User_stories>
  * requirements for WG deliverables
    <https://www.w3.org/wiki/Socialwg/Social_API/Requirements>


      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 <https://indiewebcamp.com/Micropub> lists independent 
implementations, reported 
<https://indiewebcamp.com/wiki/index.php?title=Micropub&limit=500&action=history> 
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 
<https://github.com/aaronpk/micropub/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aclosed> 
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 
<https://indiewebcamp.com/Micropub#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 <https://github.com/aaronpk/Micropub/tree/master/implementations>.


      Patent disclosures

None <http://www.w3.org/2004/01/pp-impl/72531/status>