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]

CIMCoreCR00945

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_PrintMarker_07.htm

Errata   [Yes|No]

No

Short Description

Add new class CIM_PrintMarker to enhanced printer device model.

Spec, Document or Model(s) Being Changed
[Application|Core|Database|Device|Event|Interop|
Network|Physical|Policy|Support|System|User ]

Core

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_PrintMarker.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

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_PrintMarker, is one of several classes to be added.  A PrintMarker represents the portion of the printer that places marks on media.  It is possible for a printer to have more than one marker.  However, a typical color printer, for instance, is modeled with one marker and several supplies for its several colorants. 
 

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_PrintMarker


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_PrintMarker
// ==================================================================

[Experimental, Version ( "2.17.0" ),
UMLPackagePath ( "CIM::Device::Printing" ), Description (
"This class represents the PrintMarker component of a Printer "
"(print device). It contains properties that describe the "
"PrintMarker technology, capabilities, counters, and status. "
"Note: A PrintMarker shall be associated with exactly one "
"Printer via an instance of the PrinterComponent class. See: "
"Model in section 2 of Printer MIB (RFC 3805)."),
MappingStrings { "MIB.IETF|Printer-MIB.prtMarkerEntry" }]
class CIM_PrintMarker : CIM_PrinterElement {

[Description (
"Denotes whether or not this PrintMarker is the default "
"PrintMarker for this Printer. If the default PrintMarker "
"feature is not supported for this Printer, then this "
"property shall be null. If the default PrintMarker feature "
"is supported for this Printer, then this property shall be "
"true for at most one instance of CIM_PrintMarker on this "
"Printer, i.e., the default may not be currently configured."),
MappingStrings { "MIB.IETF|Printer-MIB.prtMarkerDefaultIndex" }]
boolean IsDefault;

[Description (
"The type of marking technology used for this PrintMarker."),
ValueMap { "1", "2", "3", "4", "5", "6", "7", "8", "9", "10",
"11", "12", "13", "14", "15", "16", "17", "18", "19", "20",
"21", "22", "23", "24", "25", "26", "27", ".." },
Values { "Other", "Unknown", "ElectrophotographicLED",
"ElectrophotographicLaser", "ElectrophotographicOther",
"ImpactMovingHeadDotMatrix9pin",
"ImpactMovingHeadDotMatrix24pin",
"ImpactMovingHeadDotMatrixOther",
"ImpactMovingHeadFullyFormed", "ImpactBand", "ImpactOther",
"InkjetAqueous", "InkjetSolid", "InkjetOther", "Pen",
"ThermalTransfer", "ThermalSensitive", "ThermalDiffusion",
"ThermalOther", "Electroerosion", "Electrostatic",
"PhotographicMicrofiche", "PhotographicImagesetter",
"PhotographicOther", "IonDeposition", "EBeam", "Typesetter",
"DMTF Reserved" },
MappingStrings { "MIB.IETF|Printer-MIB.prtMarkerMarkTech",
"MIB.IETF|IANA-PRINTER-MIB.PrtMarkerMarkTechTC" },
ModelCorrespondence { "CIM_PrintMarker.OtherMarkTechDescription"
}]
uint32 MarkTech;

[Description (
"A free-form string that describes the type of technology "
"when the value of the MarkTech property is equal to 1, 5, "
"11, 14, 19, or 24 (Other, ElectrophotographicOther, "
"ImpactMovingHeadDotMatrixOther, ImpactOther, InkjetOther, "
"ThermalOther, or PhotographicOther)."),
MinLen ( 0 ), MaxLen ( 255 ),
ModelCorrespondence { "CIM_PrintMarker.MarkTech" }]
string OtherMarkTechDescription;

[Description (
"The unit that will be used by the Printer when reporting "
"counter values for this PrintMarker. The time units of "
"measure are provided for a PrintMarker like a strip "
"recorder that does not or cannot track the physical "
"dimensions of the media and does not use characters, lines "
"or sheets."),
ValueMap { "1", "2", "3", "4", "5", "6", "7", "8", "9", "11",
"16", "17", ".." },
Values { "Other", "Unknown", "TenThousandthsOfInches",
"Micrometers", "Characters", "Lines", "Impressions",
"Sheets", "DotRow", "Hours", "Feet", "Meters",
"DMTF Reserved" },
MappingStrings { "MIB.IETF|Printer-MIB.prtMarkerCounterUnit",
"MIB.IETF|Printer-MIB.PrtMarkerCounterUnitTC" },
ModelCorrespondence { "CIM_PrintMarker.OtherCounterUnit",
"CIM_PrintMarker.LifeCount", "CIM_PrintMarker.PowerOnCount" }]
uint32 CounterUnit;

[Description (
"A free-form string that describes the counter unit when the "
"value of the CounterUnit property is equal to 1 (Other)."),
MinLen ( 0 ), MaxLen ( 255 ),
ModelCorrespondence { "CIM_PrintMarker.CounterUnit",
"CIM_PrintMarker.LifeCount", "CIM_PrintMarker.PowerOnCount" }]
string OtherCounterUnit;

[Description (
"The count of PrintMarker usage during the life of the "
"Printer using units of measure as specified by "
"CIM_PrintMarker.CounterUnit."),
MappingStrings { "MIB.IETF|Printer-MIB.prtMarkerLifeCount",
"MIB.IETF|Printer-MIB.PrtMarkerCounterUnitTC" },
ModelCorrespondence { "CIM_PrintMarker.CounterUnit",
"CIM_PrintMarker.OtherCounterUnit" }]
uint32 LifeCount;

[Description (
"The count of PrintMarker usage since the equipment was most "
"recently powered on using units of measure as specified by "
"CIM_PrintMarker.CounterUnit."),
MappingStrings { "MIB.IETF|Printer-MIB.prtMarkerPowerOnCount",
"MIB.IETF|Printer-MIB.PrtMarkerCounterUnitTC" },
ModelCorrespondence { "CIM_PrintMarker.CounterUnit",
"CIM_PrintMarker.OtherCounterUnit" }]
uint32 PowerOnCount;

[Description (
"The number of process colors supported by this PrintMarker. "
"A process color of 1 implies monochrome. The value of this "
"property and CIM_PrintMarker.SpotColorants cannot both be "
"0. The value of this property shall be 0 or greater."),
MinValue ( 0 ), MaxValue ( 65535 ),
MappingStrings {
"MIB.IETF|Printer-MIB.prtMarkerProcessColorants" },
ModelCorrespondence { "CIM_PrintSupply.ColorantRole" }]
uint32 ProcessColorants;

[Description (
"The number of spot colors supported by this PrintMarker. "
"The value of this property and "
"CIMPrintMarker.ProcessColorants cannot both be 0. The value "
"of this property shall be 0 or greater."),
MinValue ( 0 ), MaxValue ( 65535 ),
MappingStrings { "MIB.IETF|Printer-MIB.prtMarkerSpotColorants" },
ModelCorrespondence { "CIM_PrintSupply.ColorantRole" }]
uint32 SpotColorants;

[Description (
"This property contains detailed availability information "
"for this PrintMarker, as follows: 1 (Other) means other "
"detailed availability information is present in the "
"OtherAvailabilityStatus property. 2 (Unknown) means "
"detailed availability information for this PrintMarker is "
"unknown. 3 (AvailableIdle) means this PrintMarker is "
"available and idle, i.e., not currently in use. 4 "
"(AvailableStandy) means this PrintMarker is available but "
"on standby, e.g., in a power saving mode. 5 "
"(AvailableActive) means this PrintMarker is available and "
"active, i.e., currently in use. 6 (AvailableBusy) means "
"this PrintMarker is available but busy, i.e., not "
"immediately available for its primary function. 7 "
"(UnavailableOnRequest) means this PrintMarker is not "
"available and is on request, i.e., needs human "
"intervention. 8 (UnavailableBroken) means this PrintMarker "
"is not available and is broken, e.g., needs "
"repair/replacement."),
ValueMap { "1", "2", "3", "4", "5", "6", "7", "8", ".." },
Values { "Other", "Unknown", "AvailableIdle",
"AvailableStandby", "AvailableActive", "AvailableBusy",
"UnavailableOnRequest", "UnavailableBroken",
"DMTF Reserved" },
MappingStrings { "MIB.IETF|Printer-MIB.PrtSubUnitStatusTC" },
ModelCorrespondence {
"CIM_ManagedSystemElement.OperatingStatus",
"CIM_PrintMarker.OtherAvailabilityStatus" }]
uint32 AvailabilityStatus;

[Description (
"A free-form string that describes the detailed availability "
"of this PrintMarker when the value of the "
"AvailabilityStatus property is equal to 1 (Other)."),
MinLen ( 0 ), MaxLen ( 255 ),
ModelCorrespondence { "CIM_PrintMarker.AvailabilityStatus" }]
string OtherAvailabilityStatus;

[Description (
"If true, there are currently non-critical alerts on this "
"PrintMarker."),
MappingStrings { "MIB.IETF|Printer-MIB.PrtSubUnitStatusTC" },
ModelCorrespondence { "CIM_ManagedSystemElement.DetailedStatus"
}]
boolean NonCriticalAlertsPresent;

[Description (
"If true, there are currently critical alerts on this "
"PrintMarker."),
MappingStrings { "MIB.IETF|Printer-MIB.PrtSubUnitStatusTC" },
ModelCorrespondence { "CIM_ManagedSystemElement.DetailedStatus"
}]
boolean CriticalAlertsPresent;
};


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
Okay... I need a visio. I am struggling with the fact everything for printer is subclass off of LogicalElement. From what little I can see, it looks like there can be a printer specific subclass that has InstanceID and SNMPRowID, but maybe more. This will also help with the association going directly to LogicalElement in the other CR.

[PWG] Visio updated and published, including description of changes and reasons. 


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 version of MOF source included in CR.

 03

 2007/06/27

Derive from PrinterElement instead of directly from LogicalElement; and remove inherited properties; and add CR dependency.  
Improve Description.

 04

 2007/06/28

Update CR dependency and schema version number.

 05

 2007/06/29

Add issue comments and responses.  

 06

 2007/07/12

Change schema version number in MOF.  

07
2007/08/05
New template.


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.