attachment-0001

As a random bystander I can confirm that &quot;one of X and Y&quot; sounds a bit odd. Although the context does make it clear.<br><br>How about &quot;Clients MUST support either DNS-SD or WS-Discovery or both&quot; to eliminate any final confusion with English&#39;s exclusive or.<br>
<br>While I&#39;m being usless let me also suggest another wording &quot;The intersection between the set of client&#39;s supported protocols and the set {DNS-SD, WS-Discovery} must not be the empty set.&quot;<br><br>Daniel<br>
<br><div class="gmail_quote">2012/8/20 Randy Turner <span dir="ltr">&lt;<a href="mailto:rturner@amalfisystems.com" target="_blank">rturner@amalfisystems.com</a>&gt;</span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word"><div><br></div> i think I understand the compromise, although I would have worded 1b and 2b a little different<div><br></div><div>Clients MUST support either DNS-SD or WS-Discovery….</div>
<div><br></div><div>It&#39;s just a different use of a contraction</div><div><br></div><div>&quot;…one of DNS-SD AND WS-Discovery&quot;  seemed to use an AND contraction which implied both - someone might inadvertently parse this in a way we didn&#39;t expect….although I got the gist of the compromise.</div>
<div><br></div><div>R.</div><div><br><div><div><div class="h5"><div>On Aug 20, 2012, at 9:16 PM, William A Wagner wrote:</div><br></div></div><blockquote type="cite"><span style="border-collapse:separate;font-family:Helvetica;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;font-size:medium"><div link="blue" vlink="purple" lang="EN-US">
<div><div class="h5"><div><div style="margin-top:0in;margin-right:0in;margin-left:0in;margin-bottom:0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">I think this is a practical and reasonable compromise. From at least my perspective, this does not put an unreasonable additional burden on printers while  making potentially easier for clients to achieve and claim compliance.<u></u><u></u></span></div>
<div style="margin-top:0in;margin-right:0in;margin-left:0in;margin-bottom:0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">Bill Wagner<u></u><u></u></span></div>
<div style="margin-top:0in;margin-right:0in;margin-left:0in;margin-bottom:0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u> <u></u></span></div>
<div><div style="border-right-style:none;border-bottom-style:none;border-left-style:none;border-width:initial;border-color:initial;border-top-style:solid;border-top-color:rgb(181,196,223);border-top-width:1pt;padding-top:3pt;padding-right:0in;padding-bottom:0in;padding-left:0in">
<div style="margin-top:0in;margin-right:0in;margin-left:0in;margin-bottom:0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif"><b><span style="font-size:10pt;font-family:Tahoma,sans-serif">From:</span></b><span style="font-size:10pt;font-family:Tahoma,sans-serif"><span> </span><a href="mailto:ipp-bounces@pwg.org" style="color:blue;text-decoration:underline" target="_blank">ipp-bounces@pwg.org</a><span> </span>[mailto:<a href="mailto:ipp-bounces@pwg.org" target="_blank">ipp-bounces@pwg.org</a>]<span> </span><b>On Behalf Of<span> </span></b>Michael Sweet<br>
<b>Sent:</b><span> </span>Monday, August 20, 2012 9:42 PM<br><b>To:</b><span> </span><a href="mailto:ipp@pwg.org" style="color:blue;text-decoration:underline" target="_blank">ipp@pwg.org</a><br><b>Subject:</b><span> </span>[IPP] IPP Everywhere and &quot;The Great Compromise&quot;<u></u><u></u></span></div>
</div></div><div style="margin-top:0in;margin-right:0in;margin-left:0in;margin-bottom:0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif"><u></u> <u></u></div><div style="margin-top:0in;margin-right:0in;margin-left:0in;margin-bottom:0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif">
All,<u></u><u></u></div><div><div style="margin-top:0in;margin-right:0in;margin-left:0in;margin-bottom:0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif"><u></u> <u></u></div></div><div><div style="margin-top:0in;margin-right:0in;margin-left:0in;margin-bottom:0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif">
We discussed the PWG Last Call comments received thus far at today&#39;s IPP WG conference call.  Two of the comments concerned the client requirements to support DNS-SD for discovery and both PWG Raster and JPEG for document formats.  After over an hour of spirited debate, the following &quot;great compromise&quot; was proposed to resolve the last call comments:<u></u><u></u></div>
</div><div><div style="margin-top:0in;margin-right:0in;margin-left:0in;margin-bottom:0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif"><u></u> <u></u></div></div><div><div style="margin-top:0in;margin-right:0in;margin-left:0in;margin-bottom:0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif">
1. Discovery:<u></u><u></u></div></div><div><div style="margin-top:0in;margin-right:0in;margin-left:0in;margin-bottom:0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif"><u></u> <u></u></div></div><div><div style="margin-top:0in;margin-right:0in;margin-left:0in;margin-bottom:0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif">
   a. Printers MUST support both DNS-SD and WS-Discovery (adds WS-Discovery)<u></u><u></u></div></div><div><div style="margin-top:0in;margin-right:0in;margin-left:0in;margin-bottom:0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif">
   b. Clients MUST support at least one of DNS-SD and WS-Discovery (Clients can choose amongst the two required protocols)<u></u><u></u></div></div><div><div style="margin-top:0in;margin-right:0in;margin-left:0in;margin-bottom:0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif">
<u></u> <u></u></div></div><div><div style="margin-top:0in;margin-right:0in;margin-left:0in;margin-bottom:0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif">2. Document Formats:<u></u><u></u></div></div>
<div><div style="margin-top:0in;margin-right:0in;margin-left:0in;margin-bottom:0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif"><u></u> <u></u></div></div><div><div style="margin-top:0in;margin-right:0in;margin-left:0in;margin-bottom:0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif">
   a. Printers MUST support both JPEG and PWG Raster (no change)<u></u><u></u></div></div><div><div style="margin-top:0in;margin-right:0in;margin-left:0in;margin-bottom:0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif">
   b. Clients MUST support at least one of JPEG and PWG Raster (relaxes conformance - previously a Client had to support both)<u></u><u></u></div></div><div><div style="margin-top:0in;margin-right:0in;margin-left:0in;margin-bottom:0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif">
<u></u> <u></u></div></div><div><div style="margin-top:0in;margin-right:0in;margin-left:0in;margin-bottom:0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif">Please comment on the proposed changes.<u></u><u></u></div>
</div><div><div style="margin-top:0in;margin-right:0in;margin-left:0in;margin-bottom:0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif"><u></u> <u></u></div></div><div><div><div><div style="margin-top:0in;margin-right:0in;margin-left:0in;margin-bottom:0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif">
<span style="font-size:13.5pt;font-family:&#39;Andale Mono&#39;,serif">_________________________________________________________<br>Michael Sweet, Senior Printing System Engineer, PWG Chair<u></u><u></u></span></div></div>
</div><div style="margin-top:0in;margin-right:0in;margin-left:0in;margin-bottom:0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif"><u></u> <u></u></div></div><div style="margin-top:0in;margin-right:0in;margin-left:0in;margin-bottom:0.0001pt;font-size:12pt;font-family:&#39;Times New Roman&#39;,serif">
<br>--<span> </span><br>This message has been scanned for viruses and<span> </span><br>dangerous content by<span> </span><a href="http://www.mailscanner.info/" style="color:blue;text-decoration:underline" target="_blank"><b>MailScanner</b></a>, and is<span> </span><br>
believed to be clean.<u></u><u></u></div></div><br>--<span> </span><br>This message has been scanned for viruses and<span> </span><br>dangerous content by<span> </span><a href="http://www.mailscanner.info/" style="color:blue;text-decoration:underline" target="_blank"><b>MailScanner</b></a>, and is<span> </span><br>
</div></div>believed to be clean.<span> </span>_______________________________________________<br>ipp mailing list<br><a href="mailto:ipp@pwg.org" style="color:blue;text-decoration:underline" target="_blank">ipp@pwg.org</a><br>
<a href="https://www.pwg.org/mailman/listinfo/ipp" style="color:blue;text-decoration:underline" target="_blank">https://www.pwg.org/mailman/listinfo/ipp</a></div></span></blockquote></div><br></div><div class="im"><br>-- 
<br>This message has been scanned for viruses and
<br>dangerous content by
<a href="http://www.mailscanner.info/" target="_blank"><b>MailScanner</b></a>, and is
<br>believed to be clean.
</div></div>
<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><br>
<br></blockquote></div><br>
<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.