attachment-0001
<br><font size=2 face="sans-serif">I agree... xyz</font>
<br><font size=2 face="sans-serif">----------------------------------------------
<br>
Harry Lewis <br>
IBM Printing Systems <br>
---------------------------------------------- </font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td>
<td><font size=1 face="sans-serif"><b>"McDonald, Ira" <imcdonald@sharplabs.com></b></font>
<br><font size=1 face="sans-serif">Sent by: owner-pwg@pwg.org</font>
<p><font size=1 face="sans-serif">03/11/2003 08:36 AM</font>
<td><font size=1 face="Arial"> </font>
<br><font size=1 face="sans-serif"> To:
"'don@lexmark.com'" <don@lexmark.com>,
Dennis Carney/Boulder/IBM@IBMUS</font>
<br><font size=1 face="sans-serif"> cc:
pwg@pwg.org</font>
<br><font size=1 face="sans-serif"> Subject:
RE: PWG> Process document updated</font></table>
<br>
<br>
<br><font size=2><tt>Hi,<br>
<br>
Rather than introducing "wg" in quotes, I suggest we take up<br>
Dennis' idea of 'xyz' everywhere. Especially because a <br>
Working Group that produces more than one standard needs a<br>
separate acronym for _each_ standard. So sometimes it's<br>
"xyz" (just the working group short name) and sometimes<br>
(in the simple filename) it's "xyzacro" (where "acro"
is<br>
for example "doc" in the "ippdoc" Document Object spec).<br>
<br>
Cheers,<br>
- Ira McDonald<br>
High North Inc<br>
<br>
<br>
-----Original Message-----<br>
From: don@lexmark.com [mailto:don@lexmark.com]<br>
Sent: Tuesday, March 11, 2003 9:28 AM<br>
To: Dennis Carney<br>
Cc: pwg@pwg.org; don@lexmark.com<br>
Subject: Re: PWG> Process document updated<br>
<br>
<br>
<br>
Dennis:<br>
<br>
Yikes... I missed that in Clause 4. We clearly need to use the same
symbol<br>
throughout the document.<br>
<br>
**********************************************<br>
Don Wright don@lexmark.com<br>
<br>
Chair, IEEE SA Standards Board<br>
Member, IEEE-ISTO Board of Directors<br>
f.wright@ieee.org / f.wright@computer.org<br>
<br>
Director, Alliances & Standards<br>
Lexmark International<br>
740 New Circle Rd<br>
Lexington, Ky 40550<br>
859-825-4808 (phone) 603-963-8352 (fax)<br>
**********************************************<br>
<br>
<br>
<br>
Dennis Carney <dcarney@us.ibm.com> on 03/11/2003 10:17:45 AM<br>
<br>
To: pwg@pwg.org<br>
cc: don@lexmark.com<br>
Subject: Re: PWG> Process document updated<br>
<br>
<br>
<br>
<br>
<br>
<br>
In regards to your question 1, it's a bit worse: chapter 4 uses 'xyz'.
I<br>
guess it makes sense to use the same "generic working group abbreviation"<br>
in all places. My personal vote would have been 'xyz', since it is
very<br>
clear that it needs to be replaced with the actual working group<br>
abbreviation. But I don't feel strongly about it. If we *did*
use 'wg',<br>
we could maybe put it in italics wherever it appears to make it clear it
is<br>
a variable that needs to be replaced?<br>
<br>
Dennis<br>
<br>
<br>
<br>
don@lexmark.com<br>
To: Dennis<br>
Carney/Boulder/IBM@IBMUS<br>
03/11/03 08:05 AM cc:
pwg@pwg.org<br>
Subject: Re: PWG> Process<br>
document updated<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
A question and a thought:<br>
<br>
1) Why in Clause 6 do we use "wg" as a stand-in for the working
group's<br>
acronym and in Clause 8, we seem to use "xxx"??<br>
<br>
2) In regards to issue 4, I think we should require LOAs to be in place<br>
before a document progresses to "Candidate Standard."<br>
<br>
**********************************************<br>
Don Wright don@lexmark.com<br>
<br>
Chair, IEEE SA Standards Board<br>
Member, IEEE-ISTO Board of Directors<br>
f.wright@ieee.org / f.wright@computer.org<br>
<br>
Director, Alliances & Standards<br>
Lexmark International<br>
740 New Circle Rd<br>
Lexington, Ky 40550<br>
859-825-4808 (phone) 603-963-8352 (fax)<br>
**********************************************<br>
<br>
<br>
<br>
<br>
Dennis Carney <dcarney@us.ibm.com>@pwg.org on 03/10/2003 07:21:59
PM<br>
<br>
Sent by: owner-pwg@pwg.org<br>
<br>
<br>
To: pwg@pwg.org<br>
cc:<br>
Subject: PWG> Process document updated<br>
<br>
<br>
<br>
<br>
<br>
<br>
I have updated the PWG Process document with the changes discussed at the<br>
SM telecon last Thursday. The changes resolved issues 1-6 in the
prior<br>
version. Issues 7-8 had to do with the LOA in the Intellectual Property<br>
chapter, and we didn't resolve those during the telecon, so I made no<br>
changes for those in this version.<br>
<br>
I added two new issues, having to do with the maturity version.<br>
<br>
I believe that this document is going to be discussed at the SM telecon<br>
this Thursday, March 13.<br>
<br>
ftp://ftp.pwg.org/pub/pwg/general/process/pwg-process20-20030310.doc<br>
ftp://ftp.pwg.org/pub/pwg/general/process/pwg-process20-20030310.pdf<br>
ftp://ftp.pwg.org/pub/pwg/general/process/pwg-process20-20030310-rev.doc<br>
ftp://ftp.pwg.org/pub/pwg/general/process/pwg-process20-20030310-rev.pdf<br>
<br>
Dennis Carney<br>
IBM Printing Systems<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
</tt></font>
<br>