@EdwardHinkle Sounds great! I can implement it at any time on Micro.blog, although first I wonder if anyone has feedback on the JSON key names.
One thing to note is these are all properties of the
h-entry vocabulary, whereas other kinds of posts support totally different properties. Things like
h-review where they are completely different things. Continuing down this path it would make sense to scope these properties to note that they are part of the
The other question is how many of the supported properties would need to be defined? If not all of them, (e.g.
published) why these ones in particular?
Is it because these correspond with post types? If that's the case, then maybe this should be somehow tied to the Post Type Discovery spec which spells out what properties map to what kinds of posts.
In that case, it may make more sense to have the server advertise which of these post types it supports, and then clients would look at the spec to know which properties to send to create those posts.