Subject: Comments on IPP version 1.0 proposal

From: Dan Bell <[email-masked]>
Date: Mon, 23 Feb 1998 20:20:27 PST

Tremendous job!  Congratulations on a successful undertaking!

A few modest suggestions are listed below:

	Responder name(s):  Daniel Bell
	Responder organization:  Xerox Corp.
            Responder email adress(es):  [email-masked]
	Responder telephone number(s):  (716) 265-2408
	Responder role:  developer/architecture production printing systems

IPP Document:   Model&Semantics
	
Item:                1
Line:                1416, 1445-1479
Topic:             "requested-attributes" attribute of Get-Jobs operation 
	
Description:   It would be desirable to retrieve a list of Jobs objects that have specific attribute values (e.g., all jobs with media=USLetter).  This would reduce bandwidth requirements when filtering jobs.  Note:  The "which-jobs" and "my-jobs" attributes of the Get-Jobs operation essentially provide this filtering function with respect to two attributes - Job object "state" and Job object "requesting user". 	

Suggested change:  Allow the specification of a particular attribute(s) and the desired value(s).  Make this a generic function and eliminate the need for "which-jobs" and "my-jobs" attributes.
--------------------------------------------------
Item:          2
Line:          2216-2240
Topic:       standard values for named time periods of "job-hold-until" attribute	

Description:   This seems like a very arbitrary set of values.  (For example, in many places the third-shift begins at 11:00pm.  Additionally, there is no 'first-shift' value.)  The work model that this is trying to address is not apparent.  The benefit of these specific enumerated values does not seem clear.	

Suggested change:   Make this a dateTime value instead of an enum, and rely on the UI/application to translate between site-defined times and the dateTime value.

----------------------------

Item:       3
Line:       2455
Topic:     Definition of resolution attribute
	
Description:     "This attribute identifies the resolution that Printer uses for a certain Job."  Since this is a Job attribute, not a Printer attribute, it identifies the resolution that the user would like the Printer to use.	

Suggested change:   Change "Printer uses" to "the Printer should use".
----------------------------
Item:      4
Line:      2302-2326
Topic:   Standard values for "finishings"  attribute

Description:   Enum is grossly underpowered for specifying finishings (staple location, number and placement of punch holes, front cover vs. back cover,?)	

Suggested change:  Make this an enum with an optional following octetString?  A general solution for extending finishing attributes with multiple fields should be addressed ASAP, before there are many inconsistent/conflicting type2 enum values assigned.
----------------------------
Item:      5
Line:      3247-3252
Topic:   "color-supported" values

Description:    With different printers having different levels of color support, including full color and highlight color, this should be (at a minimum) an enum instead of a boolean.

Suggested change:  Make color-supported attribute an enum value.