Unambiguous Content Models

I'm baffled by the justification of the "Unambiguous Content Model"
constraint as being "for compatibility".  What kind of compatibility is
it that XML Schemas is trying to achieve here?  Elsewhere there
(rightly) doesn't seem any requirement to avoid being more expressive
than XML DTDs; so why is there such a requirement here?

James