DMTF Change Request

DMTF Confidential

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]	CIMCoreCR01090
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, www.pwg.org
Alliance Partner vote history (e.g. SNIA XYZ Approved on 8/12/06)	n/a
Alliance Partner identifier/tracking number (if available)	CIMCoreCR_PrinterElement_fix_00.html
Errata [Yes\|No]	No
Short Description	Modify class CIM_PrinterElement
Spec, Document or Model(s) Being Changed [Application\|Core\|Database\|Device\|Event\|Interop\| Network\|Physical\|Policy\|Support\|System\|User ]	Device
Spec, Document or Model Version Incorporating the Change [2.16.0 Experimental \| Final]	2.19 Experimental
Filename(s) Incorporating the Change [Core/CIM_Container.mof, DSP0204.pdf]	CIM_PrinterElement.mof
Date Originated [mm/dd/yyyy]	03/03/2008
Date of Last Revision of the Change Request [mm/dd/yyyy]	03/03/2008
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:

http://isotc.iso.org/livelink/livelink.exe/fetch/2000/2122/3146825/4229629/4230450/4230456/ISO_IEC_Directives__Part_2__Rules_for_the_structure_and_drafting_of_International_Standards__2004__5th_edition___pdf_format_.pdf?nodeid=4230517&vernum=0

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 is being extended to include these important management objects. This requires extensions to the CIM_Printer class and the addition of other CIM classes to represent the capabilities, settings, and counters required.

The current class, CIM_PrinterElement, is an abstract parent class from which all components of a printer derive.

Descriptions of the changes, both editorial and substantive, are listed below.

- The Description of the class includes rules for the assocations used to relate children of this class to the Printer device.

We (PWG) are reasonably certain that there are no current implementations of this experimental class yet (at least not within our membership), so we do not feel that the changes will be burdensome.

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 and/or references documents (other then MOF) if the changes are too lengthy to include inline):

// Modify the class CIM_PrinterElement

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):



// Copyright (c) 2007 DMTF.  All rights reserved.
// Copyright (c) 2008 DMTF.  All rights reserved.
   [Experimental, Abstract, Version ( "2.1719.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)." )]
       "interfaces (SNMPRowId). \n"
       "Note: A Printer shall be associated with at least one of every "
       "required component (e.g., PrintMarker) via an instance of the "
       "PrinterComponent class. "
       "A Printer may be associated with zero or more optional "
       "components (e.g., PrintSupply) via an instance of the "
       "ConcreteComponent 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. \n"
          "For 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. \n"
          "For 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) :

Change History (Mandatory after submission to the TC, May be used by the WGs):

Version	Date	Short description of changes
000	03/03/2008	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)