Re: [uddi-dev] How can I register my Web Service?

[Paul Denning <pauld@mitre.org>]

At 07:15 PM 2006-04-27, Farrukh Najmi wrote:
> rafiqy@blueyonder.co.uk
> wrote:
> > Hi All,
> >
> > I am a final year student and as part of my finaly year project I
> > have
> > developed a Web Service, but not yet registered it with a service
> > broker,
> > can someone please adivice me how can I register this service with
> > UDDI?
> >
> >   
> Hi Yasmin,
>
> Since no one has answered I thought I should provide some information.
> There is a UDDI Technical Note on this:
>
> http://www.oasis-open.org/committees/uddi-spec/doc/tn/uddi-spec-tc-tn-wsdl-v2.htm
>
> Also if you wish to broaden your horizons then you may consider the
> following draft specification for "ebXML Registry Profile for
> WSDL":
>
> http://ebxmlrr.sourceforge.net/tmp/regrep-ws-profile-1.0.pdf
>
> The above document is a normative specification 



We need to be a little careful about the status of these
documents.

The OASIS process discusses this:
http://www.oasis-open.org/committees/process.php

Draft documents can be voted on by Tech Committees (TCs) to become
"Committee Drafts"
Committee Drafts then progress to "Committee
Specifications"
A TC may vote to submit a Committee Spec to the OASIS membership to
eventually become an "OASIS Standard".

My understanding is that the this "profile" should be an
instance of "deployment profile template (DPT)".
There are several DPT's in the works:
http://tinyurl.com/kd8p8

It is not clear if "profiles" and DPT's are on a standards
track (to borrow an IETF term), in which case, the OASIS process would
apply.
If so, I don't think the WS profile, and Registry DPT, have yet
progressed to a Committee Draft.  
Claiming that the ebXML Registry Profile for WSDL is a normative
specification, at this time, is misleading.

If a profile or DPT is not a standards track spec, then the regrep TC
should define a process to explain what 
"normative specification"
means.

The UDDI TN and BPs have a process that the OASIS UDDI Spec TC
follows:
http://www.oasis-open.org/committees/uddi-spec/doc/bps.htm#Process

<q>
A Technical Note is a non-normative document accompanying
the UDDI Specification that provides guidance on how to use UDDI
registries. While Technical Notes represent the UDDI Spec TC’s view on
some UDDI-related topic, they may be prospective in nature and need not
document existing practice. 
 

A Best Practice is a non-normative document accompanying a UDDI
Specification that provides guidance on how to use UDDI registries. Best
Practices not only represent the UDDI Spec TC’s view on some UDDI-related
topic, but also represent well-established practice.
</q>
(see link for more info about the process)

That is, the UDDI Spec TC does not currently consider TN's and BP's to be
standards track, so they have defined a TN/BP process.

It would be nice if regrep TC clarified the
process applicable to profiles and DPTs.


> for how to publish,
> manage, govern, discover and reuse WSDL documents within an ebXML
> Registry. The freebXML Registry open source project has an implementation
> of this draft spec 

Draft spec
http://tinyurl.com/rr6mo


Given the ambiguous standing of the ebXML Registry Profile for WSDL, I
can offer the following comment.

There has been discussion of a UDDI Inquiry API front end to an ebXML
Reg/Rep.  
http://www.sun.com/products/soa/registry/#registry
http://tinyurl.com/lroao  (Three-Tier Vision)

The UDDI TN for WSDL,

http://tinyurl.com/em7o7
provides some sample UDDI queries, both v2 and v3.  A slightly
modified example follows:

<find_tModel generic="2.0"
xmlns="urn:uddi-org:api_v2">
    <name>%</name>
    <categoryBag>
        <keyedReference
         
tModelKey="uuid:6e090afa-33e5-36eb-81b7-1ca18373f457"
          keyName="WSDL
type"
         
keyValue="portType"/>
     </categoryBag>
</find_tModel>

This UDDI query would discover all tModels in the registry for WSDL files
that define a "portType" in accordance with the UDDI
TN.

If WSDL documents were cataloged in accordance with the ebXML Registry
Profile for WSDL, and the above find_tModel query (or a v3 equivalent)
was submitted to a UDDI front-end to the ebXML Registry, I do not think
that the tModels for these WSDL documents would be discovered. 
Please verify this claim.

(Its not clear how section 11.1 and 4.4.1 of the ebXML profile can be
mapped to the UDDI taxonomy identified by the tModelKey
uuid:6e090afa-33e5-36eb-81b7-1ca18373f457 as defined in Appendix B.1 of
the UDDI TN).

It seems invalid to assume that you can publish and catalog a WSDL using
ebRS, then find them using a UDDI Inquiry API to the same registry. 
This limits the value of providing a UDDI Inquiry API to query an ebXML
Registry.
It would be nice if the ebXML Registry Profile for WSDL could be
harmonized with the UDDI TN.  Without such harmonization, a UDDI
Inquiry front-end to a native ebXML reg/rep is not too useful, and the
decision whether to use ebXML or UDDI as a registry for SOA governance
should consider this.  I get the feeling that the proponents of
ebXML Reg/Rep think you can get the best of both worlds by having a UDDI
Inquiry front-end, but I have my doubts.

Paul


> available:
>
> http://ebxmlrr.sourceforge.net/wiki/Overview
>
> Best of luck in your educational endeavors.
>
> -- 
> Regards,
> Farrukh