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

 


Help: OASIS Mailing Lists Help | MarkMail Help

uddi-dev message

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


Subject: RE: [uddi-dev] Service versioning in UDDI


The service binding (bindingTemplate) would include a tModel reference in the tModelInstanceInfos that points to the tModel that it implements. You could specify a version number in the instanceParms field (although you can't search based on this field).
 
You could also tag the service (businessService) with the version number category.
 
As I said, we really need to define a best practice for this topic. I'm just tossing out ideas, here. I haven't spent the time to identify the full set of requirements and design an effective solution yet.
 
Anne
-----Original Message-----
From: Mark Glass [mailto:mglass@hvc.rr.com]
Sent: Thursday, December 05, 2002 1:31 PM
To: uddi-dev@lists.oasis-open.org
Subject: Re: [uddi-dev] Service versioning in UDDI

Anne,
  Thank you for responding to my question. How would a subscriber distinguish the version when they do a find_service? Can the service info be included in the service description? If so, where and how?
 
Thakn you and Best Regards,
Mark
----- 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
-----Original Message-----
From: Mark Glass [mailto:mglass@hvc.rr.com]
Sent: Thursday, December 05, 2002 12:41 PM
To: uddi-dev@lists.oasis-open.org
Subject: [uddi-dev] Service versioning in UDDI

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


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


Powered by eList eXpress LLC