We will have a CIM alignment conference call on this Thursday. Subjects are acceptance of the last call's minutes, progress report on the phase 1 CR and recent communications on Phase 2 approach.
Bill Wagner Chairman WIMS WG/PWG
-------------- Original message --------------
From: "McDonald, Ira" <imcdonald at sharplabs.com>
> Hi Rick,
>> [copied WIMS mailing list, to get comments from other people]
>> Your list of dispositions for dubious/ambiguous/misplaced properties
> in CIM_Printer class for Phase 2 looks fine to me.
>> Note that in the latest version of my CIM Refresh document, I did
> specifically change the Description clauses for Horizontal/Vertical
> to clarify their relationship to the (already aligned) Printer MIB
> and IPP attributes.
>> Since I haven't started on the Phase 1 changes for other classes,
> I'm not sure what we may find there for Phase 2.
>> I plan to start on Phase 1 for CIM_PrintService this week.
>> I'm also trying to get a working WSDL/1.1 for WIMS together, so I
> may be a little slow with the CIM work.
> - Ira
>>> Ira McDonald (Musician / Software Architect)
> Blue Roof Music / High North Inc
> PO Box 221 Grand Marais, MI 49839
> phone: +1-906-494-2434
> email: imcdonald at sharplabs.com>> -----Original Message-----
> From: Richard_Landau at Dell.com [mailto:Richard_Landau at Dell.com]
> Sent: Monday, March 06, 2006 11:06 AM
> To: imcdonald at sharplabs.com> Subject: FW: Work items for phase 2.
>>> Ira, just in case you didn't have enough to do to stave off
> boredom :-) , here's a fun distraction.
>> I propose the following approximate list of things to do in the
> PWG-CIM alignment phase 2. Please complete the list with any items
> that you notice are missing. And suggest how we shall divvy these up.
>> PWG-CIM alignment, phase 2
>> 1. Deprecate properties that cannot be implemented interoperably.
>>> 2. Move (deprecate and add) some properties from CIM_Printer to
>>> 3. Improved explanations for other ambiguous properties, whatever
> ones we didn't get in phase 1.
>> For instance, longer explanations in CIM_Printer.HorizontalResolution
> and Vertical Resolution about how these should be derived from SNMP
> correspondence or from common sense in the case of non-SNMP printers.
> (Do we want to fix the non-metric units for these properties?)
> (These are really DefaultXxxx but badly named.)
>> Include semantic descriptions of
> - their impact on the operation of the printer;
> - how their values are changed;
> - when a changed value takes effect.
> Richard_Landau(at)dell(dot)com, System Mgt Arch & Stds
> One Dell Way,
> RR5-3 MS 8509,
> Round Rock, TX 78682
-------------- next part --------------
An HTML attachment was scrubbed...