attachment
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7651.59">
<TITLE>CIM> There is one possible candidate for EnabledLogicalElement</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->
<P><FONT SIZE=2 FACE="Arial">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. </FONT></P>
<P><FONT SIZE=2 FACE="Arial">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. </FONT></P>
<P><FONT SIZE=2 FACE="Arial">Comments? </FONT>
</P>
<P><FONT SIZE=2 FACE="Arial">rick</FONT>
</P>
<P><FONT SIZE=2 FACE="Arial">----------------------</FONT>
<BR><FONT SIZE=2 FACE="Arial">Richard_Landau(at)dell(dot)com, Stds & System Mgt Architecture, CTO Office</FONT>
<BR><FONT SIZE=2 FACE="Arial">+1-512-728-9023, One Dell Way, RR5-3, MS RR5-09, Round Rock, TX 78682</FONT>
</P>
</BODY>
</HTML>