Admittedly I skimmed -- observed that the paper dove really deep into time to perform queries and implement desired behavior, but didn't spend much time on impl

Admittedly I skimmed -- observed that the paper dove really deep into time to perform queries and implement desired behavior, but didn't spend much time on implementation of GraphQL vs a REST API. One statement made that stood out to me: > it is clear that the availability of a type system—expressed as a schema— is one of the key benefits provided by GraphQL So I wonder what the results would look like if you had an OAS spec file for the API you were hitting (with autocomplete in VSCode), seems to me that's the best of both worlds: ease of implementation on the server side, ease of use on the client side. This to me feels like an argument of better tooling and (self) documentation rather than one technique over another.