I like what I see so far. I might suggest you use an Abstract Dynamic Structured Data system instead of mandating JSON. (check out https://www.ietf.org/archiv

I like what I see so far. I might suggest you use an Abstract Dynamic Structured Data system instead of mandating JSON. (check out https://www.ietf.org/archive/id/draft-hamrick-vwrap-type-system-00.html https://www.ietf.org/archive/id/draft-hamrick-vwrap-type-sys... as an example.) Many (most?) of the SecondLife HTTP API endpoints could accept JSON, XML or our homebrew binary format and would automagically parse it based on the content-type of the blob that was posted. It was useful because we kept getting into arguments about whether we should use JSON or XML. I think you may find communities out there who will insist on JSON, YAML or ProtoBufs, so specifying things in an abstract "super-class" might be able to get past the arguments of how data is represented on the wire and onto arguments about what the data represents. I should probably go write some code to make it more obvious what I'm talking about. With respect to schema versioning, Doug Kaye wrote a book called "Loosely Coupled" and even though it's from the 2000s when everyone thought everything was going to be Web Services everywhere, it still has a decent description of the problem. It's not so great a book as for me to recommend buying it, but it's definitely worth checking out from the library: https://search.worldcat.org/title/53154427 https://search.worldcat.org/title/53154427