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

[Farrukh Najmi <Farrukh.Najmi@Sun.COM>]

Paul Denning wrote:
> 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".

I am quite clear that the "ebXML Registry Profile for WSDL" is a *draft* 
specification and never claimed anything but.

>
> 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

Above is not a correct understanding. The "ebXML Registry Profile for 
WSDL" or any other "ebXML Registry Profile for XXX" have nothing to do 
"deployment profile template (DPT)". The term "profile" is being used 
for two unrelated uses. It has been suggested to the ebXML IIC to 
cosnider using a different name than "profile" because of the prevalent 
us of that term in standards circles. Examples of the dominant use of 
the term "profile" are WS-I Basic Profiles, various profiles defined by 
XAML, SAML and WSS standards.

>
> 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.

See above. You are bringing in something totally unrelated out of 
left-field.

> If so, I don't think the WS profile, and Registry DPT, have yet 
> progressed to a Committee Draft.

And I have not claimed that it has. I have been very clear that it is a 
*draft* specification. What am I missing here?

> Claiming that the ebXML Registry Profile for WSDL is a normative 
> specification, at this time, is misleading.

I think you are confusing the term "normative" (opposite is 
non-normative) from the term "approved" (opposite is draft).

See definition at:

http://en.wikipedia.org/wiki/Normative#Standards

<definition>

In standards <http://en.wikipedia.org/wiki/Standardization> terminology, 
"normative" means "considered to be a prescriptive 
<http://en.wikipedia.org/wiki/Prescriptive> part of the standard". For 
example, many standards have an introduction, preface, or summary that 
are considered non-normative, as well as a main body that is considered 
normative. "Compliant" is defined as "complies with the normative 
sections of the standard"; an object that complies with the normative 
sections but not the non-normative sections of a standard is still 
considered to be in compliance.

[edit 
<http://en.wikipedia.org/w/index.php?title=Normative&action=edit&section=2>]

</definition>

A specification can be a draft and normative which is the case for the 
"ebXML Registry Profile for WSDL".

>
> 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.

Again the "ebXML Registry Profile for WSDL" has nothing to do with DPT. 
You made that incorrect assumption.

>
> 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/ .

All profile of ebXML Registry specification are normative.
Thanks for the suggestion. We will clarify this somewhere.


>
>
>> 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 is nothing ambiguous about the standing of the ebXML Registry 
Profile for WSDL.
I sure hope you are not trying to create FUD with statement like above ;-)

For the record, "ebXML Registry Profile for WSDL" is a draft normative 
specification that is a profile of ebXML Registry 3.0 standard. It will 
be an approved standard in a few months if all goes well.

We will take your suggestion above and have the ebXML Registry TC state 
this officially and publicly.

Lastly, You have expressed your concern in uddi-spec TC that the use of 
the term profiles may be positioning ebXML Registry profiles more 
favorably in people's eyes than UDDI TNs.

http://lists.oasis-open.org/archives/uddi-spec/200509/msg00013.html

I should point out that you are quite mistaken that they are the same 
thing but just called different names.

The difference is that:

-UDDI TNs are non-normative, while

-ebXML Registry profiles are normative specifications (draft or not).

Hope this clears up some misunderstanding. Thank you.

<some off-topic stuff deleted>

-- 
Regards,
Farrukh


begin:vcard
fn:Farrukh Najmi
n:Najmi;Farrukh
email;internet:farrukh.najmi@sun.com
tel;work:781-442-9017
url:http://ebxmlrr.sourceforge.net/tmp/farrukhRacePointIcon.jpg
version:2.1
end:vcard