A second hierarchy may be applied as well, based on IP prefixes like it exists for inetnum objects. This would mean that route objects of different origins for given IP address ranges could only be handled if properly authorized. However, authorization only makes sense if it is enforced. As a consequence, additional restrictions are imposed. The question now is whether these can be accepted.
Restrictions hinder current practice.
Routers in real life do not depend on registration. Routing and filters may be built from registry data calling for a tighter control of route objects because invalid registry data directly impacts real world routing if router configs are generated from them. Owning address space is worthless if it is not used. Usage is reflected in route objects making them important beyond mere technical operation. Unfortunately, even though there was some discussion on this topic, no real consensus was found.