Good points Mike. I looked through the slides for the presentation and I love the way you frame data modelling within IA. (Here it is, if people want to take a look: http://www.slideshare.net/reduxd/beyond-the-polar-bear). These are definitely interlocking practices, each with a slightly different focus.
Here’s how I see all of these models fitting together. There are basically three types of metadata:
* *structural metadata* - which describes how the types of content, their attributes, and how they relate to each other)
* *administrative metadata* - which describes various administrative states of a piece of content, such as who authored it, or when it was created
* *descriptive metadata* - which describes what the content is about and gives it more context and meaning
The Content Model is primarily concerned with structural metadata, while the Domain Model is largely concerned with descriptive metadata, though there’s some overlap (especially when you start talking about how content objects will be tagged, and how they’re related to other content objects).
Of course, all of these models have a common purpose, which is to help translate and communicate concepts and intentions into something that can be validated and built. Which makes them ideal tools for creating a bridge between design and technology.