Query name and response consistency

[manton]

Documenting a few differences that came up in chat. I'm not necessarily suggesting any of this change, because a lot of these have been implemented for a while. But there should probably be a kind of "style guide" for new extensions.

q=contact:

• Currently returns a "contacts" array. Could be changed to q=contacts.

q=category:

• Currently returns a "categories" array. Consistent with contact, but probably reads better as q=categories too.

q=source (without a url param):

• Currently returns an "items" array. Instead of overloading q=source from the original spec, could be q=items.

q=config:

• In addition to the media-endpoint, also returns a destination array if the user has multiple sites configured. I personally like including some of these things in q=config because it's easy to get them in one call, but probably should be a plural destinations array in the response.
• Also includes a post-types array.

q=syndicate-to:

• This response and also from q=config returns a syndicate-to array. This is in the original Micropub spec.

[manton]

Edited to remove speculation about post-types. They are not really the same thing as the type for JSON requests.

[jalcine]

I'm a bit hesistant about q=source being q=items because of the semantics of the query. q=config is a bit weird because it's very variable depending on what extensions you've defined (maybe could be solved/normalized with #44).

That said, would normalizing the output for q=contact, q=category, q=source and q=syndicate-to to be something similar to what q=source gives? Namely, assuming a items and paging being provided at the least for queries that are meant to return a list of zero or more items.