attachment-0001
<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"><base href="x-msg://1445/"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Glen,<div><br></div><div>Comments inline...</div><div><br><div><div>On Aug 21, 2012, at 11:13 AM, "Petrie, Glen" <<a href="mailto:glen.petrie@eitc.epson.com">glen.petrie@eitc.epson.com</a>> wrote:</div><blockquote type="cite"><div lang="EN-US" link="blue" vlink="blue" style="font-family: 'Andale Mono'; font-size: medium; 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; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div class="Section1" style="page: Section1; "><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman'; "><font size="3" color="blue" face="Cambria"><span style="font-size: 12pt; font-family: Cambria; color: blue; ">Mike (all)<o:p></o:p></span></font></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman'; "><font size="3" color="blue" face="Cambria"><span style="font-size: 12pt; font-family: Cambria; color: blue; "> </span></font></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman'; "><font size="3" color="blue" face="Cambria"><span style="font-size: 12pt; font-family: Cambria; color: blue; ">The change below pushes the burden to the printer (at an increased cost to the printer) while the Client, a software entity, has less burden. What is wrong with<o:p></o:p></span></font></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman'; "><font size="3" color="blue" face="Cambria"><span style="font-size: 12pt; font-family: Cambria; color: blue; "> </span></font></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman'; "><font size="3" color="blue" face="Cambria"><span style="font-size: 12pt; font-family: Cambria; color: blue; ">1. Discovery:<o:p></o:p></span></font></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman'; "><font size="3" color="blue" face="Cambria"><span style="font-size: 12pt; font-family: Cambria; color: blue; "> </span></font></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman'; "><font size="3" color="blue" face="Cambria"><span style="font-size: 12pt; font-family: Cambria; color: blue; "> a. Clients MUST support DNS-SD and WS-Discovery<o:p></o:p></span></font></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman'; "><font size="3" color="blue" face="Cambria"><span style="font-size: 12pt; font-family: Cambria; color: blue; "> b. Printers MUST support either DNS-SD or WS-Discovery and RECOMMENED to support both.</span></font></div></div></div></blockquote><div><br></div>Pretty much all printers already support DNS-SD and WS-Discovery, which is why we opted to put the "burden" on the printers (since they already carry that burden).</div><div><br></div><div><blockquote type="cite"><div lang="EN-US" link="blue" vlink="blue" style="font-family: 'Andale Mono'; font-size: medium; 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; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div class="Section1" style="page: Section1; "><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman'; "><span style="color: blue; font-family: Cambria; font-size: 12pt; ">2. Document Formats:</span></div><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman'; "><font size="3" color="blue" face="Cambria"><span style="font-size: 12pt; font-family: Cambria; color: blue; "> </span></font></div><div style="margin: 0in 0in 0.0001pt 27pt; font-size: 12pt; font-family: 'Times New Roman'; text-indent: -0.25in; "><font size="3" color="blue" face="Cambria"><span style="font-size: 12pt; font-family: Cambria; color: blue; "><span>a.<font size="1" face="Times New Roman"><span style="font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-family: 'Times New Roman'; "> <span class="Apple-converted-space"> </span></span></font></span></span></font><font color="blue" face="Cambria">Clients MUST support both JPEG and PWG Raster<o:p></o:p></font></div><div style="margin: 0in 0in 0.0001pt 27pt; font-size: 12pt; font-family: 'Times New Roman'; text-indent: -0.25in; "><font size="3" color="blue" face="Cambria"><span style="font-size: 12pt; font-family: Cambria; color: blue; "><span>b.<font size="1" face="Times New Roman"><span style="font-style: normal; font-variant: normal; font-weight: normal; font-size: 7pt; line-height: normal; font-family: 'Times New Roman'; "> <span class="Apple-converted-space"> </span></span></font></span></span></font><font color="blue" face="Cambria">Printers MUST support either JPEG or PWG Raster and RECOMMENDED to support both.</font></div></div></div></blockquote><div><br></div>I personally would rather just see a single format (PWG Raster) be required since it is the only simple raster format that works for text, graphics, and photos. However, Justin objected to PWG Raster because Microsoft currently does not support it. Thus the "great compromise".</div><div><br></div><div>Many printers already support JPEG via dedicated hardware, and PWG Raster uses the same compression algorithm that is used by most vendor PDLs, so again I am not sure we are really increasing the burden for printers and the printer requirement to support both has been in the spec for over a year now...</div><div><br></div><div><blockquote type="cite"><div lang="EN-US" link="blue" vlink="blue" style="font-family: 'Andale Mono'; font-size: medium; 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; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div class="Section1" style="page: Section1; "><div style="margin: 0in 0in 0.0001pt; font-size: 12pt; font-family: 'Times New Roman'; "><font size="3" color="blue" face="Cambria"><span style="font-size: 12pt; font-family: Cambria; color: blue; ">This change to the printer requirements could mean a faster time to market since printers are already support one of the discoveries and documents formats but may not support both discoveries and document formats.</span></font></div></div></div></blockquote><div><br></div>I would argue that document formats and discovery protocols are not the hard parts - doing a GOOD implementation of IPP is much more difficult, as the interoperability reports can attest.</div><div><br></div><div>
<span class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px; "><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; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">_________________________________________________________<br>Michael Sweet, Senior Printing System Engineer, PWG Chair</div></span></span>
</div>
<br></div><br />--
<br />This message has been scanned for viruses and
<br />dangerous content by
<a href="http://www.mailscanner.info/"><b>MailScanner</b></a>, and is
<br />believed to be clean.
</body></html>