There's and iso for dates as string with the offset, that's usually fine. Handling Post and Patch differently can at least give a general guideline for "overwr

There's and iso for dates as string with the offset, that's usually fine. Handling Post and Patch differently can at least give a general guideline for "overwriting vs keeping fields on update." The localisation part is trivial if you consider that APIs are to be consumed by machines - much harder, if you assume they're used for GUIs. Error handling is easy to define right, but so tedious to implement.... 1+n can be improved by "guessing" which nested ressources are going to be fetched, and include them "by default." But you're right that those are decisions that need to me made, and can quickly be agonised on without adding much value....