3 ms·
Is this trying to be what the semantic web was supposed to be? Or is it trying to be "OpenAPI for things that aren't REST/JSON-RPC APIs"? (Are those even any di
by tbrownaw 2y ago
Is this trying to be what the semantic web was supposed to be? Or is it trying to be "OpenAPI for things that aren't REST/JSON-RPC APIs"? (Are those even any different?)
And we already have plenty of standards for library documentation. Man pages, info pages, Perldoc, Javadoc, ...
- imtringued 2y agoIt looks like a very poorly thought out HATEOAS and the reason why nobody uses HATEOAS is that for some reason the creator insisted that knowing a set of fields associated with a datatype is evil out of band communication and therefore hinders evolvability. Of course this then leads to a problem. Your API client isn't allowed to invoke hard coded actions or access hard coded fields, it must automatically adjust itself whenever the API changes. In practice means that the types of HATEOAS clients you can write is extremely limited. You can write what basically amounts to an API browser plus a form generator, because anything more complicated needs human level intelligence.