Instructions

User Manual:

Open the PDF directly: View PDF PDF.
Page Count: 6

DownloadInstructions
Open PDF In BrowserView PDF
INSTRUCTIONS FOR AUTHORS:
HOW TO PREPARE PAPERS FOR JPC USING jpc.cls ∗
2018-06-20
ALICE NAME1, BOB NAME2, AND CARLA NAME3
address 1
e-mail address: name1@email1
address2; addresses should initially be duplicated, even if authors share an affiliation
e-mail address: name2@email2; ditto for email addresses
address 3
URL: name3@url3

(optionally, a web-page can be specified)

Abstract. The abstract has to precede the maketitle command. Be sure not to issue
the maketitle command twice! In the abstract, mathematical expressions must be kept
to the absolute minimum. Otherwise it should consist of plain ASCII text, without TEXcommands, including explicit references using the \cite command. Presently we are not
able to automatically extract an abstract containing such data and reliably turn it into
html code. If you cannot meet these criteria, it is your responsibility to provide us with
an html-version of your abstract. Please keep the abstract fairy short to prevent it from
spilling onto the second page!

Introduction
The Journal of Privacy and Confidentiality is a small journal, run by scientists like you who
devote their time and effort to make this a world-class open access journal that is free of
cost for readers as well as authors. To minimize the extra work for the layout editor and to
ensure smooth and fast publication of accepted articles, authors are asked to strictly adhere
to the instructions for preparing their final version given in this document, which takes the
form of a sample paper.
These instructions rely on the experience of multiple editors running this Journal
and others for several years, in particular the efforts of the editors of Logical Methods in
Computer Science (LMCS, https://lmcs.episciences.org/), whose LATEX class (and this
Key words and phrases: MANDATORY list of keywords.
OPTIONAL comment concerning the title, e.g., if a variant or an extended abstract of the paper has
appeared elsewhere.
thanks 2, optional.
thanks 3, optional.
∗

JOURNAL OF PRIVACY
AND CONFIDENTIALITY

www.journalprivacyconfidentiality.org
DOI:10.29012/jpc.v0.i0.000

1

c A. Name1, B. Name2, and C. Name3
Creative Commons (CC BY 4.0)

2

A. NAME1, B. NAME2, AND C. NAME3

”instructions.tex”) we used as a basis for ours. The instructions here address the most
time-consuming aspects of getting articles into publishable shape.
A note about Word documents. For those authors who are unfamiliar with LATEX, we
will provide some limited assistance. However, we strongly encourage you to try out modern
LATEX tools, such as Overleaf (https://www.overleaf.com), which make this quite easy.
A note about Wordperfect documents. Really?
TEX-nical matters. Please be aware that the class-file jpc.cls supplied to authors will be
replaced by the Journal’s master class-file before publication of your article. Hence it is not
necessary, and is in fact counterproductive, to emulate the appearance of published articles
by means of your personal macros. Submissions not using jpc.cls will be returned to the
authors, as the reformatting that usually results from changing the class-file is usually too
extensive and requires the original authors’ intervention.
What authors can do to help the layout editor is to make their TEX- source compatible
with the hyperref-package, which is included by the master class-file. In particular, care
should be taken to use the \texorpdfstring macro for mathematical expressions in section
or subsection headings (see, for instance, this explanation).
Authors must not (1) use unsupported fonts (like the times-package or the txfontspackage), (2) change the numbering style for theorems and definitions and the like, e.g.,
by redefining the already provided proclamation environments for Theorems, Propositions,
Lemmata, Corollaries etc. (you can add further environments, but those should comply with
the default numbering style), and (3) use the \sloppy option globally. If it is impossible to
achieve good line breaks by other means once the article is finished (reformulating a sentence,
changing the word order, etc.), one can use \sloppy as a last resort locally in a paragraph.
Using lengthy mathematical expressions inside running text can lead to ugly breaks
within formulae, even without producing overfull hboxes. If this is a persistent problem in
your paper, please consider using more displayed formulae, or changing your notation.
The use of different macro-packages for the purpose of creating diagrams or other
graphical displays is strongly discouraged. In the past that has led to papers that required
different ways of processing to display the graphics of one type or the other, but could not
easily be made to correctly display both types of graphics simultaneously. As a rule of thumb,
as long as pdflatex correctly processes your paper, you should be in good shape. (Users of
the pstricks-package and those used to including external eps-files should transform the
resulting PostScript files to pdf.)
Please be aware that the proofs may display different vertical spacing in general, in
particular different page breaks than the version originally submitted. If adjustments are
deemed to be necessary by the authors, they can be implemented on the basis of the proofs,
in collaboration with the layout editor, as a last step before final publication.

INSTRUCTIONS

3

Matters of convenience. Please submit only one file containing the TeX-source of
your paper! Of course, we understand that separating a TeX source into several files has
advantages during the creation of a paper, but please combine all parts into a single file for
your submission.
The following are exceptions to the above rule:
• Your personal macros can be contained in a separate file.
• You can use a single .bib file for bibliographic references. It should only include references
actually used.
• External graphics should of course be separately provided, with highest possible resolution.
All graphics should be in a separate dedicated subdirectory (e.g.“graphics” or “figures”).
Matters of style. See the website for more extensive writing style suggestions.
1. Multiple authors
In papers with multiple authors several points need to be mentioned. Do not worry about
footnote signs that will link author n to address n and the optional thanks n. This will be
taken care of by the layout editor. Even if authors share an affiliation and part of an email
address, they should follow the strict scheme outlined above and list their data individually.
The layout editor will notice duplication of data and can then arrange for more space-efficient
formatting. Alternatively, Authors can write “same data as Author n” into some field to
alert the layout editor. Unfortunately, so far we have not been able to devise a system
that automatically takes care of these issues. But once the layout editor is made aware of
some duplication, he can take some fairly simple measures to adjust the format accordingly.
Placing the responsibility on the layout editor insures that these formatting issues are
handled uniformly in different papers and that the authors do not have to second-guess the
Journal’s policy.
2. Use of Definitions and Theorems etc.
The numbering scheme for proclamations (Theorems, Definitions, etc.) uses the section
number followed by the number of the current proclamation. There are no different “numbering threads” for the various types of proclamations, as then the relative position of, e.g.,
Theorem 2.7 relative to, e.g., Definition 2.9 would not be clear.
Definition 2.1. This is a definition.
Please use the supplied proclamation environments (as well as LaTeX’s cross-referencing
facilities), or extend them in the spirit of the given ones, if necessary. Refrain from replacing
the Journal’s proclamation macros by your own constructs, especially do not change the
numbering scheme: all proclamations are to be numbered consecutively!

4

A. NAME1, B. NAME2, AND C. NAME3

2.1. First Subsection. This is a test of subsectioning. It works like numbering of paragraphs but is not linked with the numbering of theorems.
Proof. You can use the familiar \begin{proof}. . . \end{proof} construction. Please do not
insert a blank line before \end{proof}, as this moves the box to a new line.
In case a proof ends with an itemization, please issue the command \qedhere at the end
of the final item, before calling \end{enumerate} (or similar) and \end{proof}. Otherwise
the end-of-proof box is put on a separate line following the last item, which looks awkward,
unless the last line is too full to accommodate the box.
For options how to handle proofs ending in a displayed multi-line equation or formula,
see this discussion.
Corollary 2.2. If no proof is given, jpc.cls provides Paul Taylor’s end-of-proof box \qed
to conclude a proclamation (Theorem, Proposition, Lemma, Corollary). Please do not
redefine \qed!

3. Itemization
JPC.cls provides the familiar environments
(1) \begin{itemize}. . . \end{itemize}
(2) \begin{enumerate}. . . \end{enumerate} (see this listing)
(3) \begin{description}. . . \end{description}
in a form based on the enumitem-package, version 3.5.2 (please update, if you have an earlier
version). This offers considerable simplifications, both for authors and the Layout Editor.
Modifying the spacing of these environments is strongly discouraged. If you wish to change
the labels, please consult the documentation of the enumitem-package. A simple example is
found at the end of this document.
When proclamations or proofs start with an itemization without preceding text, two
possibilities exist:
Theorem 3.1.
(1) Issuing an \hfill-command before the beginning of the list environment will push the
first item to a new line, like in this case.
(2) This is the second item.
Proof.
(1) The same behavior occurs in proofs; to start the first item on a new line an explicit
\hfill-command is necessary.
(2) Citations can be formatted as you like, provided (i) the formatting is consistent and (ii)
each citation begins with the last name of the first author, as in Abowd et al. [2009].
Package \natbib and a style such as abbrvnat work well.
We strongly recommend using this variant since it produces rather orderly output. The
space-saving variant, in contrast, can look quite awful, cf. Theorem 3.2 below. Please notice
that this paragraph is not indented, since it is following a proclamation that ended with a
list environment. This can be achieved by starting the paragraph directly after the end of
that environment, without inserting a blank line, or by explicit use of the noindent-command
at the beginning of the paragraph. The effect indentation may have after a list environment
is demonstrated after the proof of Theorem 3.2.

INSTRUCTIONS

5

Theorem 3.2. (1) Without the \hfill-command the first item starts in the same line as
the title for the proclamation.
(2) This may be useful when space needs to be conserved, but not in an electronic journal.
Proof. (1) As you can see, the second option produces a somewhat unpleasant effect.
(2) Hence we would urge authors to use the first variant. Perhaps a TEX-guru can help us
to make that the default, without the need for the \hfill-command.
Here we started a new paragraph without suppressing its indentation. This adds to the
rather disorienting appearance produced by not turning off the space-saving measures built
into amsart.cls, on which this style is based. Please do issue the \noindent command in
such situations, just as after the proof of Theorem 3.1 above.
4. Figures
Figures should be used to help with exposition. Where possible, one or more figures should
provide illustrations of main results. These figures may be split into multiple parts. The
legend on these figures should have enough detail that someone can get an impression of
what is being displayed just by looking at the figure.
Acknowledgment
The authors wish to acknowledge fruitful discussions with A and B.
References
J. M. Abowd, K. Nissim, and C. J. Skinner. First issue editorial. Journal of Privacy and
Confidentiality, 1(1), apr 2009. doi: 10.29012/jpc.v1i1.562. URL https://doi.org/10.
29012/jpc.v1i1.562.
Appendix A.
Here is a check-list to be completed before submitting the paper to JPC:
. your submission uses the latest version of jpc.cls
. the text of your submission is contained in a single file, except for macros and graphics
. your graphics use only one format
. you have employed the Journal’s original proclamation environments, or suitable extensions
thereof
. you have loaded the hyperref package
. you have not loaded the times package
. you have not routinely adjusted vertical spacing manually by issuing \vspace or \vskip
commands
. you have used the command \sloppy only locally and in emergency cases
. your displayed equations use the \[...\] construct
. your abstract only contains as few math-expressions as possible and no references

6

A. NAME1, B. NAME2, AND C. NAME3

This listing also shows how to override the default bullet • of the itemize-envronment
by a different symbol, in this case \triangleright.

This work is licensed under the Creative Commons License âĂŞ Attribution 4.0 International
(CC BY 4.0). To view a copy of this license, visit https://creativecommons.org/licenses/by/4.0/
or send a letter to Creative Commons, 171 Second St, Suite 300, San Francisco, CA 94105,
USA, or Eisenacher Strasse 2, 10777 Berlin, Germany



Source Exif Data:
File Type                       : PDF
File Type Extension             : pdf
MIME Type                       : application/pdf
PDF Version                     : 1.5
Linearized                      : No
Page Count                      : 6
Page Mode                       : UseOutlines
Author                          : 
Title                           : 
Subject                         : 
Creator                         : LaTeX with hyperref package
Producer                        : pdfTeX-1.40.19
Create Date                     : 2018:06:24 21:58:32-04:00
Modify Date                     : 2018:06:24 21:58:32-04:00
Trapped                         : False
PTEX Fullbanner                 : This is MiKTeX-pdfTeX 2.9.6642 (1.40.19)
EXIF Metadata provided by EXIF.tools

Navigation menu