attachment
<html 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;}
/* 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:#954F72;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:10.0pt;
margin-left:.5in;
mso-add-space:auto;
line-height:115%;
font-size:12.0pt;
font-family:"Arial",sans-serif;}
p.MsoListParagraphCxSpFirst, li.MsoListParagraphCxSpFirst, div.MsoListParagraphCxSpFirst
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
mso-add-space:auto;
line-height:115%;
font-size:12.0pt;
font-family:"Arial",sans-serif;}
p.MsoListParagraphCxSpMiddle, li.MsoListParagraphCxSpMiddle, div.MsoListParagraphCxSpMiddle
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
mso-add-space:auto;
line-height:115%;
font-size:12.0pt;
font-family:"Arial",sans-serif;}
p.MsoListParagraphCxSpLast, li.MsoListParagraphCxSpLast, div.MsoListParagraphCxSpLast
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:10.0pt;
margin-left:.5in;
mso-add-space:auto;
line-height:115%;
font-size:12.0pt;
font-family:"Arial",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=EN-US link=blue vlink="#954F72"><div class=WordSection1><p class=MsoNormal><span style='font-size:12.0pt'>Sorry, should have brought these questions up sooner, but we have looked at pieces of this over such a long time I was waiting for a more or less complete final version. These are my reactions on reading the spec, although I haven’t gotten that far. Don’t need a formal response, but perhaps we can address them sometime in conference.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt'>Thanks<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt'><o:p> </o:p></span></p><div><p class=MsoNormal><span style='font-size:12.0pt'>Format:<o:p></o:p></span></p><p class=MsoListParagraphCxSpFirst><span style='font-family:"Calibri",sans-serif'>a. Three paragraph breaks at top margin seems excessive , Some unfortunate page breaks. (5, 18, 21)<o:p></o:p></span></p><p class=MsoListParagraphCxSpLast><span style='font-family:"Calibri",sans-serif'>b. assorted double spaces<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt'>Line 932 "a Resource by analogy to to “date-time-at-processing<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt'>para 1.1 --1.3 Do These really belong here, and with this level of detail? Uses terminology in section 2.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt'>382 Rationale for Two ... - " IPP System object and (via a System response to the Get-Printers operation) zero or more IPP Printer objects" Why two? Perhaps multiple?<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt'>440 "<i>System</i>: Listener for incoming..."<o:p></o:p></span></p><p class=MsoListParagraphCxSpFirst><span style='font-family:"Calibri",sans-serif'>a. Should this be Imaging System? <o:p></o:p></span></p><p class=MsoListParagraphCxSpMiddle><span style='font-family:"Calibri",sans-serif'>b. Do we need same entity in both Protocol and Printer Terminology? (e.g., Printer)<o:p></o:p></span></p><p class=MsoListParagraphCxSpLast><span style='font-family:"Calibri",sans-serif'>c. Do Printer, System entities under protocol correspond to Printer and System Objects described later?<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt'>483 "<i>Imaging System:</i> A logical or physical system supports a System object and a System Service for monitoring and management of one or more Imaging Services"<o:p></o:p></span></p><p class=MsoListParagraphCxSpFirst><span style='font-family:"Calibri",sans-serif'>a. That supports? <o:p></o:p></span></p><p class=MsoListParagraphCxSpMiddle><span style='font-family:"Calibri",sans-serif'>b. Before the statement was " zero or more IPP Printer objects" Zero or one? <o:p></o:p></span></p><p class=MsoListParagraphCxSpLast><span style='font-family:"Calibri",sans-serif'>c. Is the Imaging System managing Printer Objects, Printers or Imaging Services? Can we use Imaging Service rather than Printer after having defined them as synonymous?<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt'>470. FaxoutJob, Why not use Job in definition? Also in Scan Job, Transform Job, Print Job.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt'>595 "After Jane initiates service enumeration by using the IPP Client on her laptop to send a query to the Imaging System for the list of available services." No After?<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt'>3.2.4 " to extend the functionality of the Imaging System" Is it the functionality of the Imaging System or of Imaging Services supported by the Imaging System?<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt'>Should some mention be made in used cases of user restictions on some System Service operations?<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt'>646 "managed Imaging System" <o:p></o:p></span></p><p class=MsoListParagraphCxSpFirst><span style='font-family:"Calibri",sans-serif'>a. Why 'managed"? <o:p></o:p></span></p><p class=MsoListParagraphCxSpLast><span style='font-family:"Calibri",sans-serif'>b. print service is a defined term(initial Caps) <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt'>648. Why "system" in this document and not Imaging System?<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt'>653. Note is interesting, but does it belong here?<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt'>666. to reuse existing IPP Printer operations and attributes in the individual Imaging Services, but NOT directly in this specification" <o:p></o:p></span></p><p class=MsoListParagraphCxSpFirst><span style='font-family:"Calibri",sans-serif'>a. The "but ..." phrase is unclear.<o:p></o:p></span></p><p class=MsoListParagraphCxSpMiddle><span style='font-family:"Calibri",sans-serif'>b. Printer vs Imaging Service. Confusing, since definitions said they were synonymous<o:p></o:p></span></p><p class=MsoListParagraphCxSpLast><span style='font-family:"Calibri",sans-serif'>c. Note?<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt'>674, 681, " but NOT directly in this specification" same question<o:p></o:p></span></p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><div style='mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='border:none;padding:0in'><b>From: </b><a href="mailto:ipp@pwg.org">Michael Sweet via ipp</a><br><b>Sent: </b>Wednesday, May 15, 2019 10:05 AM<br><b>To: </b><a href="mailto:ipp@pwg.org">PWG IPP Workgroup</a><br><b>Subject: </b>[IPP] WG Last Call: IPP System Service v1.0 (Ends May 31, 2019)</p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>All,</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>This message starts the IPP Workgroup Last Call of the IPP System Service v1.0 specification, available at:</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippsystem10-20190515.pdf</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>All required (and many optional/recommended) portions of this specification have been prototyped in the "ippserver" program in the IPP Sample Code project.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Please reply to this message with any feedback, which we can review at the following IPP workgroup conference call.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thanks!</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>_________________________________________________________</p><p class=MsoNormal>Michael Sweet, Senior Printing System Engineer</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>_______________________________________________</p><p class=MsoNormal>ipp mailing list</p><p class=MsoNormal>ipp@pwg.org</p><p class=MsoNormal>https://www.pwg.org/mailman/listinfo/ipp</p><p class=MsoNormal><o:p> </o:p></p></div></body></html>