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 Feb 28, 2019, at 4:29 PM, Kennedy, Smith (Wireless & Standards Architect) via ipp <<a href="mailto:ipp@pwg.org" class="">ipp@pwg.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Hi there,<br class=""><br class="">As we just discussed in the IPP WG meeting today, I will take my latest JPS2v2 draft and start removing stuff to produce the first draft of "IPP Enterprise Printing Extensions". What should I remove from "IPP Enterprise Printing Extensions"?<br class=""><br class="">To Be Removed<br class="">============================<br class="">- "job-save-disposition" and whatever we don't like about the "Job Save and Reprint" feature<br class=""></div></div></blockquote><div><br class=""></div>Agreed.</div><div><br class=""><blockquote type="cite" class=""><div class=""><div class="">- "proof-print" (because we are going to redefine how that works too since it has crossover with Job Storage)<br class=""></div></div></blockquote><div><br class=""></div>I *thought* we weren't decided on this - the main issues brought up at the F2F were:</div><div><br class=""></div><div>- There is no way to discard a proof print job, either explicitly or implicitly (i.e. how long is the job retained for?) - the "job-retain-until" Job Template attribute was a potential fix for this and the more general Job Storage use case.</div><div>- Today's Clients can just submit a new job with the same document data for the "production run"; whether this matches with enterprise/light production work flows is a question I'd like to answer.</div><div><br class=""></div><div>IMHO we really just need to answer the second question before we decide proof-print's fate.</div><div><br class=""></div><div><blockquote type="cite" class=""><div class=""><div class="">- Stuff Mike is moving over to IPP Job Extensions v1.1 (Cancel-Jobs, Cancel-My-Jobs, some others)<br class=""></div></div></blockquote><div><br class=""></div>Aside from the (REQUIRED) Cancel-Jobs, Cancel-My-Jobs, and Close-Job operations, I think I should move over the following (mostly OPTIONAL) attributes to Job Extensions v1.1:</div><div><br class=""></div><div>- job-creation-attributes-supported</div><div>- job-hold-until-time/-supported</div><div>- job-ids/-supported (REQUIRED)</div><div>- job-spooling-supported</div><div>- media-col.media-tooth</div><div>- media-col.media-grain</div><div>- media-col.media-thickness</div><div><div>- media-col-database</div><div><div>- printer-detailed-status-messages</div><div class="">- which-jobs-supported</div><div class=""><br class=""></div></div><div>and the (OPTIONAL) keyword values for:</div><div><br class=""></div><div>- pdl-override-supported</div><div>- which-jobs</div><div><br class=""></div><div>and the amended semantics for Get-Printer-Attributes (media-col-database), Get-Jobs (which-jobs), Hold-Job (job-hold-until-time), and Set-Job-Attributes (job-hold-until-time).</div><div><br class=""></div><div>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><br class=""></div><div>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><br class=""></div><div>(I'll also need to update the v1.1 version of IPP Everywhere for these attributes/operations)</div><div><br class=""></div><div><blockquote type="cite" class=""><div class=""></div></blockquote></div><blockquote type="cite" class=""><div class=""><div class="">- Deprecated or obsoleted operations and attributes<br class=""></div></div></blockquote><div><br class=""></div>IMHO, the following attributes should be obsoleted:</div><div><br class=""></div><div>- feed-orientation/-default/-supported: Really bad way for Client to tell Printer which way the media is loaded; media-feed-orientation replaces it in JPS3...</div><div>- font-name-requested/-default/-supported: No sense specifying a font name when the size is useless, Unicode plain text printing often requires multiple fonts</div><div>- font-size-requested/-default/-supported: Font sizes in integer points are useless</div><div>- job-save-disposition/-default/-supported: Poorly specified, not interoperable</div><div>- pdl-init-file/-default/-supported: Poorly specified, not interoperable, too much focus on proprietary PDLs</div><div>- job-save-printer-make-and-model: Supports job-save-disposition</div><div>- max-save-info-supported: Supports job-save-disposition</div><div><br class=""></div><div>and we can remove the "media-type" registrations since MSN2 imported them.</div><div><br class=""></div><div><blockquote type="cite" class=""><div class=""><div class="">To Be Added<br class="">============================<br class="">- Smith's "job-storage" collection and related attributes (draft, to be debated)<br class="">- Smith's "job-print-password" and related attributes (draft, to be debated)<br class=""></div></div></blockquote></div><div><blockquote type="cite" class=""><div class=""><div class="">- Use case and requirements first drafts for the NextGen IPP Job Accounting solution (to replace "document-format-details" since that is now deprecated / obsoleted)<br class=""></div></div></blockquote><div><br class=""></div>- job-retain-until/-default/-supported (how long is job retained/stored?)</div><div><br class=""></div><div class="">
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: "Andale Mono"; font-variant-ligatures: normal; font-variant-east-asian: normal; font-variant-position: normal; line-height: normal; border-spacing: 0px; -webkit-text-decorations-in-effect: none;"><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>