RE: [wsdm] Definition of the identification manageability capability

["Sedukhin, Igor S" <Igor.Sedukhin@ca.com>]

William, 

You said [In addition, do you agree Igor that your proposed text does not preclude the provider to tell the consumer about more than one description/pointer to the resource it manages if this is appropriate?]

Description document location, yes. Pointer/reference, NO! The provider returns A reference in pererably standard form. No reason to rerturn all possible variations of the reference.
The text does not preclude, however common sense does :). This is exactly the argument for not overengineering. 

-- Igor Sedukhin .. (igor.sedukhin@ca.com)
-- (631) 342-4325 .. 1 CA Plaza, Islandia, NY 11788

-----Original Message-----
From: VAMBENEPE,WILLIAM (HP-Cupertino,ex1) [mailto:vbp@hp.com] 
Sent: Thursday, December 11, 2003 11:45 AM
To: 'John DeCarlo'; Sedukhin, Igor S
Cc: WSDM TC
Subject: RE: [wsdm] Definition of the identification manageability capability


I agree with John, this is a good and important clarification. In addition, do you agree Igor that your proposed text does not preclude the provider to tell the consumer about more than one description/pointer to the resource it manages if this is appropriate?

Regards,

William

> -----Original Message-----
> From: John DeCarlo [mailto:jdecarlo@mitre.org]
> Sent: Friday, December 12, 2003 8:35 AM
> To: Sedukhin, Igor S
> Cc: WSDM TC
> Subject: Re: [wsdm] Definition of the identification manageability 
> capability
> 
> 
> Sedukhin, Igor S wrote:
> 
> > I propose that the following text is incorporated in MUWS
> and MOWS specs.
> >
> > "The identification capability allows the provider of
> manageability to
> > tell what it thinks it is managing. In other words
> refer/address/point
> > to the resource it thinks it made manageable. The exact way of 
> > "referring" conforms to the subject domain of the resource."
> >
> Igor,
> 
> This looks nice, but I have some comments on it.
> 
> 1.  I feel somewhat strongly that the "identification" be opaque and 
> unique and not domain specific.
> 2.  What you describe is crucial, but it would be nice to be sure that 
> it isn't confused with the global MUWS identifier for the resource.
> 
> Thus, I propose the following:
> 
> "The identification capability provides the consumer of manageability 
> with a [globally] unique identifier for each managed resource the 
> provider of manageability thinks it is managing.  This identifier is 
> opaque (not decomposable into domain-specific information about the 
> resource).  It can be used to compare the answers from different 
> providers to see if they are both managing the same resource."
> 
> "The managed resource reference capability allows the provider of 
> manageability to tell the consumer information about what it thinks it 
> is managing. In other words refer/address/point to the resource it 
> thinks it made manageable. The exact way of "referring"
> conforms to the
> subject domain of the resource."
> 
> What do you think?
> 
> Thanks.
> 
> John DeCarlo, The MITRE Corporation, My Views Are My Own
> 
> 
> 
> 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/leave_workgroup.php.