RE: A proposal for an ebXML Publish Subscribe Service

[Krishna Sankar <ksankar@cisco.com>]

Hi,

	This actually has a lot of implications. The pub/sub & regrep need not be
an external entity; it can also help in the EAI areas internal to an
organization ! Publishing business events (like a price change to all buyers
or catalog providers) over interoperable framework, based on a standard is
required internally and externally.

	Another point is the asynchronous capability as well as the store and
forward capability for business messages. Even though all these concepts are
available now, they are not interoperable !

	Philippe/Farrukh, would this result in interoperable hubs ? Eventhough the
interoperability will make the switching costs low, it also opens up
opportunity for the hubs to conduct business in a utility model. SMEs would
definitely benefit out of this.

	More thoughts as we move along .....

	cheers


-----Original Message-----
From: Philippe DeSmedt [mailto:PDeSmedt@viquity.com]
Sent: Monday, October 30, 2000 2:19 PM
To: 'Krishna Sankar'; Farrukh Najmi; ebxml repository
Subject: RE: A proposal for an ebXML Publish Subscribe Service


All,

I agree with Krishna that a pub/sub model may be best supported through an
intermediary-based infrastructure. After all, pub/sub relies on some kind of
brokering mechanism between the sender and the receiver(s), i.e., a place
where senders publish their stuff and where receivers can register their
interest in receiving certain information ("topics" per the JMS lingo).

In other words, we require a registry of some sort. It would be advantageous
if the current thoughts and specs on registry could be applied to this
problem. I don't believe that there is anything in the specs that prevents
us from using a registry for the purpose of storing the information required
for pub/sub, and I think that doing so fits well within the functions that
we expect a registry to perform.

I fully support Krishna's notion to house the registry and the intermediary
(hub) under one roof, and I think that the way the registry is currently
spec'd allows them to coexist quite well. Using a registry to support
pub/sub is a natural thing to do in my mind. In this scenario, a hub could
be a client of a repository.

-Philippe
_______________________________
Philippe De Smedt
Architect
Viquity Corporation (www.viquity.com)
1161 N. Fair Oaks Avenue
Sunnyvale, CA 94089-2102
(408) 548-9722
(408) 747-5586 (fax)
pdesmedt@viquity.com


-----Original Message-----
From: Krishna Sankar [mailto:ksankar@cisco.com]
Sent: Monday, October 30, 2000 12:00 PM
To: Farrukh Najmi; ebxml repository
Subject: RE: A proposal for an ebXML Publish Subscribe Service


Hi,

	This is an excellent idea.

	We just architected and developed a B2B query and notification
service from
scratch using JMS because there are no standards. So this subject is very
near and dear to me.

	My only concern is that, this belongs to a hub/infomediary not a
registry/repository. We need to practice the object orientation - components
which do only one function and perform that one function well.

	If we could find a way to position the registry and the hub under
one roof,
it would be good.

	cheers

-----Original Message-----
From: Farrukh Najmi [mailto:Farrukh.Najmi@east.sun.com]
Sent: Monday, October 30, 2000 8:55 AM
To: ebxml repository
Subject: A proposal for an ebXML Publish Subscribe Service


ebXML RegRep List,

As we make progress on ebXML Registry, it is important for us as a team
to keep moving forward on important functionality that is needed for
ebXML
Registry and Repository. In that spirit I have attached a proposal for
that enables
pub/sub style brokered ebXML Messaging that
will allow for reliable many-to-many B2B communication between
parties.

The proposal relies and build upon both the ebXML Registry
Service as well as the ebXML Messaging Service. I am not sure where this

proposal fits best but my current thinking for a variety of reasons is
that it may be another Registry Service. Note that this proposal is
not a complete specification but meant only to spark the idea. Mahy
details
have been omitted in teh interest of brevity.

I would like us to engage in a discussion on this important subject
prior
to Tokyo with the goal of having a more detailed discussion on the topic

during our face-to-face meetings at Tokyo.

--
Regards,
Farrukh