> 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.)
>> Easy changes first: good idea. One, maybe two, CRs; maybe enums are
> separate, since they're sizable and substantive.
>> Don't bother with white papers. Draft directly into CR format, then
> edit as needed.
>> 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.
>> Do UML diagrams first for the new class structure, and get agreement
> on the structure before writing a lot of text.
>> Core needs some overview of the printing model. (Printer MIB has a
> good intro. Where is the similar overview for IPP?)
>> Use Capabilities and Settings classes (CIM_xxxx) to express such for
> printers. The usual division is
> - What is the device capable of? (r/o in Capabilities)
> - What has the manager requested of the device? (r/w in Settings)
> - What is the device actually doing? (properties in the device class
> (These classes are not completely straightforward, as I recall. I
> will look for some examples.)
>> 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.)
>> For the major changes, be sure to include some consideration of
> - related element causing error
> - health and status
> - messages
> - indications (event notifications in CIM, related to traps, alerts,
> alarms, etc.)
>> Send draft things, if we wish, to John Crandall and Jon_Hass at dell.com,
> or to wg_cimcore at dmtf.org>> Gotta go.
> Richard_Landau(at)dell(dot)com, System Mgt Arch & Stds
> +1-512-728-9023, One Dell Way, RR5-3 Box 8509, Round Rock, TX 78682
>-------------- next part --------------
An HTML attachment was scrubbed...