THE PUBLICATION POLICY
	    http://dies.cs.utwente.nl/publications/policy/
			version 2. 01.10.2004
			  by Pieter & Sandro

1. MOTIVATION

This policy addresses the following needs:

1) When submitting/publishing a paper, it is in everyone's interest to
make it available online at a stable link, in fact:

a. Papers that are electronically available are cited more often.

b. Self archiving will eventually become the norm. (See S. Harnad,
On-line journals and financial fire-walls, Nature 395:127-128,
Sep. 1998, http://www.ecs.soton.ac.uk/~harnad/nature.html)

c. You can refer to the paper in research proposals.

d. You claim your ideas early.

2) At the same time, you want to be able to revise and update your
online papers (e.g. after receiving referee reports). People refer to
what they can download from your homepage, and not to what they see in
some proceedings. It is very annoying to be confronted with old
versions of papers years after you have improved it.

3) Many times per year, the management needs to produce the list of
publications of a certain group on a certain topic (e.g. for
OZI). This information should be available for everyone at all
times. (You don't want managers to run after you asking what have you
been publishing).

2. THE POLICY

When submitting a paper to a conference or journal, please also 

     1) Post it on the Computing Research Repository (CoRR) at
     http://xxx.lanl.gov/archive/cs/intro.html (the first time, this
     requires registering etc). Note the address at which it is posted
     (e.g. http://xxx.lanl.gov/abs/cs/0101023). NB: CoRR is sponsored
     by the ACM. 

     2) Make a technical report version by adding at the end of the
     abstract the line "the most up-to-date version of this paper can
     be downloaded at ... (CoRR address here)", and send it
     immediately to the CTIT secretary (currently Anja Tanke,
     tanke@ctit.utwente.nl), asking her to turn your paper into a CTIT
     technical report.

     3) Send to Pieter the coordinates of both the technical report
     and the CoRR address.

When revising a paper (like after referee reports), please re-post it
to CoRR, adding at the end of the abstract a line as follows:

"Revision history: version $NUMBER, date $DATE, $COMMENTs"

where: 

- $N is the revision number (if this is the first revision, then $N =
2).

- $DATE is the date of the revision

- $COMMENTS, contains anything that can facilitate the
reader. E.g. "identical to the version in the proceedings of SAS04"
"corrected typos", or "this time with a proof that does work".