attachment
<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Bill,<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Jul. 25, 2018, at 6:50 PM, <a href="mailto:wamwagner@comcast.net" class="">wamwagner@comcast.net</a> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: Menlo-Regular; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Michael,</div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Thank you for the information. I don’t mean to overly push a point, but making job-reprint-password an operations attribute just seems wrong and may contribute to the misunderstanding of its purpose. Job-password is inherently an operation attribute, and the references you provide point out that it is not returned in a response. So it is not clear why we cannot specify job-reprint-password as a job attribute that is never returned. That is, I do not understand why security information can be specially handled for operation attributes but not for job attributes. Is it perhaps some coding implementation issue?</div></div></div></blockquote><div><br class=""></div>If you define an attribute to be a Job Description, Job Template, or Job Status attribute, you are declaring that the attribute is something that can be returned by the Get-Job-Attributes and Get-Jobs operations (per the semantics of those operations). But an operation attribute has to have explicitly defined semantics (like we have for requesting-user-name getting copied to job-originating-user-name) before it becomes exposed by those operations.</div><div><br class=""></div><div><blockquote type="cite" class=""><div class=""><div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: Menlo-Regular; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">And perhaps I was unclear on the remote reprint request subject, but my point was that if a user were to give reprint access to another user, he could provide the job ID or job UID as well as the password. If a remote reprint capability were desired, I suggest that an operation could be defined to use that information to access the appropriate job and allow remote reprint.</div></div></div></blockquote><div><br class=""></div><div>But again the semantics of the Resubmit-Job operation only allows the Job Owner, administrators, and operators to reprint just any job. We'd need to amend the semantics to allow other users to do it...</div><div><br class=""></div></div><div class="">
<div style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); font-family: Menlo; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; text-decoration: none;">_________________________________________________________<br class="">Michael Sweet, Senior Printing System Engineer</div>
</div>
<br class=""></body></html>