attachment

<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On May 9, 2011, at 2:15 PM, Ira McDonald wrote:</div><blockquote type="cite">Hi,<br><br>Glen - correct me please if I'm all wet here...<br><br>On reflection, I think Glen's comment at the end of today's Cloud call about <br>delayed Design Requirements (in the individual IPP EW or MFD Svc specs), <br> was pointing out that our existing specs often have Design Requirements of <br>the form:<br><br>(a) Protocol <abc> must/should support an <xyz> operation...<br>OR<br>(b) Protocol <abc> must/should support a <fgh> feature or property...<br> <br>That is, the target protocol (IPP Everywhere, MFD SOAP, etc.) receives<br>the requirement.<br></blockquote><div><br></div>and FWIW my plan of attack for the use case whitepaper is to make the design requirements a part of each use case as a subsection. When we actually incorporate a use case into a spec we can collate the design requirements in the form we normally use in that spec.</div><div><br><blockquote type="cite">...</blockquote><blockquote type="cite">Which raises another question.  Should the Cloud Imaging Model include<br>actual abstract operations (higher-level than current MFD Model spec)?<br> - These would get mapped to concrete operations in Cloud Print IPP <br>Binding and Cloud Print SOAP Binding.<br><br>I think the answer should be yes.<br></blockquote></div><div><br></div>Yes, absolutely. The binding documents can then use the name and semantics from the model with the corresponding protocol binding info.<div><br><div> <span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Geneva; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: 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; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Geneva; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; 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; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Monaco; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; 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; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>________________________________________________________________________</div><div>Michael Sweet, Senior Printing System Engineer, PWG Chair</div><div><br></div></div></span><br class="Apple-interchange-newline"></div></span><br class="Apple-interchange-newline"></span><br class="Apple-interchange-newline"> </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>