attachment

Hi Bill and Mike,<br><br>I also agree on all points.<br><br>The ultimately broad scenario (one for all Print) doesn't really<br>work well, IMHO.<br><br>Cheers,<br>- Ira<br><br clear="all"><div class="gmail_quote">On Jun 20, 2011 at 2:38 AM, Michael Sweet <span dir="ltr"><<a href="mailto:msweet@apple.com">msweet@apple.com</a>></span> wrote:<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><div>On Jun 15, 2011, at 12:22 PM, William Wagner wrote:</div><blockquote type="cite"> <span style="border-collapse:separate;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"><div link="blue" vlink="purple" lang="EN-US"> <div><div style="margin-top:0in;margin-right:0in;margin-left:0in;margin-bottom:0.0001pt"><u></u><font color="#000000">...</font><font color="#1f497d" face="Calibri, sans-serif" size="5">�</font><u></u></div><div class="im"> <div style="margin-top:0in;margin-right:0in;margin-left:0in;margin-bottom:0.0001pt;font-size:12pt;font-family:'Times New Roman', serif"><span style="font-size:14pt;font-family:Calibri, sans-serif;color:rgb(31, 73, 125)">In short,� I suggest:<u></u><u></u></span></div> <div style="margin-top:0in;margin-right:0in;margin-left:0.75in;margin-bottom:0.0001pt;font-size:12pt;font-family:'Times New Roman', serif"><span style="font-size:14pt;font-family:Calibri, sans-serif;color:rgb(31, 73, 125)"><span>1.<span>��<span>�</span></span></span></span><span style="font-size:14pt;font-family:Calibri, sans-serif;color:rgb(31, 73, 125)">Our terminology be not inconsistent with typical design terminology<u></u><u></u></span></div> <div style="margin-top:0in;margin-right:0in;margin-left:0.75in;margin-bottom:0.0001pt;font-size:12pt;font-family:'Times New Roman', serif"><span style="font-size:14pt;font-family:Calibri, sans-serif;color:rgb(31, 73, 125)"><span>2.<span>��<span>�</span></span></span></span><span style="font-size:14pt;font-family:Calibri, sans-serif;color:rgb(31, 73, 125)">We define our approach and terminology in the �Best Practices� document<u></u><u></u></span></div> <div style="margin-top:0in;margin-right:0in;margin-left:0.75in;margin-bottom:0.0001pt;font-size:12pt;font-family:'Times New Roman', serif"><span style="font-size:14pt;font-family:Calibri, sans-serif;color:rgb(31, 73, 125)"><span>3.<span>��<span>�</span></span></span></span><span style="font-size:14pt;font-family:Calibri, sans-serif;color:rgb(31, 73, 125)">We be consistent in terminology and level within the �Best� Practices� document and among the various projects (It would be very confusing to have a Use Case in one document become a Scenario in another.)<u></u><u></u></span></div> <div style="margin-top:0in;margin-right:0in;margin-left:0.75in;margin-bottom:0.0001pt;font-size:12pt;font-family:'Times New Roman', serif"><span style="font-size:14pt;font-family:Calibri, sans-serif;color:rgb(31, 73, 125)"><span>4.<span>��<span>�</span></span></span></span><span style="font-size:14pt;font-family:Calibri, sans-serif;color:rgb(31, 73, 125)">We not lose the �story� aspect and the �sequence of what the user does and what the �system� must do� Joe is on vacation at Yellowstone and needs to print out the map to a lost gold mine in Wyoming that his friend in New York City just found. Perhaps the story is farfetched, but it includes many aspects of the general problem that must be considered.<u></u><u></u></span></div> </div></div></div></span></blockquote><br></div><div>I agree on all points.</div><br><div> <span style="border-collapse:separate;color:rgb(0, 0, 0);font-family:Helvetica;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;font-size:medium"><div> ________________________________________________________________________<br>Michael Sweet, Senior Printing System Engineer, PWG Chair<br></div></span> </div><div class="im"> <br><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> cloud mailing list<br> <a href="mailto:cloud@pwg.org">cloud@pwg.org</a><br> <a href="https://www.pwg.org/mailman/listinfo/cloud" target="_blank">https://www.pwg.org/mailman/listinfo/cloud</a><br> <br></blockquote></div><br><div style="visibility: hidden; left: -5000px;" id="avg_ls_inline_popup"></div><style type="text/css">#avg_ls_inline_popup{position: absolute;z-index: 9999;padding: 0px 0px;margin-left: 0px;margin-top: 0px;overflow: hidden;word-wrap: break-word;color: black;font-size: 10px;text-align: left;line-height: 130%;}</style> <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.