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 [sysdevCR006655] |
CIMCoreCR00nnn |
|
CR Owner Name, Email [My Name, my.name@company.com] |
Richard Landau, Richard_Landau@dell.com |
|
Alliance Partner submitting CR request (if applicable) |
Printer Working Group pwg.org |
|
Alliance Partner vote history (e.g. SNIA XYZ Approved on 8/12/06) |
|
|
Alliance Partner identifier/tracking number (if available) |
n/a |
|
Errata [Yes/No] |
No |
|
Short Description |
Add new class CIM_PrinterElement to enhanced printer device model. |
|
Spec, Document or Model(s) Being Changed [Device Model] |
[Core Model] |
|
Spec, Document or Model Version Incorporating the Change [V2.9 Final] |
V2.16 Experimental |
|
Filename(s) Incorporating the Change [Device_USB.mof] |
CIM_PrinterElement.mof |
|
Date Originated [mm/dd/yyyy] |
06/27/2007 |
|
Date of Last Revision of the Change Request [mm/dd/yyyy] |
06/27/2007 |
|
Dependencies [smwgCR00567,sysdevCR00555] |
|
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):
As part of the PWG/DMTF Work Register, PWG is updating the printing-related classes in the CIM data model.
The PWG models for printing related devices and services include many properties that need to be managed but are not currently represented in CIM at all. The CIM model will be extended to include these important management objects. This will require extensions to the CIM_Printer class and the addition of other CIM classes to represent the capabilities, settings, and counters required.
Many early implementers of this class are expected to be proxy providers for SNMP-capable printers. A few properties in this class are included to permit software and users to correlate status and event information between CIM and legacy SNMP access paths. It is expected that such properties will be deprecated when they are no longer needed for this purpose.
The current new class, CIM_PrinterElement, is an abstract class from which all the major component classes of a printer will be derived, e.g., trays, markers, supplies, interpreters, channels, etc. Key data, and a legacy property required for correlation between external views of the various printer components, will be added at this level in the hierarchy.
Alliance Partner Status (tracking number, other key identifiers, supporting documentation, etc.):
(insert text here)
Requested Change (Change information such as details before/after the change, readable/indented MOF, and/or references to "Uploaded" MOF and other documents if the changes are too lengthy to include inline):
//add the new CIM_PrinterElement class
// Copyright (c) 2007 DMTF. All rights reserved.
// ==================================================================
// CIM_PrinterElement
// ==================================================================
[Experimental, Abstract, Version ( "2.16.0" ),
UMLPackagePath ( "CIM::Device::Printing" ), Description (
"This class extends LogicalElement to abstract the concept of a "
"PrinterElement that is a component (e.g., PrintMarker) of a "
"scoping Printer (print device). This class defines common "
"properties for key (InstanceID) and for correlation of status "
"and event (alert) information between CIM and SNMP management "
"interfaces (SNMPRowId). Note: A PrinterElement shall be "
"associated with exactly one Printer via an instance of the "
"PrinterComponent class. See: Model in section 2 of Printer MIB "
"(RFC 3805) and section 3 of Finisher MIB (RFC 3806).")]
class CIM_PrinterElement : CIM_LogicalElement {
[Key, Description (
"Within the scope of the instantiating Namespace, InstanceID "
"opaquely and uniquely identifies an instance of this class. "
"To ensure uniqueness within the NameSpace, the value of "
"InstanceID should be constructed using the following "
"\"preferred\" algorithm: \n"
"<OrgID>:<LocalID> \n"
"Where <OrgID> and <LocalID> are separated by a colon (:), "
"and where <OrgID> shall include a copyrighted, trademarked, "
"or otherwise unique name that is owned by the business "
"entity that is creating or defining the InstanceID or that "
"is a registered ID assigned to the business entity by a "
"recognized global authority. (This requirement is similar "
"to the <Schema Name>_<Class Name> structure of Schema class "
"names.) In addition, to ensure uniqueness, <OrgID> shall "
"not contain a colon (:). When using this algorithm, the "
"first colon to appear in InstanceID shall appear between "
"<OrgID> and <LocalID>. \n"
"<LocalID> is chosen by the business entity and should not "
"be reused to identify different underlying (real-world) "
"elements. If the above \"preferred\" algorithm is not used, "
"the defining entity shall assure that the resulting "
"InstanceID is not reused across any InstanceIDs produced by "
"this or other providers for the NameSpace of this instance. "
"\nFor DMTF-defined instances, the \"preferred\" algorithm "
"entity that is creating or defining the InstanceID or that "
"is a registered ID assigned to the business entity by a "
"recognized global authority. (This requirement is similar "
"to the <Schema Name>_<Class Name> structure of Schema class "
"names.) In addition, to ensure uniqueness, <OrgID> shall "
"not contain a colon (:). When using this algorithm, the "
"first colon to appear in InstanceID shall appear between "
"<OrgID> and <LocalID>. \n"
"<LocalID> is chosen by the business entity and should not "
"be reused to identify different underlying (real-world) "
"elements. If the above \"preferred\" algorithm is not used, "
"the defining entity shall assure that the resulting "
"InstanceID is not reused across any InstanceIDs produced by "
"this or other providers for the NameSpace of this instance. "
"\nFor DMTF-defined instances, the \"preferred\" algorithm "
"shall be used with the <OrgID> set to CIM.")]
string InstanceID;
[Description (
"A unique value used by a scoping Printer to identify this "
"component (e.g., PrintMarker) of the scoping Printer. "
"Although these values may change due to a reconfiguration "
"of the Printer (e.g., the addition of new components to the "
"Printer), values should remain stable across successive "
"Printer power cycles. Note: This property is necessary to "
"correlate status and event (alert) information between CIM "
"and SNMP interfaces."),
MinValue ( 1 ), MaxValue ( 65535 ),
MappingStrings { "MIB.IETF|Printer-MIB.prtCoverIndex",
"MIB.IETF|Printer-MIB.prtInputIndex",
"MIB.IETF|Printer-MIB.prtOutputIndex",
"MIB.IETF|Printer-MIB.prtMarkerIndex",
"MIB.IETF|Printer-MIB.prtMarkerSuppliesIndex",
"MIB.IETF|Printer-MIB.prtMediaPathIndex",
"MIB.IETF|Printer-MIB.prtChannelIndex",
"MIB.IETF|Printer-MIB.prtInterpreterIndex",
"MIB.IETF|Printer-MIB.prtConsoleLightIndex",
"MIB.IETF|Finisher-MIB.finDeviceIndex",
"MIB.IETF|Finisher-MIB.finSupplyIndex" }]
uint32 SNMPRowId;
};
Discussion Points (Summary of decisions and discussions of the WG in creating this CR) :
(insert text here)
Change History (Mandatory after submission to the TC, May be used by the WGs):
|
Version |
Date |
Short description of changes |
|
v00 |
2007/06/27 |
Original version. |
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 Sample Version 2.0.0.d