attachment
<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Smith,<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Mar 6, 2019, at 1:20 PM, Kennedy, Smith (Wireless & Standards Architect) <<a href="mailto:smith.kennedy@hp.com" class="">smith.kennedy@hp.com</a>> wrote:</div><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class=""><div class="">...</div></div><div class=""><div class=""><b class=""><u class="">Kept:</u></b></div></div><div class=""><div class=""><div class="">job-password</div></div></div><div class=""><div class=""><div class="">job-password-encryption</div></div></div><div class=""><div class=""><div class="">proof-print/-default/-supported</div></div></div><div class=""><div class=""><div class="">Additional keywords for "which-jobs" ('proof-print' and 'stored' defined locally, 'saved' to be deprecated)</div></div></div></blockquote></div></div></blockquote><div><br class=""></div>OK, so I'll define the standard which-jobs values in Job Extensions, and you'll define the new ones for EPE?</div><div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class="">
<div class=""><div class="">I have a few questions too:</div><div class=""><br class=""></div></div></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class=""><div class=""><div class=""><u class=""><b class="">Questions:</b></u></div></div></div><div class=""><div class=""><div class="">job-cancel-after/-default/-supported --> Job Extensions v1.1? If not, why not?</div></div></div></blockquote></div></div></blockquote><div><br class=""></div>More advanced job management seems more enterprise-y to me, but I'm good either way.</div><div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class=""><div class=""><div class="">job-delay-ouptut-until/-default/-supported --> Job Extensions v1.1? If not, why not?</div></div></div><div class=""><div class=""><div class="">job-delay-output-until-time/-supported --> Job Extensions v1.1? If not, why not?</div></div></div></blockquote></div></div></blockquote><div><br class=""></div>Likewise, these seem like an enterprise job scheduling feature.</div><div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class=""><div class=""><div class="">job-phone-number/-default/-supported --> Job Extensions v1.1? Separate registration? (Use case is ambiguous...)</div></div></div></blockquote></div></div></blockquote><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class=""><div class=""><div class="">job-recipient-name/-default/-supported --> Job Extensions v1.1? Separate registration? (Use case is ambiguous...)</div></div></div></blockquote></div></div></blockquote><div><br class=""></div>Recipient/contact information for the job seems like an enterprise or light-production use case.</div><div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class=""><div class=""><div class=""><div class="">job-retain-until/-default/-supported --> Job Extensions v1.1? If not, why not?</div></div></div></div><div class=""><div class=""><div class=""><div class="">job-retain-until-time/-default/-supported --> Job Extensions v1.1? If not, why not?</div></div></div></div></blockquote></div></div></blockquote><div><br class=""></div>I believe these were intended to resolve the ambiguity with how long a proof print/stored job is retained. Also, I don't think we want a job-retain-until-time-default, since the value is an absolute dateTime value (unless we make -time an integer and add a -date version for dateTime?)</div><div><br class=""></div><div><br class=""></div><div><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><div class=""><blockquote type="cite" class=""><div class="">On Feb 28, 2019, at 3:17 PM, Michael Sweet <<a href="mailto:msweet@apple.com" class="">msweet@apple.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><div class="">These all have a clear focus on jobs and job submission/creation and are definitely not limited to the scope of Enterprise Printing. There is a slight process issue we need to discuss, however: the new Job Extensions will have conformance requirements for required operations and attributes that were not in v1.0 of Job Extensions but *were* in v1.0 of JPS2 - the errata process doesn't allow us to change conformance requirements without going through PWG Last Call and Formal Vote, but then we are kindof merging JOBEXT and JPS2 into a single errata update and publishing a new Enterprise Printing specification with updated JPS2 content. Fuzzy logic... :)</div></div></div></div></blockquote><div class=""><br class=""></div>We should account for this in Process 4.0 somehow.</div><div class=""><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><div class=""><br class=""></div><div class="">Anyways, since this constitutes all of the non-obsoleted/migrated content from JPS2, I'd prefer to update things in one shot rather than processing two documents.</div></div></div></div></blockquote><div class=""><br class=""></div>+1</div><div class=""><br class=""></div><br class=""></div></div></div></blockquote></div><br class=""><div class="">
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: 'Andale Mono'; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; border-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-stroke-width: 0px;"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: 'Andale Mono'; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; border-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-stroke-width: 0px;"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">_________________________________________________________<br class="">Michael Sweet, Senior Printing System Engineer</div></span></div></span>
</div>
<br class=""></body></html>