Should be allowed to use the package model element as a namespace. This change would allow to apply the same element names in different package hierarchy of the same module what is very often when you define an element in different context. For example, the a microflow handling a change event of a field with the same name but in different pages.
Currently we have to define unique element names in a module, even if we define them in different package hierarchy following our feature breakdown. If a package had an own namespace providing a context for package members, their names do not have to include this context information to make it unique. It is duplication since the nesting package hierarchy provides the same purpose.
To sum up, the package concept provides a modelling structure element in general, so this practice is suggested to be followed in Mendix.