[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: [uddi-spec] Change request for deriving V2 key directly when V3key is a UUID key
I think it is reasonable to short-circuit the
production of a V1/V2 key from a V3 uuidKey. I am not sure I understand
the relevance of "root key space" and "root registry" - is it not simply the
case that if a V3 save is made that results in a V3 uuidKey then the mapping
should apply and not the hashing, but if a UUID is used in any other context
then the hashing would still apply?
I would add something to the beginning of 10.1.1
rather than letting the reader wade through the algorithm and then tell them
that it does not apply to V3 uuidKeys.
Do we not need a new policy definition? I
cannot see anything that says what approach is used to generate V1/V2 keys
during a V3 save much less allowing for V3 uuidKeys to be treated
differently.
John
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC