RE: [wsdm] Groups - Applying WS-N to WSDM .doc uploaded

[Steve Graham <sggraham@us.ibm.com>]

+1

++++++++
Steve Graham
(919)254-0615 (T/L 444)
STSM, On Demand Architecture
Member, IBM Academy of Technology
<Soli Deo Gloria/>
++++++++

Tom Maguire/Hawthorne/IBM@IBMUS 06/25/2004 07:44 AM

To:        "Vambenepe, William N" <vbp@hp.com>         cc:        "Sedukhin, Igor S" <Igor.Sedukhin@ca.com>, "Stephen Schleimer" <sschlmr@cisco.com>, wsdm@lists.oasis-open.org         Subject:        RE: [wsdm] Groups - Applying WS-N to WSDM .doc uploaded

+1 to sending the requirement to WSRF-RP.


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

"Vambenepe, William N" <vbp@hp.com> wrote on 06/24/2004
02:04:20 PM:

>
> We agree. Does anybody have a problem with WSDM sending this as a
> requirement to WSRF?
>
> William
>
> > -----Original Message-----
> > From: Sedukhin, Igor S [mailto:Igor.Sedukhin@ca.com]
> > Sent: Thursday, June 24, 2004 11:00 AM
> > To: Vambenepe, William N; Stephen Schleimer
> > Cc: wsdm@lists.oasis-open.org
> > Subject: RE: [wsdm] Groups - Applying WS-N to WSDM .doc uploaded
> >
> >
> > I think this is another one that WSRF-RP needs to define.
> > E.g. yet another topic for all property changes.
> >
> >
> > -- Igor Sedukhin .. (igor.sedukhin@ca.com)
> > -- (631) 342-4325 .. 1 CA Plaza, Islandia, NY 11788
> >
> > -----Original Message-----
> > From: Vambenepe, William N [mailto:vbp@hp.com]
> > Sent: Thursday, June 24, 2004 1:31 PM
> > To: Stephen Schleimer
> > Cc: Sedukhin, Igor S; wsdm@lists.oasis-open.org
> > Subject: RE: [wsdm] Groups - Applying WS-N to WSDM .doc uploaded
> >
> >
> > Yes, this mapping is the kind of use case I have in mind that
> > leads me to saying that we might need a convenient way to
> > subscribe to notification on property change for all
> > properties (or at least all these for which notification is
> > supported).
> >
> > If we limit ourselves to approach -1-, there are two ways to
do this:
> > - send as many subscriptions are there are properties
> > - if the manageability representation supports the "FullTopicPath"
> > expression type, you can subscribe on ALL topics and then use
> > "Selector"
> > to only receive notification messages of type
> > "PropertyChangeNotification".
> >
> > None of these is very convenient.
> >
> > The question is: is this convenient enough considering the
> > expected prevalence of this use case?
> >
> > Or do we want to make this easier by, in addition to the
> > approach in -1-, defining one
> > "ChangeInAnyPropertyInAnyNamespace" topic. This additional
> > topic would not violate WSRP. In fact, we could even try to
> > bump this down to WSRF and ask WSRP to define this topic. Or
> > we could do it in WSDM.
> >
> > Regards,
> >
> > William
> >
> > > -----Original Message-----
> > > From: Stephen Schleimer [mailto:sschlmr@cisco.com]
> > > Sent: Thursday, June 24, 2004 9:56 AM
> > > To: Vambenepe, William N
> > > Cc: Igor.Sedukhin@ca.com; wsdm@lists.oasis-open.org
> > > Subject: Re: [wsdm] Groups - Applying WS-N to WSDM .doc
uploaded
> > >
> > >
> > > It might be worth examining the DMTF IndicationSubscription
> > model.  It
> > > has the flexibility to subscribe to none, some, or all
> > properties of
> > > tracked class instances.
> > >
> > > -steve
> > >
> > > Vambenepe, William N wrote:
> > >
> > > >Thanks Igor, nice rightup, very clear and readable.
> > > >
> > > >I agree with pretty much everything. The only question
I see
> > > for us to
> > > >answer, is what set of topics do we define. Options
are:
> > > >
> > > >-1- when we define a new property in MUWS or MOWS we
decide
> > > whether or
> > > >not to create a topic for modification of this property
(I
> > > think this is
> > > >your recommendation)
> > > >
> > > >-2- use only one topic, the same for any property
> > > modification (and use
> > > >Selector to narrow down to some properties). But if
we do
> > > this, how do I
> > > >know which properties support sending notifications
on change?
> > > >
> > > >-3- a mix of -1- and -2-, where both sets of topics
are
> > available and
> > > >people decide whether to register on a property-specific
> > > topic or on the
> > > >general "property change" topic (assuming
the manageability
> > > >representation offers both.
> > > >
> > > >The reason I bring this up is that I am thinking that
some
> > managers
> > > >might just want to stay synched with the resource and
get all
> > > >notifications for all properties. If this is the case,
> > > registering on a
> > > >per-property basis is not very convenient.
> > > >
> > > >Regards,
> > > >
> > > >William
> > > >
> > > >
> > > >
> > > >
> > > >>-----Original Message-----
> > > >>From: Igor.Sedukhin@ca.com [mailto:Igor.Sedukhin@ca.com]
> > > >>Sent: Thursday, June 17, 2004 9:16 AM
> > > >>To: wsdm@lists.oasis-open.org
> > > >>Subject: [wsdm] Groups - Applying WS-N to WSDM .doc
uploaded
> > > >>
> > > >>
> > > >>The document Applying WS-N to WSDM .doc has been
> > submitted by Igor
> > > >>Sedukhin (Igor.Sedukhin@ca.com) to the OASIS Web
Services
> > > >>Distributed Management TC document repository.
> > > >>
> > > >>Document Description:
> > > >>Looked at MUWS State capability events and using
property change
> > > >>notifications to cover it.
> > > >>
> > > >>Download Document:
> > > >>http://www.oasis-open.org/apps/org/workgroup/wsdm/download.php
> > > >>/7320/Applying%20WS-N%20to%20WSDM%20.doc
> > > >>
> > > >>View Document Details:
> > > >>http://www.oasis-open.org/apps/org/workgroup/wsdm/document.php
> > > >>?document_id=7320
> > > >>
> > > >>
> > > >>PLEASE NOTE:  If the above links do not work
for you, your email
> > > >>application may be breaking the link into two pieces.
 You may be
> > > >>able to copy and paste the entire link address into
the address
> > > >>field of your web browser.
> > > >>
> > > >>
> > > >>
> > > >>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.
> > > >
> > > >
> > > >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.
> > >
> > >
> > >
> >
> >
> > 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_workgrou
> p.php.
>
>
> 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_workgrou
> p.php.
>
>
>
> 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_workgrou
> p.php.
>
>
> 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.
>


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.