The submission must follow the following Isabelle style rules. For additional guidelines on Isabelle proofs, also see the this guide (feel free to follow all of these; only the below are mandatory). Technical details about the submission process and the format of the submission are explained on the submission site.
xa— use Isar, the
rename_tacto avoid such names.
nunchakuthose calls must include the
expectparameter. Alternatively the
expectparameter must be set globally via, e.g.
applyscripts should be indented by subgoal as in the Isabelle distribution. If an
applycommand is applied to a state with
n+1subgoals, it must be indented by
nspaces relative to the first
applyin the sequence.
Your submission must contain an abstract to be displayed on the web site – usually this will be the same as the abstract of your proof document in the root.tex file. You can use LaTeX formulae in this web site abstract, either inline formulae in the form $a+b$ or \(a+b\) or display formulae in the form $$a + b$$ or \[a + b\]. Other occurrences of these characters must be escaped (e.g. \$ or \\(). Note that LaTeX in the title of an entry is not allowed. Most basic LaTeX functionality should be supported. For details on what parts of LaTeX are supported, see the MathJax documentation.
It is possible and encouraged to build on other archive entries in your submission. There is a standardised way to refer to other AFP entries in your theories.
Your submission will be refereed and you will receive notification as soon as possible. If accepted, you must agree to maintain your archive entry or nominate someone else to maintain it. The Isabelle development team will assist with maintenance, but it does not have the resources to fully maintain the complete archive.
If you have questions regarding your submission, please email email@example.com. If you need help with Isabelle, please use the firstname.lastname@example.org mailing list. It is always a good idea to subscribe.
The Archive of Formal Proofs is an online resource and therefore more dynamic than a normal scientific journal. Existing entries can and do evolve and can also be updated significantly by their authors.
This conflicts with the purpose of archiving and preserving entries as they have been submitted and with the purpose of providing a clear and simple interface to readers.
The AFP deals with this by synchronizing such updates with Isabelle releases:
Significant changes of an entry should be recorded in the metadata of the entry using the keyword “extra-history”. The resulting web page should look something like this.
Updating an entry should be mostly monotone: you add new material, but you do not modify existing material in a major way. Ideally, entries (by other people) that build on yours should not be affected. Otherwise you have to liaise with them first. If you intend to carry out major non-monotone changes, you will need to submit a completely new entry (with a description of how it relates to the old one). This should be required only very rarely: AFP entries should be mature enough not to require major changes to their interface (i.e. the main functions and theorems provided).
Major monotone changes, e.g. adding a new concept rather than more results on existing concepts, may also call for a new entry, but one that builds on the existing one. This depends on how you would like to organize your entries.
The above means that if you are an author and would like to provide a new, better version of your AFP entry, you can do so.
To achieve this, you should base your changes on the mercurial development version of your AFP entry and test it against the current Isabelle development version.
If you would like to get write access to your entry in the mercurial repository or if you need assistance, please contact the editors.