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

 


Help: OASIS Mailing Lists Help | MarkMail Help

uddi-comment message

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


Subject: RE: [uddi-comment] tModel question II


Hi Paul,

Basically, the answer depends on what you mean by "project web site."
- If you mean a web site where the Web service that implements the WSDL document can be accessed online, for example, by using HTML forms, the web site should be modeled as a separate <bindingTemplate> (in parallel to the <bindingTemplate> that represents the Web service) and its <accessPoint> should contain the web site's URL. There is no need to model a separate <tModel> since there is obviously no reuse in this case.
- If you rather mean a web site where additional documentation about the offered Web service is offered, such as authentication requirements or billing methods, this information should be modeled as a separate <overviewDoc> within the same <tModel> that represents the Web service type described by the WSDL document. The feature to add multiple <overviewDoc> elements to a <tModel> was introduced in UDDI Version 3 due to the very scenario.
Unfortunately, UDDI Version 2 does not allow multiple <overviewDoc> elements. You should then rather refer to the WSDL document only in order to meet the requirements from UDDI's WSDL best practice.

Best regards,
 Claus von Riegen, SAP

-----Original Message-----
From: Paul Sterk [mailto:paul.sterk@sun.com]
Sent: Dienstag, 15. Oktober 2002 19:20
To: uddi-comment@lists.oasis-open.org
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


----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>


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


Powered by eList eXpress LLC