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

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

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

McDonald, Ira imcdonald at sharplabs.com
Mon Aug 8 18:46:21 EDT 2005

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.
- 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 at sharplabs.com 

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

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


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.  


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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.pwg.org/archives/wims/attachments/20050808/d32a5548/attachment-0001.html

More information about the Wims mailing list