The REST API schemas provided currently are only valid for reads (GET) and for the view and edit contexts. This has some problems:

• The schemas aren't valid if you're trying to construct a create, update, or delete request
• The schemas have fewer constraints than they should have for both the view and edit contexts as they currently cover both
• The schemas are not valid for the embed context

Ideally separate schemas would be provided for each of the four request types (CRUD) and each of the three contexts (view, edit, and embed).

What I don't want to do though is maintain a bunch of schemas for each endpoint that are all similar. This needs to either use partials or be automated somehow.