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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.pwg.org/archives/wims/attachments/20060522/e1d3e3e7/attachment.html