Web-based Imaging Management Services: RE: WIMS> CIM> Dep

RE: WIMS> CIM> Deprecating (almost) all CurrentXxxx properties in CIM_Printer

From: McDonald, Ira (imcdonald@sharplabs.com)
Date: Mon Aug 08 2005 - 23:25:51 EDT

  • Next message: Richard_Landau@Dell.com: "RE: WIMS> CIM> Deprecating (almost) all CurrentXxxx properties in CIM_Printer"

    Hi,
     
    By the way, the corresponding IPP Printer attributes are called
    'charset-configured' and 'natural-language-configured'. Given that
    IPP and the Printer MIB frequently refer to the 'current configuration',
    DMTF CIM property names of 'Current...' are fine if we deprecate
    all the other non-deterministic 'CurrentXxx' properties.
     
    Cheers,
    - Ira
     

    Ira McDonald (Musician / Software Architect)
    Blue Roof Music / High North Inc
    PO Box 221 Grand Marais, MI 49839
    phone: +1-906-494-2434
    email: imcdonald@sharplabs.com

    -----Original Message-----
    From: owner-wims@pwg.org [mailto:owner-wims@pwg.org]On Behalf Of McDonald,
    Ira
    Sent: Monday, August 08, 2005 6:46 PM
    To: 'wamwagner@comcast.net'; Richard_Landau@Dell.com; wims@pwg.org
    Cc: Winston_Bumpus@Dell.com
    Subject: RE: WIMS> CIM> Deprecating (almost) all CurrentXxxx properties in
    CIM_Printer

    Hi,
     
    I agree with the proposal.
     
    However, I strongly DISAGREE with the creation of new DefaultXxx
    properties to be used in place of CurrentCharSet/NaturalLanguage.
     
    We had this discussion during the development of IPP and concluded
    that DefaultXxx has the wrong semantics, because they CANNOT be
    overridden by the user. They are the character set and language
    for the values in the Printer Description class of attributes (broadly,
    everything except Status attributes). A specific user can request
    a Notification (for example) in a different charset/language, but the
    Printer current values don't change. This is NOT the semantics
    of DefaultXxx on a Printer object.
     
    Note that the user MUST specify the charset/language of submitted
    string attributes with an IPP Job - it's a protocol error to omit them.
     
    Cheers,
    - Ira
     

    Ira McDonald (Musician / Software Architect)
    Blue Roof Music / High North Inc
    PO Box 221 Grand Marais, MI 49839
    phone: +1-906-494-2434
    email: imcdonald@sharplabs.com

    -----Original Message-----
    From: owner-wims@pwg.org [mailto:owner-wims@pwg.org]On Behalf Of
    wamwagner@comcast.net
    Sent: Monday, August 08, 2005 3:43 PM
    To: Richard_Landau@Dell.com; wims@pwg.org
    Cc: Winston_Bumpus@Dell.com
    Subject: Re: WIMS> CIM> Deprecating (almost) all CurrentXxxx properties in
    CIM_Printer

    Rick,
     
    Makes sense. Perhaps we got carried away in our generalizations and missed
    the distinction.
     
    I would see no benefit in changing the names of urrentCharSet or
    CurrentNaturalLanguage
     
    Bill Wagner
     

    -------------- Original message --------------

    Re: Deprecating (almost) all CurrentXxxx properties in CIM_Printer

    Slight revision to the proposal: Deprecate all the CurrentXxxx properties
    in favor of the corresponding DefaultXxxx properties, except CurrentCharSet
    and CurrentNaturalLanguage.

    These last two properties, CharSet and NaturalLanguage, record the character
    set and natural language being used for management, not for printing. They
    are properties of the printer controller, not properties of print jobs.
    Since they are asynchronous with printing functions, they do not suffer from
    the ambiguities of the other CurrentXxxx properties in complex printers.
    Also, neither of these properties has a corresponding DefaultXxxx property.
    Therefore these two properties must be retained.

    Summary:

    CurrentPaperType deprecate; use DefaultPaperType instead
    CurrentLanguage deprecate; use DefaultLanguage
    CurrentMimeType deprecate; use DefaultMimeType
    CurrentCapabilities deprecate; use DefaultCapabilities

    CurrentCharSet retain
    CurrentNaturalLanguage retain

    I recall that some exceptions were mentioned, but I think we all mistakenly
    referred to CurrentLanguage instead of CurrentCharSet during the discussion.

    Addendum to proposal: we could change the *names* of the two remaining
    CurrentXxxx properties to DefaultCharSet and DefaultNaturalLanguage and then
    be rid of all the CurrentXxxx properties. (Actual process: add new
    properties with identical syntax and semantics but new names, and then
    deprecate the old properties.) Only half kidding.

    Comments, please.

    rick

    -------------------------
    Richard_Landau@dell.com, System Mgt Arch & Stds
    +1-512-728-9023, One Dell Way, RR5-3 Box 8352, Round Rock, TX 78682



    This archive was generated by hypermail 2b29 : Mon Aug 08 2005 - 23:24:04 EDT