[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: [uddi-comment] tModel question II
Hi, When registering web services, web service producers could provide both a WSDL file and a project web site that contains additional documentation. Now, the producer could create two tModels, one for the WSDL file, one for the project web site, or he/she could create one tModel for the WSDL file and have a second <overviewDoc> that describes the project web site. My question is: is there a best practice in this area? Has anyone had to face a similar situation? (Since the WSDL file and project web sites are related, but different specs, it seems having two tModels more clearly separates and organizes the data, and fits better with the UDDI data model. However, two tModels involves more data and administrative support.) Thanks, Paul
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC