Lists Home |
Date Index |
> In the data model you laid out, moving the key and keyref to the
> ancestor (root) scope really don't buy you anything (even after you add
> the necessary state code to car).
> Key/keyref seem well-suited to describing elements that can be
> "flattened" into relational tuples, not so good for true hierarchies.
> I'm glad to hear HT and company are working the problem. Chained keyrefs
> sound like a useful and usable addition. (At least, they'll be usable
> after Priscilla explains them in the second edition of Definitive XML
> Schema. ;-)
yes, that is exactly what I was trying to reflect on: "relative keys"
(same as keys for elements that cannot be flattened to relational tuples),
are they useful??
chained keyrefs sound like correct, but are they really useful??? Do you
need to really go there, or can we just say that we define keyrefs only
for keys defined within the root scope..?? the question then comes is do
we really need keys that are not defined within the root scope..
Anyways, just random thoughts.. I tend to be tilting towards no need for
relative keys.. (though they are not really harmful)..