I have an application where there is an "inventor" model whose data I would like to display differently in different areas of the application. Therefore, I'd like to create different view models backed by that one model.
For instance, in one section, I might display just a list of inventors with their first, middle, and last name. In another area of the application, I might display the inventors with only their initials.
A clean implementation of MVVM would seem to dictate that I'd have one model for every view model; however, if there is one notion of a model -- the inventor -- which contains a lot of data that is common across multiple usage areas in an application, then I feel as though there should be one concrete model that is shared by multiple view models.
I've not been able to locate anything that seems to address this, though I'm surprised because I feel like it would be a common question for beginners in MVVM. Is there a "standard" or accepted answer to this?