-
Notifications
You must be signed in to change notification settings - Fork 37
Expand file tree
/
Copy pathTemplate.tex
More file actions
150 lines (113 loc) · 5.32 KB
/
Copy pathTemplate.tex
File metadata and controls
150 lines (113 loc) · 5.32 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
% If the calculus has an acronym, define it.
% (e.g. \newcommand{\LK}{\ensuremath{\mathbf{LK}}\xspace})
\calculusName{ToDo} % The name of the calculus
\calculusAcronym{} % The acronym if defined above, or empty otherwise.
\calculusLogic{ToDo} % Specify the logic (e.g. Classical Logic, Intuitionistic Logic, ...) for which this calculus is intended.
\calculusLogicOrder{ToDo} % Specify the order of the logic (e.g. Propositional, Quantified Propositional, First-Order, Higher-Order, ...).
\calculusType{ToDo} % Specify the calculus type (e.g. Tableau, Sequent Calculus, Hyper-Sequent Calculus, Natural Deduction, ...)
\calculusYear{ToDo} % The year when the calculus was published.
\calculusAuthor{ToDo:FullNameAuthor1} % The name(s) of the author(s) of the calculus.
%\calculusAuthor{ToDo:FullNameAuthor2}
%\calculusAuthor{ToDo:FullNameAuthor3}
% If this proof system has been implemented,
% include below the names and URLs of the implementations
% (e.g. \implementation{Coq}{https://coq.inria.fr})
%\implementation{NameOfImplementation1}{URL1}
%\implementation{NameOfImplementation2}{URL2}
\entryTitle{ToDo} % Title of the entry (usually coincides with the name of the calculus).
\entryAuthor{ToDo:FullNameAuthor1}
%\entryAuthor{ToDo:FullNameAuthor2}
%\entryAuthor{ToDo:FullNameAuthor3}
% The encyclopedia's peer-reviewing policy is described here:
% http://proofsystem.github.io/Encyclopedia/
%
% Reviewers of this entry will be acknowledged in the following lines:
% \entryReviewer{Reviewer 1's name}
% \entryReviewer{Reviewer 2's name}
% \entryReviewer{Reviewer 3's name}
%
% The lines above will be filled by the coordinators.
% If you would like to indicate people
% who could review your entry, contact the coordinators.
% If you wish, use tags to give any other information
% that might be helpful for classifying and grouping this entry:
% e.g. \etag{Two-Sided Sequents}
% e.g. \etag{Multiset Cedents}
% e.g. \etag{List Cedents}
% You are free to invent your own tags.
% The Encyclopedia's coordinator will take care of
% merging semantically similar tags in the future.
\maketitle
% If your files are called "MyProofSystem.tex" and "MyProofSystem.bib",
% then you should write "\begin{entry}{MyProofSystem}" in the line below
\begin{entry}{ToDo}
% Define here any newcommands you may need:
% e.g. \newcommand{\necessarily}{\Box}
% e.g. \newcommand{\possibly}{\Diamond}
\begin{calculus}
% Add the inference rules of your proof system here.
% The "proof.sty" and "bussproofs.sty" packages are available.
% If you need any other package, please contact the coordinator (Bruno Woltzenlogel Paleo <bruno.wp@gmail.com>)
ToDo
\end{calculus}
% The following sections ("clarifications", "history",
% "technicalities") are optional. If you use them,
% be very concise and objective. Nevertheless, do write full sentences.
% Try to have at most one paragraph per section, because line breaks
% do not look nice in a short entry.
% \begin{clarifications}
% ToDo: write here short remarks that may help the reader to understand
% the inference rules of the proof system.
% \end{clarifications}
% \begin{history}
% ToDo: write here short historical remarks about this proof system,
% especially if they relate to other proof systems.
% Use "\iref{OtherProofSystem}" to refer to another proof system
% in the Encyclopedia (where "OtherProofSystem" is its ID).
% Use "\irefmissing{SuggestedIDForOtherProofSystem}" to refer to
% another proof system that is not yet available in the encyclopedia.
% \end{history}
% \begin{technicalities}
% ToDo: write here remarks about soundness, completeness, decidability...
% \end{technicalities}
% General Instructions:
% =====================
% The preferred length of an entry is 1 page.
% Do the best you can to fit your proof system in one page.
%
% If you are finding it hard to fit what you want in one page, remember:
%
% * Your entry needs to be neither self-contained nor fully understandable
% (the interested reader may consult the cited full paper for details)
%
% * If you are describing several proof systems in one entry,
% consider splitting your entry.
%
% * You may reduce the size of your entry by ommitting inference rules
% that are already described in other entries.
%
% * Cite parsimoniously (see detailed citation instructions below).
%
%
% If you do not manage to fit everything in one page,
% it is acceptable for an entry to have 2 pages.
%
% For aesthetic reasons, it is preferable for an entry to have
% 1 full page or 2 full pages, in order to avoid unused blank space.
% Citation Instructions:
% ======================
% Please cite the original paper where the proof system was defined.
% To do so, you may use the \cite command within
% one of the optional environments above,
% or use the \nocite command otherwise.
% You may also cite a modern paper or book where the
% proof system is explained in greater depth or clarity.
% Cite parsimoniously.
% Do not cite related work. Instead, use the "\iref" or "\irefmissing"
% commands to make an internal reference to another entry,
% as explained within the "history" environment above.
% You do not need to create the "References" section yourself.
% This is done automatically.
% Remove all instruction comments before submitting.
% Leave an empty line above "\end{entry}".
\end{entry}