4 ms·
This doesn't seem like it's much helpful. If someone is building a new API and want a list of standard/best practices to follow, something like OpenAPI[0] would
by jypepin 7y ago
This doesn't seem like it's much helpful. If someone is building a new API and want a list of standard/best practices to follow, something like OpenAPI[0] would be much more helpful.
Here, I'm not sure what one would do with a list of RFCs?
[0] https://swagger.io/resources/open-api/ https://swagger.io/resources/open-api/
- kbenson 7y agoI agree that OpenAPI is how I would prefer to see an API documented and defined (especially since there are tools to allow you to use a good spec to automatically generate your client routines), but I think many these RFCs are a bit different, in that they may define how records should show relations to each other, or how to use Oath, etc, which is something OpenAPI documents, but not something it prescribes. Where OpenAPI defined how to implement a client or server interface for an API, these RFCs seem to define some best practices for how you would do so. That is, if OpenAPI is analogous to a dump of a database schema, these RFCs are more analogous to a set of best practices on database naming, data types to use, which levels of normalization are best for which types of data, etc.
- smt88 7y agoOpen API Spec is just a format for documenting HTTP APIs. It has no opinion on how you design your API, whether it be RESTful or not.
- M2Ys4U 7y agoThe last time I looked at Open API it was really hard to model a proper REST (HATEOAS) API
- treve 7y agoStill is
- rocketpastsix 7y agocheck out https://openapi.tools https://openapi.tools