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.7232.60">
<TITLE>CIM> A few notes from today's concall with CIM Core WG</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->
<P><FONT SIZE=2 FACE="Arial">The concall today went reasonably well, and we got much more than our allotted fifteen minutes of fame. Still didn't quite get thru it all, but close. </FONT></P>
<P><FONT SIZE=2 FACE="Arial">Comments that I heard and noted during the discussion.</FONT>
</P>
<P><FONT SIZE=2 FACE="Arial">- Adding properties to PrintService, no problem. Deprecating properties is harder. We may get pushback from some people who have already implemented them, like parts of IBM or HP. </FONT></P>
<P><FONT SIZE=2 FACE="Arial">- Need to find out what the history of the changes was. It's their impression that all the changes were made on behalf of PWG by some champion in Core. John Crandall will get hold of Steve Jerman.</FONT></P>
<P><FONT SIZE=2 FACE="Arial">- For some items such as consoles, covers, channels, maybe counters, it will likely be better to write a profile that describes how to use existing classes to model these items. Need to check on the availability of suitable existing classes. </FONT></P>
<P><FONT SIZE=2 FACE="Arial">- Language interpreter might be modeled with SoftwareIdentity; not entirely clear. </FONT>
</P>
<P><FONT SIZE=2 FACE="Arial">- For some items, we can probably use the Capabilities and Settings classes and mechanism already in CIM. [Might be reasonable for paper sizes, media paths, trays.]</FONT></P>
<P><FONT SIZE=2 FACE="Arial">- We should take a look at the Profile User's Guide for guidance. [I'll try to find it.]</FONT>
</P>
<P><FONT SIZE=2 FACE="Arial">Overall, the topic ended very abruptly and I felt left hanging. We need a working contact or two within Core who can do the education back and forth about CIM and Printers. We need to look at doing the editorial changes as "low hanging fruit first." We need to discuss process. They did not seem to disagree with the scope, but the next steps were not clear to me. Harry, Ira, et al., do you understand better how to proceed? </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_Landa</FONT><FONT SIZE=2 FACE="Arial">u(at)</FONT><FONT SIZE=2 FACE="Arial">dell</FONT><FONT SIZE=2 FACE="Arial">(dot)</FONT><FONT SIZE=2 FACE="Arial">com,</FONT> <FONT SIZE=2 FACE="Arial">System Mgt Arch & Stds</FONT>
<BR><FONT SIZE=2 FACE="Arial">+1-512-728-9023,</FONT> <FONT SIZE=2 FACE="Arial">One Dell Way,</FONT> <FONT SIZE=2 FACE="Arial">RR5-3 Box 8352, Round Rock, TX 78682</FONT>
</P>
<BR>
</BODY>
</HTML>