Domesday Book for work on WIMS CIM new Printer model
                                        Rick Landau

What have we noticed along the way that need to be done and should not be forgotten?  This should be a complete inventory of reminders of changes and fixes necessary to complete the PWG update to the CIM Printer model.  It is just a collection of yellow stickies that should not get lost.  It is not an organized list or plan to accomplish a goal.  Just an entry date and a quick reminder of something to be done.  


20070627
OutputTray: Change parent class to PrinterElement.

20070627
InputTray: Change parent class to PrinterElement.

20070627
InputTray: Fix the description of XxxBasis that incorrectly states
shall be null instead of shall be present, or vice versa, I forget.  

20070629
PrintMarker: Does Type need Vendor Reserved range, or is that covered adequately by Other and OtherTypeDescription?  

20070810
PrintInputTray: Some property is "unit32" instead of "uint32" as needed.  Fix.  How on earth did this pass into the actual build?  Maybe it didn't. 

20070810
PrintOutputTray and PrintInputTray: May need to fix 0=Unknown and 1=Other in all enum lists according to new stealth Core convention.  

20070822
PrintMarker: Maybe add FeedAddressability and XFeedAddressability and their XxxBasis properties.  

Printer: If we add FeedAddressability to PrintMarker, then augment the Deprecated clause on VerticalResolution and HorizontalResolution to point also to PrintMarker as well as PrintInterpreter.  

PrinterComponent: Add cardinality MIN(1) to subunit side of this association.  Then use this association only for the mandatory subunits of the Printer device.  

OutputTray and InputTray: add the property IsDefault.  We moved this from the CIM_Printer class to the subclasses.  

Printer: add properties from the PortMon MIB.

All those writable properties we dropped: decide if we need a method to update the property or can we just permit direct writing.  If changing the value does not have complex side effects with possibly multiple fault modes, then direct writing should be acceptable.  

Printer and PrintService: Do we need to add operations on device and service state such as purge jobs?

20070913
Printer: in its description, name all the related component classes and the associations to be used to connect them, i.e., PrinterComponent for the mandatory subunits and ConcreteComponent for the optional ones.  

Write a pre-profile for Printer and its components: a small white-paper-ish doc that describes all the component classes and all the associations, the structure required, required properties, and even required alert indications corresponding to alerts.  Don't sweat the DMTF formal Profile format, but cover the meat.