Might be another argument for preflighting data so we can throw an error if you try to supply the field

Possible rule to follow for the API: if invalid data has been provided for a valid field, throw an error. If invalid data has been provided for an invalid field, we can silently ignore.

Joe and Daniel are generally against nested object for discussion. Count should be an attribute of the link to the collection, and it doesn’t make sense to have statuses for posts and pings. We should avoid nested objects as much as possible because they make for painful cURL requests.

Title (raw|rendered) and content (raw|rendered) are unaddressed beasts in this regard. Some discussion of their inconsistencies.

Discussed named routes: https://github.com/WP-API/WP-API/issues/577

One useful use for this is shorthand for referring to other routes. Avoids having to update a bunch of paths.