Original text:
entry point for requesting the links hosted by servers with known or discovered addresses RFC6690.  6. Certain kinds of design problems are often recurring in variety of

Reviewer comments:
I just gave this advice and it might be a good rule of thumb: Assuming human-readable representation formats (i.e., text-based not binary) and a client supporting the URI scheme used, a good rule of thumb for a good hypermedia-driven design is the following: A developer should only need an entry point URI to drive the application. All further information how to navigate through the application (links) and how to construct more complex requests (forms) are published by the server(s). There must be no need for additional, out-of-band information (e.g., API specification). For machines, a well-chosen set of information needs to be shared a priori to agree on machine-understandable semantics. (Agreeing on the exact semantics of terms for relation types and data elements will of course also help the developer.)
Yes, except that text-based doesn't mean human-readable (as exemplified by JSON -- in reality you need a formatting tool to look at any instances that aren't entirely trivial). More important is that the format is self-describing (and the tool you need to look at that not too obscure).
Yes, yes, all this is already in the assumptions to get a concise rule of thumb :) Next iteration: Assuming self-describing representation formats (i.e., human-readable with carefully chosen terms or processible by a formatting tool) and a client supporting the URI scheme used, a good rule of thumb for a good hypermedia-driven design is the following: A developer should only need an entry point URI to drive the application. All further information how to navigate through the application (links) and how to construct more complex requests (forms) are published by the server(s). There must be no need for additional, out-of-band information (e.g., API specification). For machines, a well-chosen set of information needs to be shared a priori to agree on machine-understandable semantics. (Agreeing on the exact semantics of terms for relation types and data elements will of course also help the developer.)
At least one little update :)Looks good. There's just a small problem: Nobody is doing it.

Revised text:
entry point for requesting the links hosted by servers with known or discovered addresses RFC6690. <ins> 5.4. Assuming self-describing representation formats (i.e., human-readable with carefully chosen terms or processible by a formatting tool) and a client supporting the URI scheme used, a good rule of thumb for a good hypermedia-driven design is the following: A developer should only need an entry point URI to drive the application.  All further information how to navigate through the application (links) and how to construct more complex requests (forms) are published by the server(s).  There must be no need for additional, out-of-band information (e.g., API specification). For machines, a well-chosen set of information needs to be shared a priori to agree on machine-understandable semantics.  Agreeing on the exact semantics of terms for relation types and data elements will of course also help the developer. </ins> 6. Certain kinds of design problems are often recurring in variety of