attachment
<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Impact;
panose-1:2 11 8 6 3 9 2 5 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">Smith,<o:p></o:p></p>
<p class="MsoNormal">Sorry about that. I guess we should have used “inherited” and “overridden” in the job/document attribute discussions.<o:p></o:p></p>
<p class="MsoNormal">Pete<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:6.0pt;margin-right:0in;margin-bottom:6.0pt;margin-left:0in">
<span style="font-family:"Impact",sans-serif;color:navy">Peter Zehler</span><span style="font-size:8.0pt;font-family:"Arial",sans-serif;color:navy"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:navy">Xerox Corp.</span><span style="color:#1F497D"><br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:navy">Global Development Group</span><span style="color:#1F497D"><br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:navy">800 Phillips Rd, 111-04A</span><span style="color:#1F497D"><br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:navy">Webster NY, 14580-9701</span><span style="color:#1F497D"><br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:navy">Email:
</span><span style="color:#1F497D"><a href="mailto:Peter.Zehler@Xerox.com" target="_blank"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Peter.Zehler@Xerox.com</span></a><br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:navy">Office:
<a href="tel:%2B1%20%28585%29%20265-8755" target="_blank">+1 (585) 265-8755</a><br>
Fax: <a href="tel:%2B1%20%28585%29%20265-8755" target="_blank">+1 (585) 422-0238</a></span><span style="color:#1F497D"><br>
</span><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:navy">Mobile:
<a href="tel:%2B1%20%28585%29%20329-9508" target="_blank">+1 (585) 329-9508</a><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b>From:</b> ipp [mailto:ipp-bounces@pwg.org] <b>On Behalf Of
</b>Ira McDonald<br>
<b>Sent:</b> Thursday, September 7, 2017 5:48 PM<br>
<b>To:</b> Kennedy, Smith (Wireless Architect) <smith.kennedy@hp.com>; Ira McDonald <blueroofmusic@gmail.com><br>
<b>Cc:</b> PWG IPP WG Reflector <ipp@pwg.org><br>
<b>Subject:</b> Re: [IPP] Question concerning 5100.7 section 5.2 "Job Description attributes that are defaults for the Document(s) in the Job"<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Hi Smith,<o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">You got it right.<o:p></o:p></p>
</div>
<p class="MsoNormal">Remember first there were *only* Job attributes in IPP (no Document<o:p></o:p></p>
</div>
<p class="MsoNormal">object) and much later there were Document attributes. And the word<o:p></o:p></p>
</div>
<p class="MsoNormal">"default" got conscripted into service in admittedly a very different<o:p></o:p></p>
</div>
<p class="MsoNormal">meaning (not pre-configured by an Admin but submitted by a Client).<o:p></o:p></p>
</div>
<p class="MsoNormal">A clarifying paragraph that contrasts these two uses of "default"<o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">(i.e., apples and camels) would be a worthwhile errata to this spec.<o:p></o:p></p>
</div>
<p class="MsoNormal">Cheers,<o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">- Ira<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><br clear="all">
<o:p></o:p></p>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Ira McDonald (Musician / Software Architect)<br>
Co-Chair - TCG Trusted Mobility Solutions WG<br>
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 href="http://sites.google.com/site/blueroofmusic" target="_blank"><span style="color:#3333FF">http://sites.google.com/site/blueroofmusic</span></a><br>
<a href="http://sites.google.com/site/highnorthinc" target="_blank"><span style="color:#6600CC">http://sites.google.com/site/highnorthinc</span></a><br>
mailto: <a href="mailto:blueroofmusic@gmail.com" target="_blank">blueroofmusic@gmail.com</a><br>
Jan-April: 579 Park Place Saline, MI 48176 734-944-0094<br>
May-Dec: PO Box 221 Grand Marais, MI 49839 906-494-2434<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Thu, Sep 7, 2017 at 4:45 PM, Kennedy, Smith (Wireless Architect) <<a href="mailto:smith.kennedy@hp.com" target="_blank">smith.kennedy@hp.com</a>> wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal" style="margin-bottom:12.0pt">Greetings,<br>
<br>
Perhaps since I wasn't involved in the creation of PWG 5100.7, I'm having difficulty understanding the meaning of its section 5.2 "Job Description attributes that are defaults for the Document(s) in the Job". I don't quite understand how to even parse its title.
Does this mean that 5100.7 is prescribing that the Printer MUST use these Job Description attributes' values as the values for the corresponding Document Description attributes in the case where the Client hasn't overtly specified values for the individual
Document objects in a Document creation operation? The use of "default" in this context seems different than the "xxx-default" convention from RFC 8011 etc.<br>
<br>
Smith<br>
<br>
/**<br>
Smith Kennedy<br>
Wireless Architect - Client Software - IPG-PPS<br>
Standards - IEEE ISTO PWG / Bluetooth SIG / Wi-Fi Alliance / NFC Forum / USB IF<br>
Chair, IEEE ISTO Printer Working Group<br>
HP Inc.<br>
*/<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
ipp mailing list<br>
<a href="mailto:ipp@pwg.org">ipp@pwg.org</a><br>
<a href="https://www.pwg.org/mailman/listinfo/ipp" target="_blank">https://www.pwg.org/mailman/listinfo/ipp</a><o:p></o:p></p>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>