[ Thinking about the Power MIB in relation to the
Printer MIB (especially prtAlertTable and trap) ]
I propose that Power Log occurs only on System
DMTF CIM (and Printer MIB and other IETF MIBs)
instantiates logs only on whole Systems or Devices
(but not on minor components like Subunits).
DMTF CIM won't *let* us put a log on a minor
component, so the current Power Model has a
serious mapping issue.
I propose that the revised Power Log group
should have the same single key (LogID) and
two new elements named:
- existing powMonitorComponentType in MIB
- add new powMonitorComponentIndex in MIB
which, in turn, correspond to prtAlertGroup and
prtAlertGroupIndex in Printer MIB.
Both ComponentType and ComponentID are
implicit in the XML Schema - first is the enclosing
object type and second is either '1' for System or
<subunit>ID (like InputTrayID / prtInputIndex).
Ira McDonald (Musician / Software Architect)
Chair - Linux Foundation Open Printing WG
Blue Roof Music/High North Inc
email: blueroofmusic at gmail.com
579 Park Place Saline, MI 48176
PO Box 221 Grand Marais, MI 49839
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.