Re: [regrep] Using BPEL4WS in...an ebXML Registry?

["Goran Zugic" <gzugic@ebxmlsoft.com>]

Hi Joe and Farrukh,

I am very interested in this. ebXMLsoft is working on EFERA (ebXML Federated
Enterprise Reference Architecture) product with ebXMLsoft Registry and
Repository as a central component.  This paper

http://www.ebxmlsoft.com/papers/ebxml-fera.pdf

gives more details about EFERA. We are planning to use WS BPEL as a standard
spec for internal collaborations. ebXML BPSS will be used for external
collaborations.

Regards,
Goran

----- Original Message ----- 
From: "Farrukh Najmi" <Farrukh.Najmi@Sun.COM>
To: <regrep@lists.oasis-open.org>
Sent: Tuesday, December 21, 2004 6:02 PM
Subject: Re: [regrep] Using BPEL4WS in...an ebXML Registry?


> Chiusano Joseph wrote:
>
> > Not trying to be a copycat here - just noticing a potential value in
> > this for ebXML Registry as well:
> >
> > The UDDI TC is in the process of creating a TN for "Using BPEL4WS in a
> > UDDI Registry[1]". Is this something that would be valuable for ebXML
> > Registry as well? If so, we may consider waiting until WS BPEL is
> > complete rather than basing it on BPEL4WS.
> >
> > From the UDDI TC site, document description: "This proposed technical
> > note describes a standardized mapping approach between BPEL4WS
> > abstract processes and UDDI in order to make Web services discoverable
> > that implement a certain role within an abstract process definition."
> >
> > [1]
> >
http://www.oasis-open.org/committees/download.php/8442/uddi-spec-tc-tn-bpel-20040725.pdf
> >
> > Kind Regards,
> > Joseph Chiusano
> > Booz Allen Hamilton
> > Strategy and Technology Consultants to the World
> >
>
> I have had some discussion on the BPEL TC lists on this a while back.
> The TN is a good idea but as always the question is who is willing to
> write it.
> Any volunteers?
>
> -- 
> Regards,
> Farrukh
>
>
> To unsubscribe from this mailing list (and be removed from the roster of
the OASIS TC), go to
http://www.oasis-open.org/apps/org/workgroup/regrep/members/leave_workgroup.
php.
>
>