attachment

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD><TITLE>CIM> There is one possible candidate for EnabledLogicalElement</TITLE> <META http-equiv=Content-Type content="text/html; charset=us-ascii"> <META content="MSHTML 6.00.2900.3059" name=GENERATOR></HEAD> <BODY> <DIV dir=ltr align=left>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.  </DIV> <DIV dir=ltr align=left> </DIV> <DIV dir=ltr align=left>rick</DIV> <DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left> <HR tabIndex=-1> From: owner-wims@pwg.org [mailto:owner-wims@pwg.org] On Behalf Of Richard_Landau@Dell.com Sent: Thursday, April 19, 2007 13:42 To: wims@pwg.org Subject: WIMS> CIM> There is one possible candidate for EnabledLogicalElement </DIV> <DIV></DIV> 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 </BODY></HTML>