>Does your JSON response at the root entry point to the API return something signifying what all possible operations are?
Why, no, it doesn't, because it takes 3 parameters, each of which can take 10,000 possible values, and I don't want to transmit a trillion options every time someone pings the root.
I mean, I considered documenting how to pass the parameters on a client's first entry but the HATEOAS crowd told me I was just re-creating RPC, and I agreed. So no HATEOAS.
Of course not - it is called HYPERMEDIA as the engine of application state (not JSON.) That's why it's not called JATEOAS. The information you are asking for sounds more appropriate in an OPTIONS request.
> Of course not - it is called HYPERMEDIA as the engine of application state (not JSON.)
If the answer to those questions is no (whether the format of the response is JSON or anything else), then you aren't using hypermedia as the engine of application state.
Does the JSON representation of a Employee object returned URLs as a part of the body for the resource addresses for any "child" objects?
I don't think it can be considered HATEOAS if the answer to either is no.