WIMS> CIM> what to do to PrintOutputTray this week.

From: Richard_Landau@Dell.com
Date: Tue Mar 06 2007 - 20:02:42 EST

  • Next message: wamwagner@comcast.net: "WIMS> CIM>9 Mar Concall at 2PM EST"

    Ira,

    What to do with the PrintOutputTray MOF (and CR), per our discussions.

    (For context, I have attached the CR with four rounds of comments in
    it.)

     <<CIMCoreCR00901.005 aem_RBLreplies20070305.htm>>

    - Remove PrinterCreationClassName, PrinterName, CreationClassName
    properties.

    - Remove KEY qualifier from Id property.

    - Add KEY InstanceId property. Steal from SettingData.

    - Add the four new status properties from Core CR874. At least for the
    time being. I talked to Jon Hass, and 99% convinced him to up-level
    those status properties to ManagedSystemElement (from their current
    destination of EnabledLogicalElement). If/when the properties get moved
    to MSE, then we can change the inheritance of this class to MSE and get
    the new status properties the right way. He says that he'll do a CR for
    it right away; we'll see. And then later on later on the old properties
    will be deprecated. We will have more wonderful status properties than
    you can shake a stick at. Mercifully, they get instantiated only if
    someone asks for them, and then only if the provider cares to include
    them, too.

    - Add ElementName OVERRIDE WRITE with a description cribbed from
    AdminName and lengthened just a touch to indicate that it is the
    administratively assigned name to be supplied entirely by the user.

    - Leave MaxCapacity and RemainingCapacity as they are. I'll tough it
    out. There was some more discussion on today's call about the
    reluctance of small-footprint implementations to embrace the additional
    complexity of a Capabilites class, a SettingData class, and the two
    associations required for each base class with settings. Printers were
    not mentioned by name, but Aaron related that he and I had spoken about
    this topic, and that I was not the only one he knew opposed to the extra
    baggage.

    - Fix the loose "may not" (implying permission, in the old style) to
    "shall not" in MaxCapacity and similar places.

    - Leave CapacityUnit as is, same enums and all. We'll pick up PUNIT or
    ISPUNIT elsewhere.

    rick
    ----------------------
    Richard_Landau(at)dell(dot)com, Stds & System Mgt Architecture, CTO
    Office
    +1-512-728-9023, One Dell Way, RR5-3, MS RR5-09, Round Rock, TX 78682





    This archive was generated by hypermail 2.1.4 : Tue Mar 06 2007 - 20:03:28 EST