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=""><div class="">I have a draft of IPP Enterprise Printing Extension (EPE) I'm chipping away at - here's what it has thus far:</div><div class=""><br class=""></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><u class=""><b class="">Added:</b></u><div class="">job-password-length-supported (from Job Password Repertoire registration)</div><div class="">job-password-repertoire-configured/-supported (from Job Password Repertoire registration)</div><div class=""><font color="#ff2600" class="">job-print-password/-default/-supported (to be debated)</font></div><div class=""><div class=""><font color="#ff2600" class="">job-storage/-default/-</font><span style="caret-color: rgb(255, 38, 0); color: rgb(255, 38, 0);" class="">supported (to be debated)</span></div></div><div class=""><div class=""><br class=""></div></div><div class=""><div class=""><u class=""><b class="">Removed:</b></u></div></div><div class=""><div class="">feed-orientation/-default/-supported</div></div><div class=""><div class="">job-save-disposition/-etc (all related Job Template, Job Description and Printer Description attributes)</div></div><div class=""><div class="">job-creation-attributes-supported</div></div><div class=""><div class=""><div class="">job-hold-until-time/-supported</div></div></div><div class=""><div class="">job-ids/-supported (REQUIRED)</div></div><div class=""><div class="">job-spooling-supported</div></div><div class=""><div class="">media-col.media-tooth</div></div><div class=""><div class="">media-col.media-grain</div></div><div class=""><div class="">media-col.media-thickness</div></div><div class=""><div class="">media-col-database</div></div><div class=""><div class="">printer-detailed-status-messages</div></div><div class=""><div class="">which-jobs-supported</div></div><div class=""><div class="">Cancel-Jobs</div></div><div class=""><div class="">Cancel-My-Jobs</div></div><div class=""><div class="">Close-Job</div></div><div class=""><div class=""><br class=""></div></div><div class=""><div><b class=""><u class="">Kept:</u></b></div></div><div class=""><div><div class="">job-password</div></div></div><div class=""><div><div class="">job-password-encryption</div></div></div><div class=""><div><div class="">proof-print/-default/-supported</div></div></div><div class=""><div><div class="">Additional keywords for "which-jobs" ('proof-print' and 'stored' defined locally, 'saved' to be deprecated)</div></div></div></blockquote><div class="">
<div><div class=""><br class=""></div><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><div class=""><u class=""><b class="">Questions:</b></u></div></div></div><div class=""><div><div class="">job-cancel-after/-default/-supported --> Job Extensions v1.1? If not, why not?</div></div></div><div class=""><div><div class="">job-delay-ouptut-until/-default/-supported --> Job Extensions v1.1? If not, why not?</div></div></div><div class=""><div><div class="">job-delay-output-until-time/-supported --> Job Extensions v1.1? If not, why not?</div></div></div><div class=""><div><div class="">job-phone-number/-default/-supported --> Job Extensions v1.1? Separate registration? (Use case is ambiguous...)</div></div></div><div class=""><div><div class="">job-recipient-name/-default/-supported --> Job Extensions v1.1? Separate registration? (Use case is ambiguous...)</div></div></div><div class=""><div><div class=""><div class="">job-retain-until/-default/-supported --> Job Extensions v1.1? If not, why not?</div></div></div></div><div class=""><div><div class=""><div class="">job-retain-until-time/-default/-supported --> Job Extensions v1.1? If not, why not?</div></div></div></div></blockquote><div class=""><div><div class=""><br class=""></div><div class=""></div></div><div><br 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><br class=""></div>We should account for this in Process 4.0 somehow.</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=""><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><br class=""></div>+1</div><div><br class=""></div><br class=""></div></body></html>