[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [Fwd: Re: WSDL and pub/sub]
FYI... Interesting thread on email@example.com on ebXML Registry event notification. Archives may be viewed at: http://lists.w3.org/Archives/Public/public-ws-chor -- Regards, Farrukh -------- Original Message -------- Subject: Re: WSDL and pub/sub Resent-Date: Tue, 17 Feb 2004 07:38:37 -0500 (EST) Resent-From: firstname.lastname@example.org Date: Tue, 17 Feb 2004 07:38:33 -0500 From: Farrukh Najmi <Farrukh.Najmi@Sun.COM> To: email@example.com CC: firstname.lastname@example.org, UCorda@SeeBeyond.com, Monica.Martin@Sun.COM, email@example.com, firstname.lastname@example.org, email@example.com References: <99F57F955F3EEF4DABA7C88CFA7EB45A0CB9999D@c1plenaexm04.commerceone.com> firstname.lastname@example.org wrote: >Monica, Joseph, Ugo et al > >A question. Just suppose you wanted to use the ebXML RR spec with other XML documents designed to support the Auction use case I described earlier, would there be any issues that you can think of. For example ... would you need to have an ebXML Registry to store information about Auction objects? > > David, Funny you should mention an auction scenario and ebXML Registry. See a recent exchange below where I used the same scenario in the context of ebXML Registry event notification. I feel that ebXML Registry event notification could be used to support multi-party collaboration scenarios as the next logical step from binary collaborations exemplified by ebXML Messaging and SOAP. As it currently stands, registry events are only triggered when a CREATE/UPADTE/DELETE operation occurs in the registry. For example a BiddableObject must be written to registry to represent that something is open for bids. Bidders would be subscribed to BiddableObjects and will be notified. They can then write Bid objects to the registry. The auctioneer would be subscribed to Bids for "their" BiddableObjects and will be notified when a Bid is placed. They would have to write a BidResult object to registry when bidding closes and all Bidders would be notified of the BidResult. So yes several objects would have to be written to the registry in order to support this scenario. -- Regards, Farrukh -------- Original Message from Farrukh on regrep in reply to Joe -------- Subject: Re: [regrep] Direct Data Exchange vs. SOA Date: Wed, 11 Feb 2004 10:50:12 -0500 From: Farrukh Najmi <Farrukh.Najmi@Sun.COM> To: Chiusano Joseph <email@example.com> CC: firstname.lastname@example.org <email@example.com> References: <402A4C2C.C65CF5F1@bah.com> Chiusano Joseph wrote: >I have an inquiry that is not directly related to our mission here, but >I hope to get some good insight in response please: > >Let's say we have a purchase order process between trading partners (PO >sent, Invoice received). There are (for the purposes of this inquiry) 2 >possible ways to handle this process: > >(1) Direct Data Exchange (create XML documents based on a common schema, >and exchange them between trading partners) > >(2) SOA (have a purchase order/invoice shared service that is discovered >in a registry, etc.) > >My inquiry is: What would drive an organization to use one approach or >the other, from both a business and technical standpoint? For instance, >would "critical mass of services and/or trading partners" be a driver >for SOA vs. direct data exchange? > > > The second approach allows for multi-party colaboration instead of binary collaboration. It would rely on Registry Event notification. An example would be a bidding or auction scenario.