RE: WIMS> CIM - Order of next printing updates

From: Richard_Landau@Dell.com
Date: Mon Oct 29 2007 - 14:53:18 EDT

  • Next message: Whittle, Craig: "WIMS> CIM - Minutes from the October 25, 2007 teleconference posted"

    Nice idea, but...

    1. I would *really* hate to wait to get the new properties into
    Printer. I think we ought to leap on those with both feet. Deprecation
    is slightly less important.

    2. The time between public CIM versions is three months, not four to
    six. If we miss version N, then version N+1 is published three months
    later. We think that it is longer because of the delta between
    CR-approved and next schema version published dates.

    Let me ask Crandall if we can possibly fudge the deprecation for the
    properties that we want to move from Printer to PrintService. If we are
    going to keep the same property name and semantics, maybe it is not
    crazy to say "This property will be moved...."

    rick

    -----Original Message-----
    From: owner-wims@pwg.org [mailto:owner-wims@pwg.org] On Behalf Of Ira
    McDonald
    Sent: Sunday, October 28, 2007 13:52
    To: William A Wagner; Ira McDonald
    Cc: wims@pwg.org
    Subject: Re: WIMS> CIM - Order of next printing updates

    Hi Bill,

    Basically that's what I'm saying.

    But actually PrintService wouldn't be delayed at all. It just wasn't
    going to get updated in the next cycle with the wrapup of Printer and
    subunits.
    The main update of PrintService is too large to do now.

    Until we finish Printer and the subunits, we don't have a "package" of
    Print Device classes to recommend people implement. And remember we
    need two independent implementations to go from CIM Experimental (no
    stability guarantees) to CIM Final.

    Cheers,
    - Ira

    On 10/27/07, William A Wagner <wamwagner@comcast.net> wrote:
    > Ira,
    >
    > If I understand, you are suggesting to first do a CR to Print Service
    > adding those elements that are intended to be relocated from Printer,
    > then doing a through CR for Printer. I guess the question might be,
    > could a minimal CR to Print Service pass though quickly?
    > The effect would appear to be to allow a speedier completion of
    > Printer at the possible cost of delaying completion of Print Service
    > (probably a good tradeoff).
    >
    > Thanks,
    >
    > Bill Wagner
    >
    >
    >
    > -----Original Message-----
    > From: owner-wims@pwg.org [mailto:owner-wims@pwg.org] On Behalf Of Ira
    > McDonald
    > Sent: Saturday, October 27, 2007 6:32 PM
    > To: wims@pwg.org; Ira McDonald
    > Subject: WIMS> CIM - Order of next printing updates
    >
    > Hi,
    >
    > We have four or five small edits to do in the various Printer subunit
    > classes (after CIM v2.17 is published, when we can do 2.18 revisions).
    >
    > But we also have three kinds of substantive edits to do in Printer:
    > (1) Add Printer MIB v1 and v2 missing properties (a handful)
    > (2) Deprecate properties now represented better in subunit classes.
    > (3) Deprecate properties to be "moved" (i.e., copied) to PrintService.
    >
    > In phone discussions, Rick has suggested to me that we'll "have to
    > revise CIM_Printer several times" (because you can't do item (3) above

    > until AFTER service properties have already been copied to
    > PrintService, because a deprecated property MUST refer to the
    replacement one).
    >
    > But there is a very serious impedance filter in CIM updates - only ONE

    > CR against a given class can be processed in a CIM update cycle (four
    months).
    > And a new CR can't be written for a class until the previous CIM
    > version is actually *published* (several more months).
    >
    > So, I suggest that we get a little smarter and do a small update FIRST

    > to PrintService, and then submit all three items in Printer and be
    > DONE with Printer.
    >
    > The calendar difference would be four to six months sooner.
    >
    > Comments?
    >
    > Cheers,
    > - Ira
    >
    > --
    > Ira McDonald (Musician / Software Architect) Chair - Linux Foundation
    > Open Printing WG Blue Roof Music / High North Inc PO Box 221 Grand
    > Marais, MI 49839
    > work: +1-906-494-2434
    > home: +1-906-494-2697
    > email: blueroofmusic@gmail.com
    >
    >

    --
    Ira McDonald (Musician / Software Architect) Chair - Linux Foundation
    Open Printing WG Blue Roof Music / High North Inc PO Box 221  Grand
    Marais, MI  49839
    work: +1-906-494-2434
    home: +1-906-494-2697
    email: blueroofmusic@gmail.com
    


    This archive was generated by hypermail 2.1.4 : Mon Oct 29 2007 - 14:53:25 EDT