His argument is for API discoverability. Client should be able to learn about available endpoints
[edit: ...and resources. And be able to comprehend resource record conventions]
[edit: ...and resources. And be able to comprehend resource record conventions]
I just don't see any generic operations w.r.t. discovery that are … useful.
I'm not trying to say that you shouldn't, e.g., use URLs in your resulting resources; e.g., if a query for a widget returns:
{
"widget_name": "NextGen Enterprise Widget",
"suppliers": "http://bigcorp.example.com/widget/123/suppliers"
}