WIMS> CIM> There is one possible candidate for EnabledLogicalElement

WIMS> CIM> There is one possible candidate for EnabledLogicalElement

WIMS> CIM> There is one possible candidate for EnabledLogicalElement

Richard_Landau at Dell.com Richard_Landau at Dell.com
Thu Apr 19 14:50:45 EDT 2007


Actually, I would propose calling the class ConsoleButtons or
ConsoleInput.  The existing function does not disable the lights or text
display, only input from the buttons.  
 
rick

________________________________

From: owner-wims at pwg.org [mailto:owner-wims at pwg.org] On Behalf Of
Richard_Landau at Dell.com
Sent: Thursday, April 19, 2007 13:42
To: wims at pwg.org
Subject: WIMS> CIM> There is one possible candidate for
EnabledLogicalElement



Console.  Not ConsoleLights or ConsoleDisplayBuffer, but a class with no
properties other than state so that it can be enabled and disabled.  In
the voting spreadsheet from eons ago, we all voted
prtGeneralConsoleDisable as priority A.  And there is a comment on it
that says, "must be implemented as CIM state accessible by
RequestStateChange() method."  Who would have guessed that we had such
foresight way back then.  

Proposal: When we get to it, we can use this as a pipe cleaner for CIM
modeling of this writable property.  I think it results in an otherwise
empty class derived directly from EnabledLogicalElement.  No new
properties, just the state properties and RequestStateChange() method
inherited from the parent.  

Comments?  

rick 

---------------------- 
Richard_Landau(at)dell(dot)com, Stds & System Mgt Architecture, CTO
Office 
+1-512-728-9023, One Dell Way, RR5-3, MS RR5-09, Round Rock, TX 78682 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.pwg.org/archives/wims/attachments/20070419/81a19918/attachment.html


More information about the Wims mailing list