OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

uddi-spec message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: RE: [uddi-spec] CR-010: isReplacedBy tModel


Anne,

Thanks for the well-prepared change request.

As you note in section 3 (Impact statement), there is a significant impact for UDDI V2 registries if we make the change for V2 also, especially if the tModel is already used often.

However, there is at least a similar impact for UDDI V3 registries that also support UDDI V2 APIs: at the time UDDI V3 is implemented, all keyedReferences to the V2 isReplacedBy identifier system within an identifierBag have to be migrated to then occur within a categoryBag. Otherwise, the V2/V3
multi-version registry would have to switch between the two personalities of the keyedReference on the fly - and would have to support two personalities of the same tModel for the different UDDI versions as well (note that the key for the isReplacedBy tModel is not changed).
But the migration would mean that V2 API call response messages would contain the isReplaceBy tModel as a category system, which is simply wrong per the V2 specification.
Thus, I have the dim feeling that we have to change the categorization for the isReplacedBy tModel already in V2 in order to prevent problems that can occur later.

An alternative could be to not change the categorization at all ...

Thoughts?

Claus

-----Original Message-----
From: Anne Thomas Manes [mailto:anne@manes.net] 
Sent: Mittwoch, 22. Januar 2003 00:39
To: Uddi-Spec
Subject: [uddi-spec] CR-010: isReplacedBy tModel




Anne Thomas Manes
617-497-1748 (land)
617-642-3144 (mobile)


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Powered by eList eXpress LLC