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] | [List Home]


Subject: RE: [uddi-dev] UDDI registration data


Cindy,

The UDDI Version 3 Specification, section 3.5.2.2 (tModelInstanceDetails) shows you how it works:
"When a bindingTemplate is published it SHOULD contain a tModelInstanceDetails element that in turn contains in its tModelInstanceInfo structures one or more tModel references. This arbitrarily ordered collection of references is called the "technical fingerprint" of the Web service. It indicates
that the Web service being described complies with the specific and identifiable specifications implied by the tModelKey values provided. During an inquiry, interested parties can use this information to look for bindingTemplate entities that contain a specific fingerprint or partial fingerprint."

Regards,
 Claus von Riegen, SAP AG

-----Original Message-----
From: Cindy Tong [mailto:c.tong@student.qut.edu.au] 
Sent: Montag, 17. März 2003 09:03
To: uddi-dev@lists.oasis-open.org
Subject: [uddi-dev] UDDI registration data


Dear list,

I am currently doing a case study on classifying Web services based on the
tModels they implement using data mining techniques. Is there any way that
I can get UDDI registration entries with tModels for bindingTemplates so
that I can test out my case?

My understanding on tModels is that services that comply to certain
concepts can claim to implement the corresponding tModel. Therefore,
services that implement the same set of tModels are similar in some way. Is
this correct?

Regards,
Cindy Tong




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