> ... determine how data can be created, stored, and changed. So you can record sound, store it in a "track", transform it to "mono" etc? > ... It is contrast

> ... determine how data can be created, stored, and changed. So you can record sound, store it in a "track", transform it to "mono" etc? > ... It is contrasted with the remainder of the software that might be concerned with lower-level details of managing a database or displaying the user interface, system infrastructure, or generally connecting various parts of the program. You might store the sound as a wav, export it as an mp3 - the undo tree might be in SQLite... Ed: might make more sense with the term "domain"; domain logic, domain rules. Ed2: somewhat tangential, but see also the original model-view-controller-(user) paper - the user holds a mental model of data/objects in the domain - and the application holds raw data in ram/disk - the UI needs to bridge these two domains so that a user can "apply reverb" from the domain concept to the actual data model (modify a wav file). https://folk.universitetetioslo.no/trygver/themes/mvc/mvc-index.html https://folk.universitetetioslo.no/trygver/themes/mvc/mvc-in...