attachment-0001
<br><font size=2 face="sans-serif">UPDF team... first, congratulations
on UPDF passing. </font>
<br><font size=2 face="sans-serif">I believe it is your team's responsibility,
now, to address the comments received. As there was STRONG OBJECTION, which,
upon review, is substantive in terms of effecting actual adoption, I urge
the UPDF team to make a concerted effort to produce the requested improvements.
</font>
<br><font size=2 face="sans-serif">I know you worked long and hard to get
UPDF across the goal line. The objection received does not appear to be
from someone who disagrees with the specification, rather someone who is
looking for guidance that will encourage adoption. It does not good for
the PWG to pass standards that will not (or cannot readily) be adopted.
</font>
<br><font size=2 face="sans-serif">Hope your team will meet this challenge!</font>
<br><font size=2 face="sans-serif">----------------------------------------------
<br>
Harry Lewis <br>
Chairman - IEEE-ISTO Printer Working Group<br>
http://www.pwg.org<br>
IBM Printing Systems <br>
http://www.ibm.com/printers<br>
303-924-5337<br>
---------------------------------------------- </font>
<br><font size=1 color=#800080 face="sans-serif">----- Forwarded by Harry
Lewis/Boulder/IBM on 06/02/2004 10:52 AM -----</font>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>thrasher@lexmark.com</b>
</font>
<br><font size=1 face="sans-serif">Sent by: owner-pwg-announce@pwg.org</font>
<p><font size=1 face="sans-serif">06/02/2004 07:35 AM</font>
<td width=59%>
<table width=100%>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td valign=top><font size=1 face="sans-serif">pwg-announce@pwg.org</font>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td valign=top>
<tr>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td valign=top><font size=1 face="sans-serif">PWG-ANNOUNCE> PWG ANNOUNCE>
PWG Formal Vote Results for UPDF 1.0</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2><tt>The results of the recently completed PWG Formal Vote
for the UPDF 1.0<br>
Specification are as follows:<br>
<br>
Vote Count:<br>
<br>
Yes: 8<br>
No: 1 (with strong objection)<br>
Abstain: 2<br>
<br>
PWG Process Document Criteria:<br>
<br>
1. Met the 25 percent participation (needed at least 9 votes).<br>
2. Met the 80 percent approval requirement from the No w/ strong objection.<br>
3. Met the 50 percent of votes either yes or no....(needed at least 5)<br>
<br>
UPDF Formal Vote passes.<br>
<br>
Note: There was one additioinal Yes vote that was received after the voting<br>
period closed.<br>
<br>
By the guidelines in the PWG Process Document (both old and new draft),<br>
comments submitted<br>
with a No vote (or No with strong objection) are to be posted and discussed<br>
on the PWG Announce<br>
email list......<br>
<br>
Here are the comments:<br>
<br>
1. The specification does not include examples for each element,<br>
nor does it tie each schema together to show a complete<br>
implementation. See the (many) W3C specifications for
XML and/or<br>
SGML-based formats which *do* include examples.<br>
<br>
2. I do not see a single complete sample file for any printer<br>
device. I see a lot of fragments made by Norbert, but
I don't<br>
see a complete file that could be used as reference against<br>
the spec or schema files that shows the current specification<br>
is useful or feasible for a driver, application, or UI component<br>
to use.<br>
<br>
3. The separation of schemas is confusing and leads me to believe<br>
that a single device description is composed of multiple
XML<br>
files. Given the limited sample fragments on the PWG
FTP<br>
server, it is not clear what the actual organization is supposed<br>
to be. THIS NEEDS TO BE DEFINED in order to allow for
actual<br>
interoperability and network transparency.<br>
<br>
4. My general impression is that the current specification is<br>
not complete enough to be used in an actual printing<br>
environment nor does it provide any advantages over existing<br>
interfaces and formats. Of what use is a new format
if it only<br>
does what every other format does?<br>
<br>
<br>
I will send a separate not when the 51xx.n number is assigned and is<br>
published as a candidate standard.<br>
<br>
Jerry Thrasher<br>
PWG Secretary<br>
<br>
<br>
<br>
</tt></font>