Since publishing the latest W3C draft of Micropub on March 1, there have been a few minor updates based on feedback from people who have implemented it.
Simpler update syntax
The update syntax had an extra nesting that was not necessary. The syntax changed from:
Moving a post
If the update operation caused the post to be moved to a new URL (such as when the URL scheme is based off of the post's date, or has a custom slug that is editable), the Micropub client needs a way to know the new URL of the post.
The Update Response section now includes HTTP 201 as a possible response, along with:
If the update operation caused the URL of the post to change, the server must respond with HTTP 201 and include the new URL in the HTTP
Thanks to Greg for providing feedback on his Micropub implementation.