attachment

<html><body> <DIV>Rick,</DIV> <DIV> </DIV> <DIV>Thanks for your observations. I agree generally with your summary of the CIM core opinions. However, I suggest:</DIV> <DIV> </DIV> <DIV>1. The white paper was part of the PWG process, not necessarily something to be submitted to CIM core. The white paper was to be used both to allow a third person (Craig) to generate the CRs and to publicize to the PWG members what was being done in the name of the organization. I think it is an important part of our activities.</DIV> <DIV> </DIV> <DIV>2. However, the white papers should contain the overview information CIM requested. Indeed, one of the callers suggested that a white paper may help them understand  the background. So we may want to make the white paper available to CIM.</DIV> <DIV> </DIV> <DIV>3. We  need to consider the Capabilities and Settings issue. I have the notion that this structure is distinctly different from the model that we are trying to propagate. I wonder how the fact that settings can be changed by the print jobs as well as by management setting operations would be accomodated by this approach. That is, your have capabities, defaults and actuals.</DIV> <DIV> </DIV> <DIV>4. As was dicussed, the profile is a posibility for the future but is not currently part of the PWG/CIM realignment plan. If you that that the profile should be done as part of this this activity, please indicate your rational. It has been stated that the profile is complicated and of limited use, being primarily for WEBM which we believe will be replaced by WSDM.</DIV> <DIV> </DIV> <DIV>Thanks,</DIV> <DIV> </DIV> <DIV>Bill Wagner</DIV> <DIV> </DIV> <DIV> </DIV> <DIV> </DIV> <BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">-------------- Original message -------------- <BR>From: <Richard_Landau@Dell.com> <BR> <META content="MS Exchange Server version 6.5.7232.60" name=Generator> <P><FONT face=Arial size=2>Short notes on a few things I heard in the CIM Core concall today.  (I didn't have much opportunity to take notes for the first half hour, but here are some things I remember.)</FONT></P> <P><FONT face=Arial size=2>Easy changes first: good idea.  One, maybe two, CRs; maybe enums are separate, since they're sizable and substantive.  </FONT></P> <P><FONT face=Arial size=2>Don't bother with white papers.  Draft directly into CR format, then edit as needed.  </FONT></P> <P><FONT face=Arial size=2>Don't bother with PWG private extensions.  Propose phase 3 changes as experimental.  Then the implementation experience of two companies will be needed to promote the changes to full status.  </FONT></P> <P><FONT face=Arial size=2>Do UML diagrams first for the new class structure, and get agreement on the structure before writing a lot of text.  </FONT></P> <P><FONT face=Arial size=2>Core needs some overview of the printing model.  (Printer MIB has a good intro.  Where is the  similar overview for IPP?)</FONT></P> <P><FONT face=Arial size=2>Use Capabilities and Settings classes (CIM_xxxx) to express such for printers.  The usual division is </FONT><BR><FONT face=Arial size=2>- What is the device capable of? (r/o in Capabilities)</FONT> <BR><FONT face=Arial size=2>- What has the manager requested of the device? (r/w in Settings)</FONT> <BR><FONT face=Arial size=2>- What is the device actually doing? (properties in the device class itself)</FONT> <BR><FONT face=Arial size=2>(These classes are not completely straightforward, as I recall.  I will look for some examples.)</FONT> </P> <P><FONT face=Arial size=2>Think about doing a profile in the long term.  (A really good idea.  I will explain this and get an example for PWG to look at.  I think we should draft the profile along with the UML.)</FONT></P> <P><FONT face=Arial size=2>For the major changes, be sure to include some consideration of </FONT><BR><FONT face=Arial size=2>- related element causing error</FONT> <BR><FONT face=Arial size=2>- health and status</FONT> <BR><FONT face=Arial size=2>- messages</FONT> <BR><FONT face=Arial size=2>- indications (event notifications in CIM, related to traps, alerts, alarms, etc.)</FONT> </P> <P><FONT face=Arial size=2>Send draft things, if we wish, to John Crandall and Jon_Hass@dell.com, or to wg_cimcore@dmtf.org</FONT> </P> <P><FONT face=Arial size=2>Gotta go.  </FONT></P> <P><FONT face=Arial size=2>rick</FONT> <BR><FONT face=Arial size=2>-------------------------</FONT> <BR><FONT face=Arial size=2>Richard_Landa</FONT><FONT face=Arial size=2>u(at)</FONT><FONT face=Arial size=2>dell</FONT><FONT face=Arial size=2>(dot)</FONT><FONT face=Arial size=2>com,</FONT> <FONT face=Arial size=2>System Mgt Arch & Stds</FONT> <BR><FONT face=Arial size=2>+1-512-728-9023,</FONT> <FONT face=Arial size=2>One Dell Way,</FONT> <FONT face=Arial size=2>RR5-3 Box 8</FONT><FONT face=Arial size=2>509</FONT><FONT face=Arial size=2>, Round Rock, TX 78682</FONT> </P></BLOCKQUOTE></body></html>