----- Original Message -----
Sent: Thursday, December 05, 2002 1:29
PM
Subject: RE: [uddi-dev] Service
versioning in UDDI
You've identified an area that sorely needs a best practice
document.
There is no formal mechanism available to indicate a relationship (such
as versioning) between tModels. What I would recommend is that you create a
couple of categorization tModels -- one that indicates version number, and one
that provides a reference to the original version tModel. Then you categorize
your tModels using these tModels.
Anne
I'm a beginner with UDDI and would appreciate
some insight with answers to the following questions:
Given the following scenario:
I publish a service to UDDI, it is revised and
I publish it again. How may I keep track of the service version in
UDDI?
I understand a usniques UDDI key is
generated each time a service is published and, if the publisher does not
generate the key then UDDI will. Is this true?
Id so, may I include the service version in the
UDDI? Is there a better way to keep track of the service and
version?
Where is the best place to keep the version
info from the subscribers point of view?
Thak you for your help.
Mark Glass
Software Developer
Datalinx Corp.
Tarrytown,
NY