Re: Multi Valued Interface Models?

dawn wrote:
> ... separate yourself from thinking about the data model for the
> database (that is the model of the interface to the database) and focus
> on the data model of the interface to the user. It simply is not
> possible for the RM to be the data model for that interface.

Can you say why? I read your blog posts, and I didn't see any justification
for this statement. Your example UI model wasn't very enlightening, either.

In any event, I am certain that the "not possible" part of the above statement
won't hold up, because the RM can model any concrete type, even if restricted to 1NF. I'm not saying "convenient" necessarily, just possible.
On the other hand, you use the words "model" and "interface" in a lot of different ways, and it's possible I'm not following your argument.

Calling out specific concerns is always helpful to the conversation. I sometimes feel like you spend too much time on definitions, especially
definition of multivalued (ha ha) words like "interface". Specific terms
are easier to define than generic terms.

Marshall Received on Thu Feb 09 2006 - 22:05:26 CET