attachment

I fully agree with Rick. ---------------------------------------------- Harry Lewis IBM STSM Chairman - IEEE-ISTO Printer Working Group http://www.pwg.org IBM Printing Systems http://www.ibm.com/printers 303-924-5337 ---------------------------------------------- <table width=100%> <tr valign=top> <td width=40%><Richard_Landau@Dell.com> Sent by: owner-wims@pwg.org 05/22/2006 10:01 AM <td width=59%> <table width=100%> <tr valign=top> <td> <div align=right>To</div> <td><wims@pwg.org> <tr valign=top> <td> <div align=right>cc</div> <td> <tr valign=top> <td> <div align=right>Subject</div> <td>WIMS> CIM> What CIM schema changes can be made in minor (non-breaking) updates?</table> <table> <tr valign=top> <td> <td></table> </table> In a CIM Core discussion about some proposed changes, I found the following blurb:    "Remember that a minor schema change may:      - Add properties      - Introduce new classes between existing classes      - Move existing properties up from an existing class" A "minor schema change" in this context is one that alters the minor version number but not the major version number.  The CIM Schema version number is structured as  major.minor.patch,  so that, for instance, moving from 2.12 to 2.13 is a minor change.  Minor changes must not break existing code, but otherwise may include the types of changes mentioned.   The changes we (PWG) are proposing are all minor.  *Extremely* minor in phase 1, very minor in phase 2, and still minor in phase 3 even if we perform some surgery on the class structure.  Let's not worry too much about this until someone says, "No."  Remember Grace Hopper's Law: It is easier to beg forgiveness than to get permission.   rick ---------------------- Richard_Landau(at)dell(dot)com, Stds & System Mgt Arch, CTO Office +1-512-728-9023, One Dell Way, RR5-3 MS 8509, Round Rock, TX 78682