Re: Attribute Value Attributes, Fuzzy Sets, & Color-coded Data

From: Dawn M. Wolthuis <dwolt_at_tincat-group.com>
Date: Tue, 20 Apr 2004 07:53:28 -0500
Message-ID: <c636gd$hu8$1_at_news.netins.net>


"Laconic2" <laconic2_at_comcast.net> wrote in message news:E5OdnfL6z8lYjxjdRVn_iw_at_comcast.com...
> Take a look a data warehousing.
>
> You don't go back and alter history.
>
> You relate what was at that time to what came later.

I'm quite familiar with data warehousing, but what does that have to do with DBMS's that have capabilities for introducing across-the-schema attribute value attributes? Perhaps you were just tapping into the statements I made that relate to "aging" the data -- that is just an example of a type of attribute value attribute -- not intended to give a solution to a specific problem.

To make it simple, but not necessarily obvious why one would need it, just use the example of wanting to color-code your data for one reason or another. So, for each value entered (not the same for each value of a particular attribute) you want to put an RGB value with it. Are there any data models or database implementations that incorporate these global attribute value attributes?

And my other question is how this would be handled in a relational model and I think I have that answer -- attribute value attributes would not be global specified, they would be specified with each individual value, and then normalization would explode the data into separate tables for every "attribute" (since each would have its own attribute value attribute associated with it).

If you just take this problem statement of color-coded data values, how would you model the data?
--dawn Received on Tue Apr 20 2004 - 14:53:28 CEST

Original text of this message