Nice find, will have to check out the site further. The diagram/flow
chart is well done, but I think there is a more meaningful way the
info could be structured so that it would be a better 'what should I
do in this case' type of reference, and could list both proper and
improper use cases for each status code.
In the interest of having a single repository of [hopefully]
structured info, I've regged
cfrest.org and will setup a wiki for our
use. Will keep you guys posted on that in the next day or so.