attachment
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2722.900" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=610294619-26032003><FONT face=Arial color=#0000ff
size=2>Harry,</FONT></SPAN></DIV>
<DIV><SPAN class=610294619-26032003><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=610294619-26032003><FONT face=Arial color=#0000ff size=2>Not
intending to "churn" , but Gail's question (and my poorly phrased one) of what
is the criteria by which the companies of some significant members of the group
ban travel is a necessary consideration for the next meeting. As you
know, setting up and then canceling a meeting is a lot of wasted effort (and
money) for you and for the rest of us. We would want to have some confidence
that members will be able to come. Of course, we may not know what the criteria
are. But if they are distance or location limitations, that may help
assure a good pick. If it is the fact that there is military action or a
high terrorist code, that may well go on for quite a long
time.</FONT></SPAN></DIV>
<DIV><SPAN class=610294619-26032003><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=610294619-26032003><FONT face=Arial color=#0000ff size=2>Bill
Wagner</FONT></SPAN></DIV>
<BLOCKQUOTE>
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B> Harry Lewis
[mailto:harryl@us.ibm.com]<BR><B>Sent:</B> Wednesday, March 26, 2003 2:44
PM<BR><B>To:</B> thrasher@lexmark.com<BR><B>Cc:</B>
pwg@pwg.org<BR><B>Subject:</B> Re: PWG> RE: PWG-ANNOUNCE> Rearranging
PWG schedule<BR><BR></FONT></DIV><BR><FONT face=sans-serif size=2>We can try
(to nail the next meeting quickly). This is why I posted the scheduling guide.
For those who need to reschedule flights to avoid penalty... my suggestion is
to book into Provo in October. I don't believe rescheduling the entire year is
feasible. </FONT><BR><BR><FONT face=sans-serif size=2>If we churn on this
(which it looks like we are) ... some people will be hosed. </FONT><BR><FONT
face=sans-serif size=2>----------------------------------------------<BR>Harry
Lewis <BR>IBM Printing Systems
<BR>---------------------------------------------- </FONT><BR><BR><BR>
<TABLE width="100%">
<TBODY>
<TR vAlign=top>
<TD>
<TD><FONT face=sans-serif size=1><B>thrasher@lexmark.com</B></FONT>
<BR><FONT face=sans-serif size=1>Sent by: owner-pwg@pwg.org</FONT>
<P><FONT face=sans-serif size=1>03/26/2003 12:02 PM</FONT> </P>
<TD><FONT face=Arial size=1> </FONT><BR><FONT
face=sans-serif size=1> To:
pwg@pwg.org</FONT> <BR><FONT face=sans-serif size=1>
cc: </FONT> <BR><FONT
face=sans-serif size=1> Subject:
Re: PWG> RE: PWG-ANNOUNCE> Rearranging PWG
schedule</FONT></TR></TBODY></TABLE><BR><BR><BR><BR><FONT size=2><TT>Since
there are time constraints for the near term, can we just get the<BR>very next
F2F meeting scheduled<BR>ASAP and look at further re-arrangements at that
F2F...????<BR></TT></FONT><BR><FONT size=2><TT>For me...using keywords instead
of numbers.......:)<BR></TT></FONT><BR><FONT size=2><TT>June 2-6
(preferable)<BR>June 16-20 (acceptable)<BR></TT></FONT><BR><FONT
size=2><TT>Location options (no preference)... for either
week.<BR></TT></FONT><BR><FONT size=2><TT>JT<BR></TT></FONT><BR><BR><BR><FONT
size=2><TT>"Farrell, Lee" <Lee.Farrell@cda.canon.com>@pwg.org on
03/26/2003 01:54:34<BR>PM<BR></TT></FONT><BR><FONT size=2><TT>Sent by:
owner-pwg@pwg.org<BR></TT></FONT><BR><BR><FONT size=2><TT>To:
"Harry Lewis" <harryl@us.ibm.com>,
<pwg@pwg.org><BR>cc:<BR>Subject: PWG> RE:
PWG-ANNOUNCE> Rearranging PWG schedule<BR></TT></FONT><BR><BR><FONT
size=2><TT>Harry,<BR></TT></FONT><BR><FONT size=2><TT>What's the fundamental
goal here? To revisit the schedule for all future<BR>meetings in the
year, or just up to (but not including) October?<BR></TT></FONT><BR><FONT
size=2><TT>Is there any reason not to try to "squeeze in" four [newly
scheduled]<BR>meetings into the remainder of the year? [For example,
June 2-6, August<BR>4-9, October 6-10 (why not still hold this in New York?),
and December 1-5<BR>seem reasonable goals for future meetings. Eight
week separation on<BR>average, but still allowing four face-to-face meetings
for the rest of the<BR>year.<BR></TT></FONT><BR><FONT size=2><TT>Given that
this organization has already cut down this year's schedule of<BR>meetings to
only five, I would think that we should avoid reducing it to<BR>four if we
can.<BR></TT></FONT><BR><FONT size=2><TT>Any
thoughts?<BR></TT></FONT><BR><FONT
size=2><TT>lee<BR>===========================<BR>Lee Farrell<BR>Canon
Development Americas<BR>110 Innovation Drive<BR>Irvine, CA
92612<BR>(949) 856-7163 - voice<BR>(949) 856-7510 -
fax<BR>lee.farrell@cda.canon.com<BR>===========================<BR></TT></FONT><BR><FONT
size=2><TT>-----Original Message-----<BR>From: Harry Lewis
[mailto:harryl@us.ibm.com]<BR>Sent: Wednesday, March 26, 2003 10:29 AM<BR>To:
pwg-announce@pwg.org<BR>Subject: PWG-ANNOUNCE> Rearranging PWG
schedule<BR></TT></FONT><BR><BR><BR><FONT size=2><TT>To recover from
cancelation of D.C. I've prepared a scheduling
guide.<BR><ftp://ftp.pwg.org/pub/pwg/general/misc/DCRecovery.pdf><BR>ftp://ftp.pwg.org/pub/pwg/general/misc/DCRecovery.pdf</TT></FONT>
<BR><BR><FONT size=2><TT>As you can see, two weeks in June appear to be the
best alternatives.<BR>Please identify any conflicts / alignments I have
missed. We need to settle<BR>on the next meeting date quickly so people can
reschedule their canceled<BR>flights. People flying AA seem to have the
shortest amount of time and we<BR>may not be able to reschedule within their 2
day deadline! In this case I<BR>recommend these people reschedule for the
Provo meeting in October.<BR></TT></FONT><BR><FONT size=2><TT>PLEASE HOLD
DISCUSSION OF THIS TOPIC ON pwg@pwg.org NOT
pwg-announce!<BR></TT></FONT><BR><FONT
size=2><TT>----------------------------------------------<BR>Harry
Lewis<BR>Chairman - ISTO Printer Working Group<BR>IBM Printing
Systems<BR>----------------------------------------------<BR>(See attached
file: C.htm)<BR></TT></FONT><BR><BR><BR><BR><BR><FONT face=sans-serif
size=2>#### C.htm has been removed from this note on March 26, 2003 by Harry
Lewis</FONT> <BR></BLOCKQUOTE></BODY></HTML>