Being freely accessible does not mean 'public domain', however. All material
remains copyrighted.
The standard phrase defining the rights for readers of individual papers in
a proceedings volume is
"Copyright © XXXX for the individual papers by the
papers' authors. Copying permitted for private and
academic purposes. Re-publication of material from this
volume requires permission by the copyright
owners."
where XXXX is the year of publication. This phrase tells readers
of your proceedings volumes the conditions under which they can
download individual papers (resp. material contained in your volume).
Make sure that the rights you obtained from the paper
authors are compatible with this phrase! You can also negotiate with us an adaption
of the phrase. Be aware that CEUR-WS.org has no obligation to track copyrights
violators. We, i.e. the manager of CEUR-WS.org and the organization that hosts CEUR-WS.org,
take no responsibility for any damage caused by the publication of your proceedings volume.
See
disclaimer for more details. You are the publisher of your own proceedings volume,
CEUR-WS.org is just a publication tool.
Formally, CEUR-WS.org (and the editorial board of Sun SITE Central Europe) is not obliged to store any submitted material on the server. In practice however, we are committed to provide this service for a virtually unlimited time. The published material must be scientific or serve academic purposes. It may not contain indecent parts or parts violating human rights. Commercial advertisements should be avoided. Better put them on the home page of your workshop.
From the year 2008 onwards, we impose a soft restriction on the number of papers per proceedings volume. A normal volume should have at least five papers. If your proceedings volume has less papers, you should contact CEUR-WS.org in advance to get the volume published.
View the files as ASCII text rather than as HTML code. Your file index.html must at least contain the title of the material and the names/addresses of the editors (normally identical to the publishers). It must use the style sheet http://ceur-ws.org/ceur-ws.css which defines some common layout for proceedings volumes. It may not contain or start executable code such as Java, Javascript, Active-X or any other type of executable code. Neither may it contain cookie definitions nor invisible pixels and the like. You can check the consistency/completeness of the submission directory by accessing it locally with your Web browser. Please do not use a Web page editor to produce index.html but rather a simple text editor like 'vi' or 'notepad'. Web page editors including MS-Office-WinWord tend to produce unreadable HTML code which we want to avoid in CEUR-WS.org. The FONT command should not be used unless for exceptional cases like a footnote or an acknowledgement. Special characters like umlauts and accents should be encoded in HTML by their command form, e.g ä for ä. Using 8-bit ASCII codes for such characters is likely to cause problems. Please be careful in the preparation of the file index.html. Delays in publishing a volume are mostly due to errors in that file. The management of CEUR-WS.org reserves the right for adapting the file index.html to accomodate the common style of CEUR-WS.org and to include volume numbers and similar meta information.
The technical papers in the proceedings should be in one of the following formats (ordered by preference):
HREF="paper1.pdf"rather than absolute
HREF="http://www.dept.org/paper1.pdf".
Paper files and other items should be put in the main directory rather than sub-directories of the submission directory. This allows short URLs to the citable items of a published proceedings volume. An exception to this general rule are back links to workshop home pages and home pages of scientific institutions (or research labs) sponsoring the workshop. Moreover, back links to editor and author home pages are welcome. Please note however that such absolute links can and will become dangling when people change their affiliation! That's also a reason why putting the proceedings online at CEUR-WS.org is probably a better idea than putting it on your home page.
We advise proceedings editors to include a link to their workshop web page in their index file of their CEUR-WS volume. This allows readers to easily locate further information about the workshop such as the call for papers. We also recommend to include a back link from the workshop page to the CEUR-WS volume.
\usepackage{times,latexsym} % use Postscript font instead of TeX times and math fonts
If you are using the older version LaTeX 2.09, then the Postscript
fonts have to be configured in the first line, e.g.
\documentstyle[times,latexsym]{article}
Note that some LaTeX installations do not include Postscript fonts.
Then you cannot use the above optimizations for PDF.
Other text processors like StarWriter and MS-Word produce
Postscript files that can be converted to readable PDF without
the abovementioned font problem.
One way is to deal with page numbers is to assign them local per paper, e.g. paper 1 has pages 1.1 to 1.14, paper 2 has pages 2.1 to 2.15, and so forth. An example is shown in Vol-19. You should in this case inform the author about their paper number so that they can produce the right page numbering of their final paper version.
If you want to supply absolute page numbers, then you need to produce an integrated proceedings document like for example in Vol-62 and include the page numbers from the integrated proceedings document. Absolute page numbers are preferable but they also require much more work on your side.
Most volumes in CEUR-WS.org have no data about page numbers. So, providing them is an extra service. We have no specific knowledge about suitable tools to change page numbers or merge multiple pdf files into a single one. You might want to try Pdftk, Adobe Acrobat or CutePdf.
If you want to merge several pdf files into one and create a table of contents for the merged document, you may want to use the LaTeX macro definitions by Daniel A. Sadilek, originally used for producing the aggregated proccedings file Vol-324/dsml08.pdf.
zip -r sub_file.zip dir_namewhere "sub_file.zip" is the name of the submission file and "dir_name" is the name of the submission directory. For example, the command
zip -r IBDD96.zip IBDD96creates a submission file for the material contained in the directory IBDD96. Use meaningful names for the submission file, e.g. the acronym of the workshop. Under Windows, you can use packers like WinZIP, PKZIP or similar to produce the submission file. But beware: use ISO-standard file names! In particular, blank characters in file names are not allowed. Under Unix, you may also use the 'tar/gzip' commands to create the submission directory. Make sure that the submission file expands to a directory and not to files in the current directory. Subsequently, the procedures PUT (submit a proceedings volume to be published on CEUR-WS.org) and DELETE (remove a published volume) are explained. These two procedures shall be executed by one of the proceedings editors., i.e. by you. You should in particular sign the corresponding fax, and you should be the person mentioned in the clause "submitted by ..." at the end of the index file of the volume. If you are one of the editors but the technical upload is done by a person who is not one of the editors, then you should use the clause "submitted by your name, other name" in the index file.
Step 3 (sending the PUT-FAX) should be executed before step 4! If you do not have access to a fax machine, you may send the signed PUT-FAX via postal mail and send a scanned image via email to shortcut the transport time of the postal mail. The PUT-FAX has no direct legal role for us. It just indicates us that you are aware of copyright issues. If the material is accepted by us you will receive a notification with the bibliographic reference of the material.
Some proceedings editors would like to get a CEUR-WS volume number assigned to their workshop in advance to the publication at CEUR-WS, for example to announce it on the workshop web site or to include the URL of the proceedings volume in the impressum of the proceedings. To do so, just contact the manager of this site via email (see end of this page) and specify a deadline until which the proceedings volume will be uploaded. It is not a requirement to ask in advance for a volume number. Neither do we recommend to ask for a volume number in advance. The standard procedure is that we assign the next free volume number to your proceedings as soon as you upload the submission file and send the accompanying PUT FAX.
The actual date of execution of PUT/DELETE is subject to local maintenance policy of SunSITE.Informatik.RWTH-Aachen.DE.
ftp://sunsite.informatik.rwth-aachen.de/pub/publications/CEUR-WS/Vol-XXX.zipand then make the changes as required.
Clearly indicate in the revised index.html the correction date and possibly the kind of revision you made, e.g. at the end:
23-Aug-2007: corrected title of paper 3Afterwards, put the corrected proceedings volume into a zip archive Vol-XXX.zip and upload it as described for the PUT procedure. Notify me with an email that you uploaded a correction.
The revision of published volumes is limited to error correction! For example, it might be that you forgot to include the pdf file of an article referenced in index.html. Another example is a misspelled title or author name. The revision is not meant for providing any improved version of a paper or to include papers that were not originally intended to be in the proceedings! Likewise, you cannot remove individual papers that were included in the original proceedings submission. This would violate the unwritten rules of academic conduct.
Of course, you as the proceedings editor have the right to remove a proceedings
volume as a whole (see procedure DELETE above).
Re-publication vs. mirroring
Being freely accessible on the Internet does not imply an
automatic right to re-publish/re-package CEUR-WS.org proceedings volumes (or parts of them)
without authorization.
Normally, only the proceedings editors have the right to re-publish their proceedings
elsewhere, e.g. with a publisher or via a Web site.
When proceedings editors decide to re-publish their CEUR-WS.org volume elsewhere,
they should make sure that the re-published version is clearly distinguishible from the
CEUR-WS.org version. In particular, it may not use the following attributes characteristic
to CEUR-WS.org:
Authors of individual papers are not restricted by CEUR-WS.org to re-publish their papers elsewhere. In fact, CEUR-WS.org does not acquire rights from authors: authors pass rights to the proceedings editors. This is typically a non-exclusive right to publish the author's paper. By doing so, authors can of course no longer publish their papers with another publisher who demands the transfer of the exclusive copyright! This would violate the earlier transfer of non-exclusive copyrights to the proceedings editors.
We forbid mirroring of the CEUR-WS.org web site or its parts. Mirroring is different from re-publication since it publishes a one-to-one copy via another Web site. A mirror would negatively affect the authenticity of CEUR-WS.org. At the end, why would anyone want to have a mirror of something that is freely accessible anyway?
M. Lenzerini: Description logics for schema level reasoning in databases. Proc. of 1st Workshop KRDB'94, Saarbrücken, Germany, September 20-22, 1994, CEUR Workshop Proceedings, ISSN 1613-0073, online CEUR-WS.org/Vol-1/lenzerini.pdf.A shorter form can be:
M. Lenzerini: Description logics for schema level reasoning in databases. Proc. of 1st Workshop KRDB'94, Saarbrücken, Germany, September 20-22, 1994, CEUR-WS.org/Vol-1/lenzerini.pdf.A whole proceedings volume can be referenced as follows:
Enrico Franconi, Michael Kifer (eds.): Knowledge Representation meets Databases 1999. Proc. 6th Intl. Workshop KRDB'99, Linköping, Sweden, July 29-30, 1999, CEUR Workshop Proceedings, ISSN 1613-0073, online CEUR-WS.org/Vol-21/.The physical URL http://SunSITE.informatik.rwth-aachen.de/Publications/CEUR-WS/ should not be used for references!
