Re:Standards.REST: A Collection of HTTP/REST API Standards a...
by smt88 on Friday May 17, 2019 @05:40PM
(#19943828)
Open 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.
Re:Standards.REST: A Collection of HTTP/REST API Standards a...
by M2Ys4U on Friday May 17, 2019 @07:11PM
(#19944461)
The last time I looked at Open API it was really hard to model a proper REST (HATEOAS) API
Re:Standards.REST: A Collection of HTTP/REST API Standards a...
by treve on Tuesday May 21, 2019 @09:47AM
(#19970073)
Still is
Re:Standards.REST: A Collection of HTTP/REST API Standards a...
by kbenson on Friday May 17, 2019 @05:00PM
(#19943525)
I 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.
Re:Standards.REST: A Collection of HTTP/REST API Standards a...
by rocketpastsix on Saturday May 18, 2019 @08:34AM
(#19947061)
check out https://openapi.tools
Here, I'm not sure what one would do with a list of RFCs?
[0] https://swagger.io/resources/open-api/