Re: [IPP] NODRIVER: Seeking consensus on a solution for use cases 3.2.20 and 3.2.21

Paul Tykodi via ipp <ipp@pwg.org> Fri, 27 March 2020 15:24 UTC

Return-Path: <ipp-bounces@pwg.org>
X-Original-To: ietfarch-ipp-archive@ietfa.amsl.com
Delivered-To: ietfarch-ipp-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C2353A0C9C for <ietfarch-ipp-archive@ietfa.amsl.com>; Fri, 27 Mar 2020 08:24:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.798
X-Spam-Level:
X-Spam-Status: No, score=-2.798 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, MIME_HTML_MOSTLY=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vIl9inLUCFnO for <ietfarch-ipp-archive@ietfa.amsl.com>; Fri, 27 Mar 2020 08:24:48 -0700 (PDT)
Received: from mail.pwg.org (mail.pwg.org [50.116.7.199]) by ietfa.amsl.com (Postfix) with ESMTP id 02D803A0CA5 for <ipp-archive2@ietf.org>; Fri, 27 Mar 2020 08:24:47 -0700 (PDT)
Received: by mail.pwg.org (Postfix, from userid 1002) id 8998C3AB6; Fri, 27 Mar 2020 15:24:47 +0000 (UTC)
Received: from mail.pwg.org (localhost [IPv6:::1]) by mail.pwg.org (Postfix) with ESMTP id C90B332F4; Fri, 27 Mar 2020 15:24:40 +0000 (UTC)
X-Original-To: ipp@pwg.org
Delivered-To: ipp@pwg.org
Received: by mail.pwg.org (Postfix, from userid 1002) id ED23B3A58; Fri, 27 Mar 2020 15:24:38 +0000 (UTC)
Received: from jax4mhob21.registeredsite.com (jax4mhob21.registeredsite.com [64.69.218.109]) by mail.pwg.org (Postfix) with ESMTPS id 937FDC5C for <ipp@pwg.org>; Fri, 27 Mar 2020 15:24:37 +0000 (UTC)
Received: from mailpod.hostingplatform.com ([10.30.71.205]) by jax4mhob21.registeredsite.com (8.14.4/8.14.4) with ESMTP id 02RFOZKp079170 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for <ipp@pwg.org>; Fri, 27 Mar 2020 11:24:35 -0400
Received: (qmail 13087 invoked by uid 0); 27 Mar 2020 15:24:35 -0000
X-TCPREMOTEIP: 24.34.46.33
X-Authenticated-UID: ptykodi@tykodi.com
Received: from unknown (HELO LAPTOPE93UT79P) (ptykodi@tykodi.com@24.34.46.33) by 0 with ESMTPA; 27 Mar 2020 15:24:34 -0000
To: "'Kennedy, Smith (Wireless & IPP Standards)'" <smith.kennedy@hp.com>
References: <F32C5672-6747-4B9B-BF01-94BBE6A87AEF@hp.com>
In-Reply-To: <F32C5672-6747-4B9B-BF01-94BBE6A87AEF@hp.com>
Date: Fri, 27 Mar 2020 11:24:36 -0400
Organization: Tykodi Consulting Services LLC
Message-ID: <010601d6044b$d39676c0$7ac36440$@tykodi.com>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQGXkCp5aWBHTC/4QYlW8uRF38DBpqjZdV4w
Content-Language: en-us
Cc: ipp@pwg.org
Subject: Re: [IPP] NODRIVER: Seeking consensus on a solution for use cases 3.2.20 and 3.2.21
X-BeenThere: ipp@pwg.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: ISTO-PWG Internet Printing Protocol workgroup discussion forum <ipp.pwg.org>
List-Unsubscribe: <https://www.pwg.org/mailman/options/ipp>, <mailto:ipp-request@pwg.org?subject=unsubscribe>
List-Archive: <http://www.pwg.org/pipermail/ipp/>
List-Post: <mailto:ipp@pwg.org>
List-Help: <mailto:ipp-request@pwg.org?subject=help>
List-Subscribe: <https://www.pwg.org/mailman/listinfo/ipp>, <mailto:ipp-request@pwg.org?subject=subscribe>
From: Paul Tykodi via ipp <ipp@pwg.org>
Reply-To: ptykodi@tykodi.com
Content-Type: multipart/mixed; boundary="===============4955233384665162593=="
Errors-To: ipp-bounces@pwg.org
Sender: ipp <ipp-bounces@pwg.org>

Hi Smith,

 

In the 3D Concrete Printing space, the print quality term is discussed in terms of creating a suitable object (i.e. has good quality) and the amount of time the concrete mix can be pumped (typically referred to as “open time”).

 

The following quote comes from “3D printing using concrete extrusion: A roadmap for research” https://www.sciencedirect.com/science/article/pii/S0008884617311924

 

“In parallel, the printability of the material is evaluated by printing a series of single filament stacks. Fig. 6a depicts this process for a test to evaluate flow stress on a cement paste containing a limestone powder. The print quality changes with time where t = 0 is when cement and water first come into contact. At 6 min after mixing, the yield stress of the mixture is too low to support the mass of the material deposited above. It develops until at 60 min, the material has reached a state where it is able to support multiple deposited layers. Continuing the test on this mix finds that the desirable behaviour is maintained through 80 min until at 99 min, the plastic viscosity has reached a point where pumping is difficult. This test can be used to determine the open time for a particular mix, which here was 37 min.”

 

If we are going to enhance the definition of print quality for 2D applications, we probably should determine how to define it more appropriately within our IPP 3D standard as well.

 

Thanks.

 

Best Regards,

 

/Paul

--

Paul Tykodi
Principal Consultant
TCS - Tykodi Consulting Services LLC

Tel/Fax: 603-343-1820
Mobile:  603-866-0712
E-mail:  ptykodi@tykodi.com <mailto:ptykodi@tykodi.com> 
WWW:   <http://www.tykodi.com/> http://www.tykodi.com

 

This e-mail reply and any attachments are confidential and may be privileged.

If you are not the intended recipient, please notify Tykodi Consulting Services LLC 

immediately by replying to this message and destroying all copies of this message 

and any attachments. Thank you

 

From: ipp <ipp-bounces@pwg.org> On Behalf Of Kennedy, Smith (Wireless & IPP Standards) via ipp
Sent: Friday, March 27, 2020 8:57 AM
To: PWG IPP WG Reflector <ipp@pwg.org>
Subject: [IPP] NODRIVER: Seeking consensus on a solution for use cases 3.2.20 and 3.2.21

 

Greetings,

 

In the last review of IPP Driverless Printing Extensions v2.0, concerns were once again raised about extending the set of enum values for "print-quality" to solve the "Manufacturer-Deployed Print Quality Mode" and "Administrator-Deployed Print Quality Mode" use cases (3.2.20 and 3.2.21 in the 20200204 published draft <https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippjobprinterext3v20-20200204.pdf> ). I want to see if we can hash this out via email in between meetings.

 

Before we dive into the implementation choices, I want to focus on the use cases and the user experience(s) we want to support. The use cases I have articulated are important to HP, and I have to believe that they are also important to other printer vendors.

 

The "print-quality" attribute as defined originally in IPP/1.0 (RFC 2566) has remained unchanged for over 20 years:

 


 <https://tools.ietf.org/html/rfc2566#section-4.2.13> 4.2.13 print-quality (type2 enum)

 
 
   This attribute specifies the print quality that the Printer uses for
   the Job.
 
   The standard enum values are:
 
     Value  Symbolic Name and Description
 
     '3'    'draft': lowest quality available on the printer
     '4'    'normal': normal or intermediate quality on the printer
     '5'    'high': highest quality available on the printer

 

Since semantically there is a linear progression from "draft" to "normal" to "high", a "Print Quality" UI selection control could be presented as a slider, or more generically as a radio button group or a pop-up or table list, where only one option can be chosen. The ordering of the three choices is clear and common sense dictates that they should be presented in order rather than out-of-order.

 

Unfortunately, though, this long-standing definition doesn't provide for the possibility that the Printer supports more than 3 quality levels. Nor does it provide space for vendor-defined or site-defined levels, which have existed for quite some time, but always been described in terms of vendor-unique attributes or via legacy (non-IPP) mechanisms. I strongly believe that we need to find a way to allow printers to express their additional print quality options in a way that allows simpler UIs to maintain their simplicity but still allows access to these printer-provided non-standard print quality levels.

 

So, my questions are these:

 

1. Are there any specific objections to these use cases? I believe these are important to all printer manufacturers, not just HP, as a way of expressing an important vector of product differentiation without having to adopt vendor-unique or site-unique attributes, which many universal clients ignore. This undermines efforts to move away from model-specific drivers.

 

 

2. Assuming agreement with the use cases, if we had a green field / blank sheet of paper, how to support the use cases in IPP?

 

Option 1: Extend "print-quality" as per the current proposal

 

 

Option 2: "print-quality-percent" as per Mike's proposal, which I don't think adequately addresses the use cases

 

 

Option 3: Define a new "print-quality-col", which could contain a "print-quality-percent" but could also have printer-provided localized labels and tooltips.

 

 

Option 4: ???

 

 

Please share your thoughts and feedback!

 

 

Smith

/**
    Smith Kennedy
    HP Inc.
*/

 

_______________________________________________
ipp mailing list
ipp@pwg.org
https://www.pwg.org/mailman/listinfo/ipp