attachment-0001
Hi Harry,<br><br>Thanks for the comments - my replies are inline below.<br><br>Cheers,<br>- Ira<br><br clear="all">Ira McDonald (Musician / Software Architect)<br>Chair - Linux Foundation Open Printing WG<br>Blue Roof Music/High North Inc<br>
email: <a href="mailto:blueroofmusic@gmail.com">blueroofmusic@gmail.com</a><br>winter:<br> 579 Park Place Saline, MI 48176<br> 734-944-0094<br>summer:<br> PO Box 221 Grand Marais, MI 49839<br> 906-494-2434<br>
<br><br><div class="gmail_quote">On Mon, May 11, 2009 at 4:44 PM, Harry Lewis <span dir="ltr"><<a href="mailto:harry.lewis@infoprint.com">harry.lewis@infoprint.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br><font size="2" face="sans-serif">Ira, great start! Couple observations.</font>
<br>
<br><font size="2" face="sans-serif">1. As written, adding or changing power
state definitions is out of scope. Should the objectives include "interpretation"
or mapping of defined power states as they relate to imaging devices? </font>
<br><font size="2" face="sans-serif"> - For example - are we going
to standardize which "power level" relates to fuser or scanner
lamp readiness etc?</font>
</blockquote><div><br><ira><br>My two cents.<br><br>There was strong concensus at the last two face-to-face BOFs<br>NOT to allow any but standard (CIM/ACPI) or vendor-defined <br>power states - no site-defined power states - however, each<br>
power state should have an attribute for power consumption <br>(in watts) - ACPI and CIM do NOT manage the absolute<br>power level - they manage a *small* set of standard power<br>states.<br><br>Therefore, the power *state* that relates to fuser or scanner<br>
lamp readiness is in-scope for WIMS Power, but the exact <br>power consumption should NOT be changeable by the site.<br><br>Site-defined Power Policy (when to go to sleep after idle<br>or a time-of-day) that can be changed is in-scope.<br>
</ira><br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<br><font size="2" face="sans-serif">2. Should the subtask have its own reflector?
(we can't pass up the opportunity for <a href="mailto:POW@PWG.ORG" target="_blank">POW@PWG.ORG</a>!)</font>
<br>
</blockquote><div><br><ira><br>No - we should continue to use the single WIMS reflector<br>(as we have done for 4 years for CIM without problems).<br></ira><br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br><font size="2" face="sans-serif">Regards,</font>
<br><font size="2" face="sans-serif">Harry<br>
</font><font size="1" face="Arial"><b><br>
Harry Lewis</b></font><font color="#808080" size="1" face="Arial"><br>
Program Manager - Intellectual Property & Open Standards<br>
Phone: 720-663-3456<br>
e-mail: <a href="mailto:harry.lewis@infoprint.com" target="_blank">harry.lewis@infoprint.com</a></font><font color="blue" size="1" face="Arial"><br>
</font><a href="http://www.infoprint.com/" target="_blank"><font color="blue" size="1" face="Arial">infoprint.com</font></a><font size="3"><br>
<br>
</font><img src="cid:_1_02EB49A002EB1B600071EED0872575B3"><font color="#3f621f" size="3" face="Webdings"><br>
P</font><font size="3"> </font><font color="#3f621f" size="1" face="Arial">Think
before you print</font><font size="3"> </font>
<br>
<br>
<br>
<table width="100%">
<tbody><tr valign="top">
<td width="40%"><font size="1" face="sans-serif"><b>Ira McDonald <<a href="mailto:blueroofmusic@gmail.com" target="_blank">blueroofmusic@gmail.com</a>></b>
</font>
<br><font size="1" face="sans-serif">Sent by: <a href="mailto:wims-bounces@pwg.org" target="_blank">wims-bounces@pwg.org</a></font>
<p><font size="1" face="sans-serif">05/11/2009 12:54 PM</font>
</p></td><td width="59%">
<table width="100%">
<tbody><tr valign="top">
<td>
<div align="right"><font size="1" face="sans-serif">To</font></div>
</td><td><font size="1" face="sans-serif"><a href="mailto:wims@pwg.org" target="_blank">wims@pwg.org</a>, William Wagner <<a href="mailto:wamwagner@comcast.net" target="_blank">wamwagner@comcast.net</a>>,
Ira McDonald <<a href="mailto:blueroofmusic@gmail.com" target="_blank">blueroofmusic@gmail.com</a>></font>
</td></tr><tr valign="top">
<td>
<div align="right"><font size="1" face="sans-serif">cc</font></div>
</td><td>
</td></tr><tr valign="top">
<td>
<div align="right"><font size="1" face="sans-serif">Subject</font></div>
</td><td><font size="1" face="sans-serif">[WIMS] Draft of Charter of WIMS Power
Mgmt Project</font></td></tr></tbody></table>
<br>
<table>
<tbody><tr valign="top">
<td>
</td><td></td></tr></tbody></table>
<br></td></tr></tbody></table><div><div></div><div class="h5">
<br>
<br>
<br><font size="3">Hi Bill,<br>
<br>
Attempting to more constructively help out...<br>
<br>
I just posted a draft of a charter for WIMS Power Mgmt Project:<br>
<br>
</font><a href="ftp://ftp.pwg.org/pub/pwg/wims/wd/wd-wimspower-charter-20090511.htm" target="_blank"><font color="blue" size="3"><u>ftp://ftp.pwg.org/pub/pwg/wims/wd/wd-wimspower-charter-20090511.htm</u></font></a><font size="3"><br>
<br>
I followed the format approved by the PWG in IPP PSX project<br>
and more recently the MFD WG (basically the same idea).<br>
Especially, it includes a specific Out-Of-Scope section.<br>
<br>
Please add a brief Problem Statement (replace <tbd>).<br>
<br>
The Milestones during Definition Phase (Initial draft, Prototype<br>
draft, and PWG Last Call for each of Model and Binding specs) <br>
are the ones the PWG Steering Committee agreed on for MFD <br>
- the SC specifically do not want a milestone such as 'PWG CS',<br>
because a WG can't project that.<br>
<br>
Comments?<br>
<br>
Cheers,<br>
- Ira<br>
<br>
Ira McDonald (Musician / Software Architect)<br>
Chair - Linux Foundation Open Printing WG<br>
Blue Roof Music/High North Inc<br>
email: </font><a href="mailto:blueroofmusic@gmail.com" target="_blank"><font color="blue" size="3"><u>blueroofmusic@gmail.com</u></font></a></div></div><font size="3"><div><div></div><div class="h5"><br>
winter:<br>
579 Park Place Saline, MI 48176<br>
734-944-0094<br>
summer:<br>
PO Box 221 Grand Marais, MI 49839<br>
906-494-2434<br>
<br></div></div>
-- <br>
This message has been scanned for viruses and <br>
dangerous content by </font><a href="http://www.mailscanner.info/" target="_blank"><font color="blue" size="3"><b><u>MailScanner</u></b></font></a><font size="3">,
and is <br>
believed to be clean. </font><tt><font size="2">_______________________________________________<br>
wims mailing list<br>
<a href="mailto:wims@pwg.org" target="_blank">wims@pwg.org</a><br>
<a href="https://www.pwg.org/mailman/listinfo/wims" target="_blank">https://www.pwg.org/mailman/listinfo/wims</a><br>
</font></tt>
<br>
<br>
_____________________________________________________________________________<br>
"This message and any attachments are solely for the intended recipient and may contain confidential or privileged information. If you are not the intended recipient, any disclosure, copying, use, or distribution of the information included in this message and any attachments is prohibited. If you have received this communication in error, please notify us by reply e-mail and immediately and permanently delete this message and any attachments. Thank you." _____________________________________________________________________________<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.