Not going to explain why in detail at the moment, but basically, with respect to the navigation system, the URL routing system, and the view system,

- the Views shouldn't know anything about what user-facing names are used for them in the interface
- the Views shouldn't know anything about where in the navigation hierarchy they are - it's alright to have common View mixins whose names reflect actual overlap between the navigation hierarchy and shared functionality of the views, but these should be totally separate from anything having to do with the navigation hierarchy
- the Views shouldn't know anything about what their URLs are named or what URLs they are viewed at

It almost became a requirement recently that one view could be displayed in two different places.  (We got rid of the Message History report on the Messaging Page.  This might have been confusing to users if we didn't provide a link in the old place.  Right now we're just providing a link to the Message Log report, and it takes you to the Reports page, but it would have been nice to be able to actually show the Message Log report in two different places in the navigation hierarchy if that was desired.)