Persistent disks proposal

A stake in the ground ... something to evolve into a working implementation.
Let me ask my question differently: Let's assume that the boolean lives at the VolumeSource level. Why does this necessitate 2 pod definitions? Is it possible that I would only ever want to mount a disk as readonly for pod use? If so, wouldn't that mean that I don't need two pod definitions?