From David Booth:
I would suggest adding a small, simple REST example, perhaps even showing "DO"s and "DON'T"s. For example, show what it means to have the server return a set of links for the possible client next steps, as opposed to having a fixed URL pattern. Programmers hear abstract platitudes REST all the time -- what it is and isn't -- but they need to know concretely (through simple examples) how to do REST properly.
From David Booth:
I would suggest adding a small, simple REST example, perhaps even showing "DO"s and "DON'T"s. For example, show what it means to have the server return a set of links for the possible client next steps, as opposed to having a fixed URL pattern. Programmers hear abstract platitudes REST all the time -- what it is and isn't -- but they need to know concretely (through simple examples) how to do REST properly.