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,<div class=""><br class=""></div><div class="">The "job-uri" attribute is a holdover from IPP/1.0 where every IPP object would get its own URI. However, since the URI path information was never standardized (RFC 3510 only went so far as to say that "job-uri" SHOULD use "printer-uri" as a prefix, and that came out years after IPP/1.0), interoperability between Clients and Printers was a serious problem and made both implementations needlessly complicated. In contrast, the "printer-uri" + integer identifier mechanism is both trivial and cleaner to implement.</div><div class=""><br class=""></div><div class="">Subsequent objects (subscription, document, and now resource) have only ever used "xxx-id (integer(1:MAX))".</div><div class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On May 1, 2018, at 2:34 PM, Kennedy, Smith (Wireless & Standards Architec) <<a href="mailto:smith.kennedy@hp.com" class="">smith.kennedy@hp.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html; charset=us-ascii" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi there,<div class=""><br class=""></div><div class="">When interacting with a Job object, like for instance in a Get-Job-Attributes operation, RFC 8011 section 4.3 says:</div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class="">
<div class="page" title="Page 73">
<div class="section" style="background-color: rgb(100.000000%, 100.000000%, 100.000000%)">
<div class="layoutArea">
<div class="column">
<pre class=""><span style="font-size: 10.000000pt; font-family: 'Courier'; color: rgb(0.000000%, 0.000000%, 100.000000%)" class="">4.3</span><span style="font-size: 10.000000pt; font-family: 'Courier'" class="">. Job Operations
</span></pre>
<pre class=""><span style="font-size: 10.000000pt; font-family: 'Courier'" class=""> All Job operations are directed at Jobs. A Client MUST always supply
some means of identifying the Job object in order to identify the
correct target of the operation. That Job identification SHOULD be
the combination of a Printer URI with a Job ID but MAY be the
(single) Job URI. The IPP implementation MUST support both forms of
identification for every Job.
</span></pre>
</div>
</div>
</div>
</div></div></blockquote><div class="">Why briefly is Printer URI + Job ID preferable to Job URI again?</div><div class=""><br class=""><div class="">
<div dir="auto" style="letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div style="letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Smith<br class=""><br class="">/**<br class=""> Smith Kennedy<br class=""> Wireless & Standards Architect - IPG-PPS<br class=""> Standards - IEEE ISTO PWG / Bluetooth SIG / Wi-Fi Alliance / NFC Forum / USB-IF<br class=""> Chair, IEEE ISTO Printer Working Group<br class=""> HP Inc.<br class="">*/<br class=""><br class=""><br class=""></div></div>
</div>
<br class=""></div></div>_______________________________________________<br class="">ipp mailing list<br class=""><a href="mailto:ipp@pwg.org" class="">ipp@pwg.org</a><br class="">https://www.pwg.org/mailman/listinfo/ipp<br class=""></div></blockquote></div><br class=""><div class="">
<span class="Apple-style-span" style="border-collapse: separate; 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=""></div></body></html>