Hi Kasun,
I think your use of the TModel for additional information is ok, check
out some of the uses for 'other core TModels':
http://www.uddi.org/taxonomies/UDDI_CoreOther_tModels.htm. In particular
the Telephone specification seems pretty much what you want
<tModel tModelKey="uuid:38E12427-5536-4260-A6F9-B5B530E63A07">
<name>uddi-org:telephone</name>
<description xml:lang="en">Telephone based service</description>
<overviewDoc>
<description xml:lang="en">
This tModel is used to describe a service that is invoked through
a telephone call
and interaction by voice and/or touch-tone.
</description>
<overviewURL>
http://www.uddi.org/taxonomies/UDDI_CoreOther_tModels.htm#overPhone
</overviewURL>
</overviewDoc>
<categoryBag>
<keyedReference tModelKey="uuid:C1ACF26D-9672-4404-9D70-39B756E62AB4"
keyName="tModelType"
keyValue="specification"/>
</categoryBag>
</tModel>
So in this case the keyValue of 'specification' is used. So it really
depends on how you want to
categorize your documentation references. If there is no existing
categorization scheme that fits
your documents, then you can always create your own.
Is this what you are looking for?
--Kurt
On 1/4/11 1:03 PM, Kasun Weranga wrote:
Hi Tom,
Thanks for your reply, According to UDDI spec The discoveryURL only
appears at the businessEntity level, But this additional
documentations are specific to a service. (Because this documents
describe details of a particular service). So in that case how can I
publish these information into UDDI? Also I would like to know what is
wrong with above TModel?
I really appreciate your help.
Thank you,
Kasun.
On Tue, Jan 4, 2011 at 3:11 AM, Tom Cunningham <[email protected]
<mailto:[email protected]>> wrote:
This doesn't sound to me like the correct use of TModel. I'd
suggest re-reading the UDDI docs - it sounds to me like what you
are looking for are discoveryURLs.
http://www.oasis-open.org/committees/uddi-spec/doc/spec/v3/uddi-v3.0.2-20041019.htm
On 12/31/2010 09:07 AM, Kasun Weranga wrote:
Hi all,
I am doing a project in which I publish service details into
jUDDI registry.
In service user interface of our project we capture relevant
information relating to the service (service name, service
description, WSDL url, and additional documentation regarding the
service etc..).
By using those captured information from service UI, I was able
to successfully publish the service details in to UDDI registry.
(I used WSDL to UDDI mapping too).
But when I going to publish the additional documents relating to
the service as separate TModels. I couldn't find a standard way
for doing that.
I came up with following TModel.
/<tModel tModelKey="" >
<name>
*[Document Name]*
</name>
<overviewDoc>
<description xml:lang="en">
*[DESCRIPTION_GOES_HERE]*
</description>
<overviewURL useType="text">
*[URL_GOES_HERE]*
</overviewURL>
<overviewDoc>
</tModel>
But problem is what are the KeyedReferences in CategoryBag should
be? Since I couldn't find relevant KeyedReferences I kept
CategoryBag field empty. Is it right?
Can anyone tell me what are the KeyedRefrences?
I really appreciate your help
//
/Can anyone help me ?
Thanks,
Kasun.
--
Kasun Weranga Gunathilake.
Dept of Computer Science & Engineering
University of Moratuwa
Sri Lanka.
