Re: MV Keys

dawn wrote:

> mAsterdam wrote:
> 

> 
> 
> Yes, I too often mix sets & lists when I think in terms of the MV data
> model, which has only list attributes in which conceptual sets & lists
> are both implemented.

Really? Are sets implemented as well? I thought it was more like this: When you have a model only supporting lists (e.g. XML) you have no choice but to implement any multi-value thingy as a list - wether you initially thought of it as a set or not.

>>>It might model a proposition something like
>>>
>>>The team with people whose ID's are 112233 and 123456 has a best run of
>>>38 seconds in the potato sack race.
>>
>>The team with people whose ID's are 123456 and 112233 has a best run of
>>38 seconds in the potato sack race.
>>
>>Would be the same proposition, right?
>>
>>So, in this example we have a set-key, not a list-key.

> 
> 
> Yes, unless we add to the proposition so that it matters who's on top
> -- perhaps that person is the lead person, the one we want to contact,
> the one whose left leg is in the sack, the parent...