Based on the fact that REST [1] is not a protocol but an architectural style the term "binding" is definitely wrong.
I think we could also choose to call it something more vague with restful in its name.
Generally, I would like to propose that in addition to changing the name throughout the specification we should
also try to adhere to the design principles of AtomPub.
[1]
http://en.wikipedia.org/wiki/Representational_State_Transfer
If what we want is *some* HTTP binding, call it "HTTP binding". If we're sue it's gonna be based in AtomPub, then let's called it that way.