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


Dan,

Thanks to both you and Scott for your thoughts and concerns. I agree that ebXML Registry should
not try and be a global business registry. I believe that is not the intent of Sanjay's proposal.

I believe Sanjay's proposal is bringing UDDI and ebXML closer together and providing a mapping
between UDDI
information model and ebXML. While the global nature of UDDI could be used to publish minimal
metadata for an
Organization, Service, ServiceBinding it could be mapped and routed to an ebXML Registry where
more detailed metadata
could be provided (including user defined metadata as Slots and including arbitrary
relationships). Finally the binding could
be linked to an ExtrinsicObject that is proxying an actual specification in the ebXML Registry's
repository.

Does the above scenario not use both registries in a complimentary manner?

Let us discuss the issue in the next RAWS sub-team meeting. I have not heard from you on your
time preference. So far tomorrow 2-3pm seems best for folks. I want to emphasize that we are not
going to do anything in haste here and will operate as a team to sort through the issues.

As far as Organization goes, we have had Organization in RIM since the earliest versions
and it is fairly important to our model.

Lastly, I would be very interested in contributing to the success of any sincere efforts to
bringing UDDI and ebXML Registry closer
in a meaningful manner. But until that happens, I feel we should not be ignoring the needs of
users of ebXML Registry and sitting by the sidelines waiting.

Dan Chang wrote:

> Farrukh,
>
> I agree with what Scott said in his note. I believe OASIS/ebXML Registry
> should NOT be a business registry, duplicating the functionality of UDDI,
> for reasons that Scott has pointed out. The industry does not need two
> overlapping specifications.
>
> If Sanjay's proposal is intended to facilitate the interoperability and
> integration of OASOS/ebXML Registry with UDDI, that will be very fine. For
> example, UDDI manages business definitions, business service interfaces and
> technical bindings, but it does NOT manage any corresponding specification
> documents. If Sanjay's proposal deals with these specification documents
> but NOT business definitions, business service interfaces or technical
> bindings, that will be very fine.
>
> 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
>
>
>                     Farrukh Najmi
>                     <Farrukh.Najmi       To:     Dan Chang/Santa Teresa/IBM@IBMUS
>                     @Sun.COM>            cc:     "Patil, Sanjay" <SPatil@iona.com>, Scott
>                                           Hinkelman/Austin/IBM@IBMUS,
>                     09/04/01 04:43        "'regrep-raws@lists.oasis-open.org'"
>                     PM                    <regrep-raws@lists.oasis-open.org>, Lisa Carnahan
>                                           <lisa.carnahan@nist.gov>
>                                          Subject:     Re: Proposal for supporting Service and
>                                           ServiceBinding
>
>
>
>
> Dan,
>
> This work item was sanctioned early on when we discussed work items for
> V2.0. We had discussed earlier in a
> RAWS meeting that we will include this item in the RAWS team as it is
> related to web services.
>
> I do not believe that our progress should be hindered by what is going on
> in UDDI. The UDDI team is
> constantly making changes in each release that duplicates ebXMl
> functionality. I cannot even discuss
> specific instances as it is private to the UDDI AG. On the other hand every
> thing in this TC is open for
> duplication.
>
> I feel that there is a string need for us to support the capabilities
> outlined by Sanjay and they fit well
> with focus on web services in this team. Please, lets focus on the merits
> of the proposal instead.
>
> Dan Chang wrote:
>
> > 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
> >
> > (See attached file: SupportServiceAndServiceBinding.doc)
> >
> >
> ------------------------------------------------------------------------
> >                                           Name:
> SupportServiceAndServiceBinding.doc
> >    SupportServiceAndServiceBinding.doc    Type: WINWORD File
> (application/msword)
> >                                       Encoding: BASE64
>
> --
> Regards,
> Farrukh
>
> #### najmi.vcf has been removed from this note on September 05 2001 by Dan
> Chang
>
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>

--
Regards,
Farrukh

begin:vcard 
n:Najmi;Farrukh
tel;work:781-442-0703
x-mozilla-html:FALSE
url:www.sun.com
org:Sun Microsystems;Java Software
adr:;;1 Network Dr. MS BUR02-302;Burlington;MA;01803-0902;USA
version:2.1
email;internet:najmi@east.sun.com
fn:Farrukh Najmi
end:vcard


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


Powered by eList eXpress LLC