attachment
<div dir="ltr"><div>Hi Mike,</div><div><br></div><div>I actually favor v2.0, with a firm hand making attributes filling</div><div>holes in IPP/1.1 (retention, history, etc.) as REQUIRED and</div><div>as many as possible remaining attributes as RECOMMENDED.</div><div><br></div><div>I hope we stop using OPTIONAL in IPP specs and reserve it</div><div>for "experimental" or "narrow-use" new stuff in Registrations.</div><div><br></div><div>Cheers,</div><div>- Ira</div><div><br></div><div><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr">Ira McDonald (Musician / Software Architect)<br>Co-Chair - TCG Trusted Mobility Solutions WG</div><div>Co-Chair - TCG Metadata Access Protocol SG<br></div><div dir="ltr">Chair - Linux Foundation Open Printing WG<br>Secretary - IEEE-ISTO Printer Working Group<br>Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG<br>IETF Designated Expert - IPP & Printer MIB<br>Blue Roof Music / High North Inc<br><a style="color:rgb(51,51,255)" href="http://sites.google.com/site/blueroofmusic" target="_blank">http://sites.google.com/site/blueroofmusic</a><br><a style="color:rgb(102,0,204)" href="http://sites.google.com/site/highnorthinc" target="_blank">http://sites.google.com/site/highnorthinc</a><br>mailto: <a href="mailto:blueroofmusic@gmail.com" target="_blank">blueroofmusic@gmail.com</a><br>PO Box 221 Grand Marais, MI 49839 906-494-2434<br><br><div style="display:inline"></div><div style="display:inline"></div><div style="display:inline"></div><div></div><div></div><div></div><div></div></div></div></div></div></div></div></div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Mar 7, 2019 at 12:51 PM Michael Sweet via ipp <<a href="mailto:ipp@pwg.org">ipp@pwg.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">All,<br>
<br>
I mentioned this in a previous thread, but wanted to bring this up in a new thread to discuss separately.<br>
<br>
We are in the process of updating PWG 5100.7-2003: IPP Job Extensions (JOBEXT), and based on previous discussions have decided to incorporate parts of PWG 5100.11-2010: IPP Job and Printer Extensions - Set 2 (JPS2) that have more general usefulness, with the remaining enterprise functionality going into a new IPP Enterprise Printing Extensions specification to replace 5100.11 (which will be obsoleted, like we did for the original overrides spec many years ago).<br>
<br>
Many of the attributes coming from 5100.11 are OPTIONAL, so adding them to Job Extensions v1.1 poses no problem for our defined standards errata process - no change in conformance for the original 5100.7 so the 5100.7-2019 update will be backwards-compatible with any implementation conformaing to 5100.7-2003.<br>
<br>
However, JPS2 also defines four new REQUIRED operations and a REQUIRED operation attribute (job-ids). Keeping these in a 5100.11 errata update would pose no problem, but PWG Process/3.0 says nothing about cross-spec errata updates.<br>
<br>
Using a conservative interpretation of the approved process, we would need to change the major version number of the Job Extensions specification to increase the conformance requirements, and then use the "long" process (verification of prototyping, PWG Last Call, and PWG Formal Vote) instead of the "short" process (PWG Call for Objections).<br>
<br>
An alternative is to make these operations RECOMMENDED and job-ids conditionally required - then there is no conformance increase and we can use the short process for an errata update. Since IPP Everywhere already makes most of these operations REQUIRED already, the practical reality is that they will be required attributes.<br>
<br>
Thoughts?<br>
<br>
_________________________________________________________<br>
Michael Sweet, Senior Printing System Engineer<br>
<br>
_______________________________________________<br>
ipp mailing list<br>
<a href="mailto:ipp@pwg.org" target="_blank">ipp@pwg.org</a><br>
<a href="https://www.pwg.org/mailman/listinfo/ipp" rel="noreferrer" target="_blank">https://www.pwg.org/mailman/listinfo/ipp</a><br>
</blockquote></div>