Timeline for Models: two very different concepts
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 8, 2018 at 15:36 | vote | accept | MyiEye | ||
| Aug 4, 2018 at 20:50 | comment | added | MyiEye | So would you say it's correct to label the combination of "view models" (for presentation), "domain models" (for business/domain logic) and "data models" (for performing persistence)" as the model of an application? | |
| Aug 4, 2018 at 18:12 | comment | added | Erik Eidt | Both in some sense. Regarding the former, yes, the term model is context sensitive. Regarding the latter, yes, though rather than describing the model as a layer, I would maybe call it a component of MVC; a component whose implementation detail isn't specified by MVC, but we can certainly talk about it by shifting to another context. | |
| Aug 4, 2018 at 17:54 | comment | added | MyiEye | Good insight. Can I summarize your answer regarding terminology as: "the term is indeed strongly ambiguous and we will simply have to learn to contextualize it for the rest of our lives"? Or are you saying that option 1 (eg. POJO's) is simply part of the option-2-model, which is ultimately the correct meaning? | |
| Aug 4, 2018 at 17:38 | history | answered | Erik Eidt | CC BY-SA 4.0 |