Smith,
> On Mar 15, 2019, at 1:52 PM, Kennedy, Smith (Wireless & Standards Architect) via ipp <ipp at pwg.org> wrote:
>> ...
>> I like it! I'll update my EPE draft to specify that and we can discuss that first draft at our next IPP WG meeting.
>> OK, more questions:
>> 1. Should "job-password-action" be an operation attribute, or a Job Template attribute?
Good question. Ordinarily we would make it a Job Template attribute, but I can see the argument for not exposing too many details of "job-password" usage and "job-password-encryption" is also an operation attribute.
Of course, the 'job-password-wait' keyword in "job-state-reasons" will expose the fact that a job is held for a password at the console, but we're stuck with that so an operator or user knows some action is required...
OK, I think I'm slightly more in favor of it being an operation attribute, if for any other reason that I think there will be less chance for an implementor to mess things up... :)
> 2. We would want the semantic to be that if the "job-password-action" was 'retain-only' or 'process-and-retain' then the "job-password" value would become a "hidden Job Status attribute" so that the Printer would require the "job-password" to be entered before any reprints could occur.
I think we should require job-password for any action - yes, a new semantic for Resubmit-Job, but I think one we can get away with since the combination of job-password and Resubmit-Job was not fully specified... (unlike save-disposition and proof-print)
> 3. I'm not clear on the semantic meaning of 'process-and-retain'?
Print it (without password) and then retain for later reprint (using the password).
So basically:
- 'hold-job' is "hold the job until the password is entered, then print and retain"
- 'process-and-retain' is "print the job immediately and then retain"
- 'retain-only' is "do not print the job but retain the job for possible later printing"
Any subsequent reprints require the password. I guess the question is whether the "job-retain-until" for the resubmitted job should be "none" or the copied job should also have the same job-password-xxx values? (I can see the latter actually being a benefit)
_________________________________________________________
Michael Sweet, Senior Printing System Engineer