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

 


Help: OASIS Mailing Lists Help | MarkMail Help

regrep-raws message

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


Subject: Re: Proposal for supporting Service and ServiceBinding


---------------------- Forwarded by Scott Hinkelman/Austin/IBM on
09/05/2001 10:54 AM ---------------------------

Scott Hinkelman
09/05/2001 07:47 AM

To:   "Patil, Sanjay" <SPatil@iona.com>
cc:   Dan Chang/Santa Teresa/IBM@IBMUS,
      "'regrep-raws@lists.oasis-open.org'"
      <regrep-raws@lists.oasis-open.org>
From: Scott Hinkelman/Austin/IBM@IBMUS
Subject:  Re: Proposal for supporting Service and ServiceBinding  (Document
      link: Scott Hinkelman)

Sanjay,
Your proposal very closely matches similar functionality centered directly
around that of UDDI, and I share Dan's concern. With your proposal,
the raws subgroup is operating in a space where other efforts have made
significant contribution and increasing traction, only by great expense of
involved companies.

In order to address some of what is in your proposal, for businesses to
find services, on the larger picture of global eBusiness we must take into
account the global topology structure. UDDI certainly is covering the
global position for bussinesses find services, etc, and nobody should
underestimate what it takes to provide and initially implement such a
global business directory, taking into account distribution/replication,
single fail point, etc. My position is that at this point, it will be a
very large undertaking for anyone or company to replicate that, be it using
a UDDI reg or ebXML reg, and the greatest possiblity of success for a
gloabl Business registry for services is in UDDI. This might sound harsh,
and not directly pointed at you, but any attempt to overlay UDDI's core
functionality will likely have minimal success at this point.

I believe now as things have moved forward that one succesful positioning
otion for ebXML registry is to NOT be a business registry and have no
notion of Organization. I would like to understand more on your thoughts on
topology - are you thinking would there be many ebXML registries with your
proposed UDDI-like function, or a global image like the UDDI-cloud?

Scott Hinkelman, Senior Software Engineer
XML Industry Enablement
IBM e-business Standards Strategy
512-823-8097 (TL 793-8097) (Cell: 512-940-0519)
srh@us.ibm.com, Fax: 512-838-1074



From: Dan Chang on 09/04/2001 03:58 PM

To:   "Patil, Sanjay" <SPatil@iona.com>
cc:   Scott Hinkelman/Austin/IBM@IBMUS,
      "'regrep-raws@lists.oasis-open.org'"
      <regrep-raws@lists.oasis-open.org>
From: Dan Chang/Santa Teresa/IBM@IBMUS
Subject:  Re: Proposal for supporting Service and ServiceBinding  (Document
      link: Scott Hinkelman)

Sanjay,

I am concerned that in doing so we will explicitly overlap and repeat what
has been done in UDDI. I believe we ought to first resolve the issue on
positioning OASIS/ebXML Registry with UDDI, as suggested by Scott.

Regards,  Dan

Metadata Management Technology and Standard
IBM DBTI for e-Business
Notes:     Dan Chang/Santa Teresa/IBM@IBMUS
Internet:  dtchang@us.ibm.com
VM:          IBMUSM50(DTCHANG)
Phone:    (408)-463-2319


                                                                                                                
                    "Patil,                                                                                     
                    Sanjay"              To:     "'regrep-raws@lists.oasis-open.org'"                           
                    <SPatil@iona.c        <regrep-raws@lists.oasis-open.org>                                    
                    om>                  cc:                                                                    
                                         Subject:     Proposal for supporting Service and ServiceBinding        
                    09/04/01 03:05                                                                              
                    PM                                                                                          
                                                                                                                
                                                                                                                




Here is a proposal for supporting Service and ServiceBinding objects
as first class object in the RIM.
 <<SupportServiceAndServiceBinding.doc>>

In order to be readily useful, a registry needs to have inherent support
for
the commonly used business documents. Business Service interface and the
technical binding of these Business Service interfaces seem to be falling
in
such a category.

           1.        Providing inherent support for common business
documents.
           2.        Functionally complete in comparison with other
Registry
Standards

Please review the proposal and let us start discussing it over the mail
list.

thanks,
Sanjay Patil
----------------------------------------------------------------------------

------------------------------
IONA
Total Business Integration (TM)
Phone: 408 350 9619                                 http://www.iona.com












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


Powered by eList eXpress LLC