GDPRhub commentary style guide: Difference between revisions

From GDPRhub
No edit summary
Line 1: Line 1:
This page provides specific guidance on the Commentary. For general information regarding the writing style on the Hub, including on the Commentary, please follow this [https://wiki.noyb.eu/index.php?title=Legal_Writing_Style_Guide guide].
This page provides specific guidance on the Commentary. For general information regarding the writing style on the Hub, including on the Commentary, please follow this [https://wiki.noyb.eu/index.php?title=Legal_Writing_Style_Guide guide].


== General Information for Commentary Articles ==
==General Information for Commentary Articles==
The '''GDPRhub''' '''Commentary''' features relatively short analysis regarding a GDPR Article. Commentaries should not exceed 5000 words total (including abstract, main text, references and figure legends). They should have an abstract of 50 words or less ("Overview"), no more than 35 references, and one or two figures (with figure legends) or tables.
The '''GDPRhub''' '''Commentary''' features relatively short analysis regarding a GDPR Article. Commentaries should not exceed 5000 words total (including abstract, main text, references and figure legends). They should have an abstract of 50 words or less ("Overview"), no more than 35 references, and one or two figures (with figure legends) or tables.


== Writing your Commentary Article ==
==Writing your Commentary Article==


=== Overview ===
===Overview===
Commentary begins with an introductory paragraph that immediately presents the issues under discussion in a way that captures the reader's interest. The Overview should be general enough to orient the reader not familiar with the specifics of the field being discussed. Here, and throughout the article, the author should avoid the jargon and special terms of his or her field or system.
Commentary begins with an introductory paragraph that immediately presents the issues under discussion in a way that captures the reader's interest. The Overview should be general enough to orient the reader not familiar with the specifics of the field being discussed. Here, and throughout the article, the author should avoid the jargon and special terms of his or her field or system.


=== Body of the text ===
===Body of the text===
The body of the text should, in the limited space available, develop the discussion in a lively manner. By "lively" we don't mean hype and oversimplification. Rather, the editors seek clear, declarative writing that avoids the passive tense, tangled constructions, and needless detail. Avoid asides that interrupt the flow of the text.
The body of the text should, in the limited space available, develop the discussion in a lively manner. By "lively" we don't mean hype and oversimplification. Rather, the editors seek clear, declarative writing that avoids the passive tense, tangled constructions, and needless detail. Avoid asides that interrupt the flow of the text.


=== Citation Style ===
Hierarchy
In the text, references to the literature should be by author and year; where there are two authors, both should be named; with three or more only the first author's name plus "et al." need be given. The list at the end of the paper should include only works mentioned in the text and should be arranged alphabetically by name of first author. References should be cited as follows:


* Journal papers -- name(s) and initial(s) of author(s), year in brackets, full title, name of the journal as abbreviated in Chemical Abstracts, volume number, first and last page numbers:Quiring R, Walldorf U, Koter U, Gehring WJ (1994) Homology of the eyeless gene of Drosophila to the small eye gene in mice and aniridia in humans. Science 265:785
(No) numbering
* Books -- name(s) of author(s), year in brackets, full title, edition, publishers, place of publication, page number:Maizels N, Weiner AM (1993) The genomic tag hypothesis: modern viruses as fossils of ancient strategies  for genomic replication. In: Gesteland RF, Atkins JF (eds) The RNA world. Cold Spring Harbor Laboratory Press, New York, pp. 577 -- 602Li W - (1997) Molecular evolution. Sinauer Assosiates, Sunderland, MA
 
<br />
 
===Citation Style===
We quote the ''author'', the ''editor'' (if applicable) the title, the edition, date or year and the reference used by the book (e.g. reference number or page). Mind that there are often multiple books that are called “General Data Protection Regulation” and alike or that these books may be published in the 10<sup>th</sup> edition, so we have to make sure that we provide a clear reference.  
 
* ''Books'' --> name(s) of author(s), year in brackets, full title, edition, publishers, place of publication, page number. Where there are two authors, both should be named; with three or more only the first author's name plus "et al." need be given. The list at the end of the paper should include only works mentioned in the text and should be arranged alphabetically by name of first author:
 
<blockquote>Example: Maizels N, Weiner AM (1993) The genomic tag hypothesis: modern viruses as fossils of ancient strategies  for genomic replication. In: Gesteland RF, Atkins JF (eds) The RNA world. Cold Spring Harbor Laboratory Press, New York, pp. 577 -- 602Li W - (1997) Molecular evolution. Sinauer Assosiates, Sunderland, MA</blockquote>
 
* ''Journal papers'' --> name(s) of author(s), year in brackets, full title, full name of the journal, volume number, first and last page numbers. In case there are three or more authors, the above stays valid:
 
<blockquote>Example: Quiring R, Walldorf U, Koter U, Gehring WJ (1994) Homology of the eyeless gene of Drosophila to the small eye gene in mice and aniridia in humans. Science 265:785</blockquote>
 
* ''EDPB/DPAs guidelines, opinions'' --> name of the authority (EDPB, CNIL, etc.), title, date, page number
 
<blockquote>Example:</blockquote>
 
* ''EDPB, DPA, Court decisions'' --> name of the authority, case number, date and link to the GDPRhub summary (if available)
 
<blockquote>Example: </blockquote>Please, <u>do not</u> use op. cit., ibid., 3-m dashes, en dashes, or et al. (in place of the complete list of authors' names). Never.


[[Category:Legal]]
[[Category:Legal]]

Revision as of 09:47, 22 April 2021

This page provides specific guidance on the Commentary. For general information regarding the writing style on the Hub, including on the Commentary, please follow this guide.

General Information for Commentary Articles

The GDPRhub Commentary features relatively short analysis regarding a GDPR Article. Commentaries should not exceed 5000 words total (including abstract, main text, references and figure legends). They should have an abstract of 50 words or less ("Overview"), no more than 35 references, and one or two figures (with figure legends) or tables.

Writing your Commentary Article

Overview

Commentary begins with an introductory paragraph that immediately presents the issues under discussion in a way that captures the reader's interest. The Overview should be general enough to orient the reader not familiar with the specifics of the field being discussed. Here, and throughout the article, the author should avoid the jargon and special terms of his or her field or system.

Body of the text

The body of the text should, in the limited space available, develop the discussion in a lively manner. By "lively" we don't mean hype and oversimplification. Rather, the editors seek clear, declarative writing that avoids the passive tense, tangled constructions, and needless detail. Avoid asides that interrupt the flow of the text.

Hierarchy

(No) numbering


Citation Style

We quote the author, the editor (if applicable) the title, the edition, date or year and the reference used by the book (e.g. reference number or page). Mind that there are often multiple books that are called “General Data Protection Regulation” and alike or that these books may be published in the 10th edition, so we have to make sure that we provide a clear reference.

  • Books --> name(s) of author(s), year in brackets, full title, edition, publishers, place of publication, page number. Where there are two authors, both should be named; with three or more only the first author's name plus "et al." need be given. The list at the end of the paper should include only works mentioned in the text and should be arranged alphabetically by name of first author:

Example: Maizels N, Weiner AM (1993) The genomic tag hypothesis: modern viruses as fossils of ancient strategies for genomic replication. In: Gesteland RF, Atkins JF (eds) The RNA world. Cold Spring Harbor Laboratory Press, New York, pp. 577 -- 602Li W - (1997) Molecular evolution. Sinauer Assosiates, Sunderland, MA

  • Journal papers --> name(s) of author(s), year in brackets, full title, full name of the journal, volume number, first and last page numbers. In case there are three or more authors, the above stays valid:

Example: Quiring R, Walldorf U, Koter U, Gehring WJ (1994) Homology of the eyeless gene of Drosophila to the small eye gene in mice and aniridia in humans. Science 265:785

  • EDPB/DPAs guidelines, opinions --> name of the authority (EDPB, CNIL, etc.), title, date, page number

Example:

  • EDPB, DPA, Court decisions --> name of the authority, case number, date and link to the GDPRhub summary (if available)

Example:

Please, do not use op. cit., ibid., 3-m dashes, en dashes, or et al. (in place of the complete list of authors' names). Never.