Re: [uddi-spec] Change request for deriving V2 key directly when V3key is a UUID key

[Andrew Hately <hately@us.ibm.com>]

Here is an update without the references
to root space.  They were not really necessary.


As for policy, it's pretty flexible
already but does not call out V2 key derivation, should the following be
added as 9.4.3.6:

9.4.3.6 Legacy version key derviation
policy

In a registry supporting UDDI Version
1 or Version 2 APIs access to a UDDI Version 3 data model , a policy decision
should be declared detailing the methodology for deriving keys for the
Version 1 and Version 2 APIs.  This policy should declare that the
methodology used or that the methodology described in Section 10 of the
specification is used in the registry.

Andrew Hately
IBM Austin
UDDI Development, Emerging Technologies 
Lotus Notes: Andrew Hately/Austin/IBM@IBMUS
Internet: hately@us.ibm.com
(512) 838-2866,  t/l 678-2866

John Colgrave <colgrave@hursley.ibm.com>

02/07/2003 04:57 AM

To	uddi-spec@lists.oasis-open.org
cc
Subject	Re: [uddi-spec] Change request for deriving V2 key directly when V3 key 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
----- Original Message ----- 
From: Andrew
Hately 
To: uddi-spec@lists.oasis-open.org

Sent: Friday, February 07, 2003 1:06 AM
Subject: [uddi-spec] Change request for deriving
V2 key directly when V3 key is a UUID key


Please find attached a change request for review. 




Andrew Hately
IBM Austin
UDDI Development, Emerging Technologies

uddi-spec-tc-cr023-v2tov3keyMapping-20030304.doc