Googlebot is not an automated HATEOAS client, it's solely an automated web client. Even if the web conformed to all the specifications it would still be an exceedingly atypical example of a HATEOAS API. And googlebot is nowhere near the reliability level that we would require for most use cases.
Re:Who Cares about GET vs. POST? NoREST
by dragonwriter on Tuesday March 03, 2015 @05:53PM
(#9141353)
> Even if the web conformed to all the specifications it would still be an exceedingly atypical example of a HATEOAS API.
The HTTP-powered Web is the prototypical REST (including the HATEOAS constraint that is part of the definintion of REST) API.
Then REST is a wrong word, one that doesn't point to a natural empirical cluster. The web is very different from all the other things that are called "REST API"s.
Re:Who Cares about GET vs. POST? NoREST
by dragonwriter on Wednesday March 04, 2015 @09:56AM
(#9144532)
Most, but not all, "REST" APIs (other than the web) violate at least one element of the definition of REST, most commonly they don't actually implement HATEOAS, requiring out of band knowledge of applicable resource URIs or URI patterns and/or information about data formats not communicated by documentation of media types and hypertext relations.
But that's because REST is often used as a buzzword by people who don't know what the architectural style entails, or aspirationally to describe one goal of the design of an API, but one that may be compromised for conflicting goals.
HATEOAS doesn't inherently require that you "go" anywhere to get a hypertext document describing an API, and can be as complete as you want. But, since its really designed for web-scale decentralized interlinked APIs, no, its not primarily intended to have one document that gives you every possible linked endpoint.
> Automated HATEOAS clients are at this point purely theoretical
Googlebot is an example of an automated HATEOAS client that handles a wide array of content types. It is decidedly not purely theoretical.