All changes to be submitted by the Working Group Chair (or designee) after approval by the working group.
The Change Request
sample (http://www.dmtf.org/members/zdata/CRTemplateSample.html)
contains more detailed
information on how to complete the template.
DMTF Change Request Number [CIMCoreCR006655] |
|
CR Owner Name, Email |
|
Alliance
Partner submitting CR request (if applicable) |
|
Alliance
Partner vote history (e.g. SNIA XYZ Approved on 8/12/06) |
|
Alliance
Partner identifier/tracking number (if available) |
|
Errata [Yes|No] |
|
Short Description |
|
Spec, Document or Model(s) Being Changed |
|
Spec, Document or Model Version Incorporating the Change [2.16.0 Experimental | Final] |
|
Filename(s) Incorporating the Change |
|
Date Originated [mm/dd/yyyy] |
|
Date of Last Revision of the Change Request [mm/dd/yyyy] |
|
Dependencies [CIMCoreCR00555,CIMCoreCR00600,...] |
Terminology
The terminology used in this CR should conform to the "Rules for the structure and drafting of International Standards", 5th Edition, 2005 available at:
Particular attention shall be paid to Annex H which lays out guidelines for the expression of provisions.
Background/Rationale (Explanation of the
background and reason(s) for the requested change, and supporting
documentation):
Alliance
Partner Status (tracking number, other key identifiers,
supporting documentation, etc.):
n/a
Requested
Change (Change information such as details before/after the change
and/or references documents (other then MOF) if the changes are too
lengthy to include inline):
//add the class CIM_PrintSupply
MOF
Changes (The complete CIM Class (ASCII) using blue text for new, red
text for removed and black text for no change, only one CIM Class can
be changed per CR): |
|
Discussion Points (Summary of decisions and discussions of the WG in creating this CR) :
Comments on v02 2007/06/08:
Company |
Person |
Issue and Response |
Brocade |
John Crandall |
ColorantName has min and max len when it is a numeric. [PWG] Done. A leftover from previous string version. |
Brocade |
John Crandall |
SNMPRowID needs some other naming convention. This definition does not allow for other instrumentation abstractions although I knwo today it is primarily SNMP. How about PrintSupplyID? [PWG] This was the naming convention previously worked out with the Core chairs. It is specifically for the use of proxy agents and clients that need to correlate instances between SNMP views and CIM views of the same data, such as the SNMP Printer MIB Alerts table. Native CIM implementations will not express this property because clients will be able to use the associations internal to the CIM repository. This property is factored out of all the printer component classes in the latest model, and included in the PrinterElement class from which all the component classes are derived. |
Company |
Person |
Issue and Response |
Symantec |
Steve Hand |
It is not clear to me how this
class represents the supplies for the print finisher. For example,
ought there be a property that contains the remaining staples? Can you add the appropriate finisher values for PrintSupply (e.g. staples)? [PWG] The property CIM_PrintSupply.Level is designed to answer the question, How much of the supply remains, regardless of the type of supply. The combination of SupplyUnit, MaxCapacity, and Level (and their related OtherXxx and XxxBasis properties) should supply the information needed by an application. I think the necessary values are already present. - The enum list for PrintSupply.Type already includes the value Staples. - For Type=Staples, the normally appropriate SupplyUnit is Items, though a manufacturer might always choose to use Percent. Is there still something else that needs to be added to these lists? |
Change History (Mandatory after submission to the TC, May be used by the WGs):
Version |
Date |
Short description of changes |
00 |
2007/05/31 |
Original version. |
01 |
2007/05/31 |
Correct descriptions of ColorantName and OtherColorantName. |
02 |
2007/06/01 |
Correct ColorantName again. |
04 |
2007/0626 |
Change parent class to PrinterElement; remove inherited properties; add CR dependency. Clean up element terminology. Add references to PrintFinisher for completeness. |
05 |
2007/06/28 |
Update CR dependency and schema version number. |
06 |
2007/06/29 |
Add issue comments and responses. |
07 |
2007/07/12 |
Change schema version number
in MOF |
08 |
2007/08/05 |
New template. |
09 |
2007/08/10 |
Fix color tags. |
10 |
2007/08/20 |
Change Model from Core to Device. |
11 |
2007/08/23 |
Respond to comments from
TC. |
Note that this
document is labeled as "DMTF Confidential". It is intended only
for DMTF member companies and alliance partners.
This Change Request may be withdrawn or modified by subsequent Change
Requests.
All submissions MUST comply with the DMTF Patent and Technology policy (http://www.dmtf.org/about/policies/patent-10-18-01.pdf)
Template Version
2.0.1b
Copyright (C) 2007 Distributed Management Task Force,
Inc. (DMTF). All rights reserved.