attachment-0001
<br><font size=2 face="sans-serif">While I support the endeavor to stabilize
the ISTO Template, I want to make it clear that documents currently in
last call should not have their horizon modified for lack of adherence
to the ultimate template. If the authors do have time to update to the
latest template... fine. </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>"Hastings, Tom N" <hastings@cp10.es.xerox.com></b></font>
<br><font size=1 face="sans-serif">Sent by: owner-sm@pwg.org</font>
<p><font size=1 face="sans-serif">01/29/2003 03:19 PM</font>
<td><font size=1 face="Arial"> </font>
<br><font size=1 face="sans-serif"> To:
pwg@pwg.org</font>
<br><font size=1 face="sans-serif"> cc:
sm@pwg.org</font>
<br><font size=1 face="sans-serif"> Subject:
SM> Strawman for a PWG IEEE-ISTO
Template for PWG Proposed Standards</font></table>
<br>
<br>
<br><font size=2><tt>In case there is time at the end of the SM telecon
tomorrow, Thursday, Jan<br>
30, 1-2 PM EST (10-11 PST) after we discuss the PWG Process, here is a<br>
Strawman for a PWG IEEE-ISTO Template for PWG Proposed Standards.<br>
<br>
This is a one-time notification to both reflectors. Further on-line<br>
discussion of the PWG Template with occur ONLY on pwg@pwg.org, NOT on the<br>
sm@pwg.org (same as for any other PWG process discussion). <br>
<br>
Dennis Carney, Ira McDonald, Ron Bergman, and I have been working on an<br>
MS-WORD template for PWG IEEE-ISTO standards for use by all the PWG WGs<br>
doing IEEE-ISTO standards. Here is version 0.2 as a strawman. <br>
<br>
ftp://ftp.pwg.org/pub/pwg/general/templates/pwg-template-for-standards-lates<br>
t.pdf<br>
ftp://ftp.pwg.org/pub/pwg/general/templates/pwg-template-for-standards-lates<br>
t.doc<br>
ftp://ftp.pwg.org/pub/pwg/general/templates/pwg-template-for-standards-v02-0<br>
30127.pdf<br>
ftp://ftp.pwg.org/pub/pwg/general/templates/pwg-template-for-standards-v02-0<br>
30127.pdf<br>
<br>
Ira and I made some simplifications in it as part of making version 0.2
over<br>
the IEEE-ISTO style as documents below in Appendix C which also described<br>
why we made each change. Ira and I haven't had a chance to talk to
anyone<br>
else about many of these simplifications. <br>
<br>
ISSUE: So an imporant issue is whether these simplifications are
OK or do<br>
we need to rigorously follow the IEEE-ISTO standard style? <br>
<br>
The rest of version 0.2 is incorporating the detailed commens that Dennis<br>
Carney had made as a result of trying to use a template while he wrote
up<br>
his "-actuals" IPP specification. <br>
<br>
There is a companion document: "Tips for Good Technical Writing"
which I<br>
moved from the Appendix to a separate document available at:<br>
ftp://ftp.pwg.org/pub/pwg/general/templates/good-writing-tips-latest.pdf<br>
ftp://ftp.pwg.org/pub/pwg/general/templates/good-writing-tips-latest.doc<br>
ftp://ftp.pwg.org/pub/pwg/general/templates/pwg-template-for-standards-v02-0<br>
30127.pdf<br>
ftp://ftp.pwg.org/pub/pwg/general/templates/pwg-template-for-standards-v02-0<br>
30127.pdf<br>
<br>
Please send comments.<br>
<br>
Thanks,<br>
Tom<br>
<br>
<br>
Appendix C
Differences between this Template and the IEEE-ISTO standard<br>
style<br>
This Appendix lists the differences between this Template and the IEEE/ISTO<br>
standard style and explains why. The IEEE-ISTO standard style is<br>
represented in the IEEE/ISTO 5101.1 Media Name Standard. These differences<br>
have evolved after experience using the IEEE/ISTO standard style for online<br>
viewing and printing with Adobe Acrobat. The differences are (working
top<br>
to bottom):<br>
1.
Merged the redundant second page (which had the Abstract)<br>
onto the first page and got rid of the second page. Our understanding
is<br>
that having two title pages comes from publishing the document in printed<br>
form, where the first page is like a cover. Most standards bodies
have<br>
eliminated the cover so that the Abstract appears on the first page.<br>
2.
Added "(PWG)" after "The Printer Working Group" in
the<br>
title.<br>
3.
Removed the redundant indications of whether this version is<br>
a Working Draft, a Proposed Standard, a Draft Standard, or a Standard from<br>
the Header. Only the title indicates the status. A Working
Draft has:<br>
"Working Draft for a PWG Proposed Standard". A Proposed
Standard after<br>
passing WG Last Call will have: "PWG Proposed Standard". A
Draft Standard<br>
after passing WG Last Call will have: "PWG Draft Standard". A
Standard<br>
after passing PWG Last Call will have: "PWG Standard"<br>
4.
Added the URL for the document on the first page, so that it<br>
is easy to find.<br>
5.
Added Editor's name(s) to the first page, so that proper<br>
credit is given as is common in some standards bodies.<br>
6.
Simplified the headers and footers, so that the headers are<br>
all the same except for the first page. Keeping the headers and footers<br>
simple will reduce errors in producing drafts and allow editor's to focus
on<br>
content more and format less. <br>
7.
The Left side of the Header is blank for Working Drafts,<br>
then gets IEEE-ISTO 51nn.n after the Working Draft passes WG Last Call.<br>
Thus the editor only changes the Header once, when the specification passes<br>
Last Call. <br>
8.
In the Header, the Title is centered with most of the fixed<br>
parts removed.<br>
9.
In the Header, the page number is always on the right. The<br>
IEEE-ISTO format did not have the page number on the top at all, which
has<br>
proved a problem when viewing the specification with Adobe Acrobat, when
the<br>
user can only see part of the page at one time. Also scrolling upwards
and<br>
downwards needs the page numbers to be at the top and bottom. <br>
10.
The Footer follows the IEEE-ISTO style, except the page<br>
number is always centered, instead of alternating left and right. This<br>
makes it easier to spot the page number when viewing it on the screen.<br>
11.
Page numbers in the Header and Footer, start at 1 with the<br>
first page. No Roman numerals are used. This makes it easier
to relate<br>
pages as numbered by Adobe Acrobat and those printing on each page and
in<br>
the Table of Contents. Also when printing out selected pages, the
page<br>
number used by the Printer driver agree with the printed page numbers.<br>
12.
Defined the Body Text style to use ragged right, rather than<br>
justified, in order to make the document more readable by people when<br>
printed or displayed though it may not look as pretty.<br>
13.
Added editor names for PWG standards in the References<br>
section, as is practice in some standards bodies and most technical<br>
publications.<br>
14.
Removed the first initials from references and used only<br>
family names as is becoming practice to avoid the cultural confusion about<br>
whether family names come first or last.<br>
<br>
Here is the change log:<br>
Changes to make version 0.2, January 27, 2003<br>
The following changes were made to create version 0.2, January 27, 2003<br>
after careful review by Dennis Carney and Ira McDonald:<br>
1.
Generalized the template so that it can be for any PWG<br>
standard, not just IPP.<br>
2.
Simplified the template so that as few fields as possible<br>
have to be updated as the specification progresses through the process
-<br>
otherwise everyone does it differently.<br>
3.
Follow the IEEE-ISTO style with the exceptions listed in<br>
Appendix C derived from experience viewing and printing on-line versions<br>
using Adobe Acrobat.<br>
4.
Explained the file naming scheme for PWG WGs.<br>
5.
Added the requirements for a Logical Diagram and a<br>
Configuration Diagrams and showed some IPP examples.<br>
6.
Highlighted IPP specific instructions and examples in green,<br>
like this, in order to give real examples, but make the Template work for<br>
all PWG Working Groups<br>
7.
Added RFC 3380, 3381, 3382.<br>
8.
Added a number of terms that may be useful to PWG projects<br>
other than IPP.<br>
9.
Moved the Appendix "Tips for Good Technical Writing" to a<br>
separate document available at:<br>
ftp://ftp.pwg.org/pub/pwg/general/templates/good-writing-tips-latest.pdf<br>
<br>
<br>
</tt></font>
<br>