RE: [wsdm] 'Expensive' metadata element

[Heather Kreger <kreger@us.ibm.com>]

Ok, lets let it ride to V2. 

Heather Kreger
STSM, Web Services Lead Architect for SWG Emerging Technologies
Author of "Java and JMX: Building Manageable Systems"
kreger@us.ibm.com
919-543-3211 (t/l 441)  cell:919-496-9572

"Andrea Westerinen" <andreaw@cisco.com>

11/18/2004 05:44 PM

To	Heather Kreger/Raleigh/IBM@IBMUS, <wsdm@lists.oasis-open.org>
cc
Subject	RE: [wsdm] 'Expensive' metadata element

Expensive is not a standard DMTF qualifier, and kind of
 subjective.  Do we need it in V1?
 
Andrea

---

From: Heather Kreger  [mailto:kreger@us.ibm.com]

Sent: Thursday, November 18, 2004 2:24  PM
To: wsdm@lists.oasis-open.org
Subject: [wsdm]  'Expensive' metadata element


In response to my action  Item to propose an 'Expensive'
metadata element for any property or operation,  

/(wsdm:MUWS)/expensive 
Metadata element indicates the if the retrieval or setting
of the  property or invocation of an operation is expensive 
for the manageable resource to execute.   Expensive
is relative to the perception and resources of the  
resource.    

  <xs:element name="expensive"  type=’xs:boolean’/>


   <expensive>xs:boolean</expensive>


If there are no objections tomorrow, then William  should
add this to MUWS. 

Of  course, you can still comment on this during
review due on the 29th.  

Heather Kreger
STSM, Web  Services Lead Architect for SWG Emerging
Technologies
Author of "Java and  JMX: Building Manageable
Systems"
kreger@us.ibm.com
919-543-3211 (t/l  441)  cell:919-496-9572