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]	CIMCoreCR00947
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)	CIMCoreCR_AssociatedPrintSupply_06.htm
Errata [Yes\|No]	No
Short Description	Add new class CIM_AssociatedPrintSupply to enhanced printer device model.
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.17 Experimental
Filename(s) Incorporating the Change [Core/CIM_Container.mof, DSP0204.pdf]	CIM_AssociatedPrintSupply.mof
Date Originated [mm/dd/yyyy]	05/31/2007
Date of Last Revision of the Change Request [mm/dd/yyyy]	06/27/2007
Dependencies [CIMCoreCR00555,CIMCoreCR00600,...]	CIMCoreCR00958,CIMCoreCR00946

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 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_AssociatedPrintSupply, is the fifth of several classes to be added. This association class relates a PrintSupply with the PrintMarker that uses that supply.

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 new class CIM_AssociatedPrintSupply

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.
// ==================================================================
// CIM_AssociatedPrintSupply
// ==================================================================

   [Association, Experimental, Version ( "2.17.0" ),
       UMLPackagePath ( "CIM::Device::Printing" ), Description (
       "This class represents the association between a PrintSupply "
       "component of a Printer (print device) and a PrintMarker or "
       "PrintFinisher component of the same Printer. Note: A "
       "PrintSupply shall be associated with exactly one PrintMarker "
       "or PrintFinisher. See: Model in section 2 of Printer MIB (RFC "
       "3805) and section 3 of Finisher MIB (RFC 3806)."), 
    MappingStrings { 
       "MIB.IETF|Printer-MIB.prtMarkerSuppliesMarkerIndex",
       "MIB.IETF|Finisher-MIB.finSupplyDeviceIndex" }]
class CIM_AssociatedPrintSupply : CIM_Dependency {

      [Override ( "Antecedent" ), Description (
          "The PrintSupply (e.g., toner cartridge or staples) "
          "component of a Printer.")]
   CIM_PrintSupply REF Antecedent;

      [Override ( "Dependent" ), Min ( 1 ), Max ( 1 ), Description (
          "The PrintMarker or PrintFinisher component of the same "
          "Printer that needs or is associated with this PrintSupply.")]
   CIM_PrinterElement REF Dependent;
};

Discussion Points (Summary of decisions and discussions of the WG in creating this CR) :

Comments on v01 2007/06/08:

Company	Person	Issue and Response
Brocade	John Crandall	PrintSupply is not an existing class. Need top make CIMCOreCR00946 a dependency CR. [PWG] Done.
Brocade	John Crandall	Also what LogicalElement can be expected. Where I am going is that we may need a subclass of LogicalElement for SubUnit. This also would probably contain the SNMPRowID or a better name and keep from having all these classes subclass off of LogicalElement. [PWG] Done. A new abstract class CIM_PrinterElement will be added and used as the parent for all the component classes such as CIM_PrintSupply. That class is used in the REF of this class so that a PrintSupply can be associated with a PrintMarker or PrintFinisher, as required.
Brocade	John Crandall	Also I believe there is a cardinality here that could be specified. [PWG] Done.

<>

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

Version	Date	Short description of changes
01	2007/05/31	Original version.
02	2007/06/27	Add cardinality specs for Dependent. Improve Description.
03	2007/06/28	Update CR dependency and schema version number.
04	2007/06/29	Add comments and responses.
05	2007/07/12	Change schema version number in MOF.
06	2007/08/05	New template.
08	2007/08/20	Change Model from Core to Device.

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)