[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [wsdm] WSRF requirements for discovery
I will be overviewing the CIM Indications model tomorrow in the second half of the call, and it has a concept of lifecycle and alert indications. Just thought that I would highlight that and invite the discovery folks to stick around for the notifications discussion (even though most of you will anyway). Andrea > -----Original Message----- > From: Tom Maguire [mailto:tmaguire@us.ibm.com] > Sent: Friday, May 21, 2004 8:29 AM > To: Mark Ellison > Cc: John DeCarlo; Vambenepe, William N; Wsdm (E-mail) > Subject: Re: [wsdm] WSRF requirements for discovery > > > > > > > > Mark Ellison <ellison@ieee.org> wrote on 05/20/2004 05:30:02 PM: > > > Hi, > > > > After listening to the discussion today, it occurs to me that > > discovery > > (discoverability?) might be usefully described in terms of > > notifications. This is because I think the same fundamental > > architectural issues are at work when: > > > > (1) A consumer wishes to subscribe to notifications on a given > topic. > > (2) A consumer wishes to discover the existence of > resources for > > a given type > > (or, property list, or, attribute set, or, wsdl > fragment) > > > > If a ws-r were to emit a notification at instantiation time with a > > topic of "discovery", a reference to wsdl, its known epr > and publish > > within a brokered framework, then it would be possible for > a consumer > > to subscribe to a"discovery" topic (maybe a subtopic of a ws-r type > > would help here...). Subject, of course, to security and access > > rights, etc. > > +1 to standardized lifecycle events. Certainly that would be > something > that > we could take to WSRF as a requirement. > > > I am assuming that ws-n might support some mechanism for a > consumer to > > subcribe to a topic, like "discovery", and be able to > obtain the past > > (unique) events on topic. Such a list should ultimatedly > provide the > > discoverability consumer with a list of ws-r eprs, each as reported > > during instantiation by the ws-r itself. > > > > So, how might a structured "discovery" topic be worked into the ws-n > scheme? > > > > Comments? > > > > Regards, > > > > Mark > > > > > > > > John DeCarlo wrote: > > > > > > > > D) Managed Resource Creation/Deletion Events. Manageability > > > Consumer is there first. As each resource is made manageable, an > > > event (containing the EPR in the payload) goes to the Consumer. > > > > > > > > > > > > > > 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/wsdm/members/leave_workgroup.php. > > > > T o m M a g u i r e > > STSM, On Demand Architecture > Poughkeepsie, NY 12601 > > internet: tmaguire@us.ibm.com > phone: 845.433.9401 (t/l 293-9401) > > > > 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/wsdm/members/leav e_workgroup.php.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]