Now someone moves collection c that contains t - then the server has to do fixup semantics. When you move c to d, you just change the binding from c to rc to be d to rc. Then all members stay the same. We need 2 kinds of references. We still need references that aren t bindings, they refer to URLs.
Bindings are direct by definition.
The fixup stage is intended to produce this. We need both kinds of members, so we define a new operation called BIND different from move or copy. There s a requirement that references be able to carry properties. We can just say that trying to meet that goal led to a protocol with undesirable characteristics. In versioning, the only properties it was tempting to put on references were transitory and interesting only for the server.