Author's guide - Instructions for Final preparation

Journal of Machine Learning Research

[Based heavily on the JAIR Author's Guide, gratefully reproduced by permission of JAIR]

This file is available at

Checklist (see detailed instructions below)

1.   [ ] Format article using JMLR style.
2.   [ ] Have your article proofread.
3.   [ ] Contact editor (, obtain final approval and formatting check.
4.   [ ] Fill out permission to publish form, and send it.
5.   [ ] Fill out source code release, and send it (only necessary if you are releasing source code in an online appendix).
6.   [ ] Fill in page numbers and publication date, make final changes.
7.   [ ] Create HTML version (strongly recommended, but not required).
8.   [ ] Send all the required files.
9.   [ ] Inform the editor of any special mailing lists or newsgroups you'd like an announcement sent to.
10. [ ] After your article is published, create forward pointers (optional).

Once a paper has been accepted for publication in JMLR, you should follow the procedure outlined below. The final version of your manuscript is due to us within three months of the acceptance date. If you require more than three months, please request an extension from the editor. 

1. Format your article according the JMLR style, which is described in Instructions for Formatting JMLR Articles (PostScript and PDF versions are also available). The instructions also describe the use of the JMLR LaTeX style file, which should simplify adhering to the requirements. There is also an annotated JMLR sample paper available as LaTeX source, PostScript and PDF, which we strongly recommend using as a template for your submission.

For users of LyX, the graphical front end to LaTeX, Ralf Herbrich has made available a set of LyX layout files that conform to the JMLR style.

For users of Microsoft Word, George Forman has made available a template to simplify following the JMLR format. However, note that Computer Modern Roman, the standard font used by JMLR, is not available in most MS Word installations. Times Modern Roman, the closest match in MS Word, is acceptable, but please realize that your paper will look slightly different from the JMLR standard when it is published.

Unfortunately, we do not yet have macros or a template for FrameMaker, or Gnu's GROFF; we would be indebted to anyone who, in the course of formatting their paper using these systems, could make their templates available.

Authors are responsible for correctly formatting their article. If you wish we can recommend professionals who will do this for you for a fee.

Here are things to check, before you send us your article:

Consulting a brief checklist of common formatting errors before submitting the formatted paper will save time and effort on everybody's part.

2. Make any final changes and have your article proofread. For better or worse, we do not have a copyediting staff. (Note: Authors are notoriously bad proofreaders. Have the paper proofread by a skilled proofreader - NOT one of the authors.)

3. Send the paper to the editor in charge of your article. Also send a copy You should leave the publication date and page numbers blank for the moment, pending final approval from the editor (step 7, below).

4. Please print out, fill in, and sign the Permission to Publish form (available in plain text and PDF formats). Send the form to:

Journal of Machine Learning Research
Leslie Pack Kaelbling, Editor
32 Vassar Street, 32G-486
Cambridge, MA 02139

The form agreement provides non-exclusive rights for electronic publication to JMLR and for print publication to Microtome Press; the copyright remains with the authors.

5. We encourage you to make use of "online appendices" where appropriate. Online appendices can contain source code, data, even quicktime demonstrations -- anything that that will make life easier (or more interesting) for your readers and researchers who follow in your footsteps.

If there are online appendices containing source code, please sign the software release form (available in PostScript and PDF formats) and send it along with the Copyright form. The release form is intended to reduce the liability of JMLR.

6. Once you have the final approval on the paper and the formatting, you should add in the page numbers and publication date sent to you by the editor. Put the final touches on any additional versions of the paper that you want us to publish alongside the PostScript or PDF version. As noted above, we encourage authors to produce an HTML version of their paper.

7. JMLR requests (but does not require) that authors construct a version of the paper in HTML in addition to the PostScript version. Check out the Latex2HTML translator at the following URL:
(If you use Latex2HTML, don't bother using the JMLR style file, as it will only cause problems.)

8. Send the editor all the files. (A single tar file is convenient.) We would appreciate it if you use the following naming scheme for your files. Assuming the first author's last name is "Jones" and the current year is 2000, you should send us:

Optionally: Note: if the first author has previously published a JMLR article earlier in the year called jones00a, use jones00b this time.

As an alternative to emailing the files, you can send FTP instructions to the managing editor.

9. After we receive the final version and release the article, we will post an announcement on the JMLR mailing list. The paper will also be stored at the JMLR distribution site and forwarded to ACM's computing repository (CORR) and the CiteSeer Index.

If you know of any other mailing lists where it would be appropriate to post an announcement for your paper, please feel free to forward our announcement. If you would prefer that we do, please let the managing editor know the addresses where he should forward the announcement.

10. After your article is published, you can create an HTML page listing pointers to subsquent papers you (or others, if you wish) write on the same topic. JMLR will maintain a pointer to this page, assuming you agree to maintain the page of forward pointers. Contact the Managing Editor if you are interested in this.