CINXE.COM

<!DOCTYPE html>      <html lang="en">  <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> <meta name="viewport" content="width=device-width, initial-scale=1.0" /> <title>Guidelines and Policies for Entry Content (Stanford Encyclopedia of Philosophy)</title>  <link href="https://fonts.googleapis.com/css?family=Source+Sans+Pro:400,300,600,200&subset=latin,latin-ext" rel="stylesheet" type="text/css" /> <link rel="stylesheet" type="text/css" media="screen" href="css/bootstrap.min.css" /> <link rel="stylesheet" type="text/css" media="screen" href="css/bootstrap-responsive.min.css" /> <link rel="stylesheet" type="text/css" href="css/font-awesome.min.css" />  <link rel="stylesheet" type="text/css" media="screen" href="css/style.css" /> <link rel="stylesheet" type="text/css" media="print" href="css/print.css" /> <link rel="stylesheet" type="text/css" href="css/entry.css" />  <script type="text/javascript" src="js/jquery-1.9.1.min.js"></script> <script type="text/javascript" src="js/bootstrap.min.js"></script>  <script type="text/javascript" src="js/sep.js"></script> </head>  <body class="nojs" id="pagetopright"> <div id="container"> <div id="header-wrapper"> <div id="header"> <div id="branding"> <div id="site-logo"><a href="index.html"><img src="symbols/sep-man-red.png" alt="SEP logo" /></a></div> <div id="site-title"><a href="index.html">Stanford Encyclopedia of Philosophy</a></div> </div> <div id="navigation"> <div class="navbar"> <div class="navbar-inner"> <div class="container"> <button class="btn btn-navbar collapsed" data-target=".nav-collapse" data-toggle="collapse" type="button"> <i class="icon-reorder"></i> Menu </button> <div class="nav-collapse in collapse"> <ul class="nav"> <li class="dropdown open"><a id="drop1" href="#" class="dropdown-toggle" data-toggle="dropdown" role="button"><i class="icon-book"></i> Browse</a> <ul class="dropdown-menu" role="menu" aria-labelledby="drop1"> <li role="menuitem"><a href="contents.html">Table of Contents</a></li> <li role="menuitem"><a href="new.html">What's New</a></li> <li role="menuitem"><a href="https://plato.stanford.edu/cgi-bin/encyclopedia/random">Random Entry</a></li> <li role="menuitem"><a href="published.html">Chronological</a></li> <li role="menuitem"><a href="archives/">Archives</a></li> </ul> </li> <li class="dropdown open"><a id="drop2" href="#" class="dropdown-toggle" data-toggle="dropdown" role="button"><i class="icon-info-sign"></i> About</a> <ul class="dropdown-menu" role="menu" aria-labelledby="drop2"> <li role="menuitem"><a href="info.html">Editorial Information</a></li> <li role="menuitem"><a href="about.html">About the SEP</a></li> <li role="menuitem"><a href="board.html">Editorial Board</a></li> <li role="menuitem"><a href="cite.html">How to Cite the SEP</a></li> <li role="menuitem"><a href="special-characters.html">Special Characters</a></li> <li role="menuitem"><a href="tools/">Advanced Tools</a></li> <li role="menuitem"><a href="contact.html">Contact</a></li> </ul> </li> <li class="dropdown open"><a id="drop3" href="#" class="dropdown-toggle" data-toggle="dropdown" role="button"><i class="icon-leaf"></i> Support SEP</a> <ul class="dropdown-menu" role="menu" aria-labelledby="drop3"> <li role="menuitem"><a href="support/">Support the SEP</a></li> <li role="menuitem"><a href="support/friends.html">PDFs for SEP Friends</a></li> <li role="menuitem"><a href="support/donate.html">Make a Donation</a></li> <li role="menuitem"><a href="support/sepia.html">SEPIA for Libraries</a></li> </ul> </li> </ul> </div> </div> </div> </div> </div>  <div id="search"> <form id="search-form" method="get" action="search/searcher.py"> <input type="search" name="query" placeholder="Search SEP" /> <div class="search-btn-wrapper"><button class="btn search-btn" type="submit" aria-label="search"><i class="icon-search"></i></button></div> </form>  </div>  </div>  </div> <div id="content"> <h1>Guidelines and Policies for Entry Content</h1> <p> In this document, we develop guidelines and policies concerning the content of entries written for the <em>Stanford Encyclopedia of Philosophy</em>. Authors should not just familiarize themselves with Sections 1–4 below (and any remaining section that applies to their case), but also read our <a href="info.html#c">Copyright Policy</a>. The latter makes it clear that by sending us their entry, they are agreeing to the Copyright Policy. </p> <ol> <li><a href="#Econtent">Entry Substance, Style and Length</a></li> <li><a href="#revision">Entry Revision</a></li> <li><a href="#write">Writing a New Entry in Word or LaTeX</a></li> <li><a href="#format">Entry Format</a></li> <li><a href="#footnotes">The Use of Footnotes</a></li> <li><a href="#symbols">The Use of Special Symbols</a></li> <li><a href="#writeHTML">If You Choose to Write Your Entry in HTML</a> (Optional) <ul> <li><a href="#sup-links">Linking from the Main Entry to Supplementary Documents</a></li> <li><a href="#spe-cha">Special Characters</a></li> <li><a href="#for-rel">Formatting the Related Entries Section in HTML</a></li> <li><a href="#for-foot">Formatting Footnotes in HTML</a></li> </ul></li> </ol> <h2><a id="Econtent"></a>1. Entry Substance, Style and Length</h2> <p> The <em>Stanford Encyclopedia of Philosophy</em> is intended to serve as an authoritative reference work suitable for use by professionals and students in the field of philosophy, as well as by all others interested in authoritative discussions on philosophical topics. Entries should therefore be scholarly, written with the highest of professional standards, yet strive to be of interest to as wide an audience as possible. Entries should focus on the philosophical issues and arguments rather than on sociology and individuals, particularly in discussions of topics in contemporary philosophy. In other words, entries should be “idea-driven” rather than “person-driven”. One indication that the entry is “person-driven” is that the section and subsection titles invoke the names of philosophers; this should be avoided, though the editors may make an exception if the entry is primarily historical in character. (If in doubt, check with the editors.) Non-historical, concept-based entries should therefore focus on <em>the philosophical problems to be solved</em> and on the extent to which distinctions, ideas, concepts, or arguments being put forward solve the problem. The internal logic of these distinctions, ideas and arguments should therefore drive the discussion, so that the reader will more frequently encounter sentences that <i>cite</i> philosophers without coming across as being <i>about</i> them.</p> <p> Authors should try to structure the entry so as to organize the ideas into common themes and avoid where possible straight historical presentations of “who said what when and where”. Entries should avoid having numerous sentences of the form “X (1960, 11) argues that …”, “Y responds that … (1964, 8)”, “Z additionally requires (1970, 2) that …”, etc. Rather, the ideas and arguments should, at least much more often than not, be the focus of the sentences, with inline, parenthetical citations at the end of the sentence that document the source of the idea, argument, etc. Moreover:</p> <ul> <li>Authors should strive to <em>minimize the use of jargon</em>, and introduce any such terms of art in plain or previously defined language. Entries should strive to be self-contained, so that readers can understand your entry without having to read a lots of other entries.</li> <li>Biographical entries should be critical (i.e., include mention and explanation of works critical of the subject's ideas) and not be hagiographical.</li> <li>Historical entries should not only introduce the primary literature (and cite the passages in the primary literature which support the description of the ideas being explained), but also should give evidence that they are <em>informed</em> by the secondary literature; such entries should include citations to the secondary literature when explaining key ideas for which there is significant discussion in the secondary literature (e.g., questions of interpretation, criticisms, etc.)</li> <li>Technical entries will be expected to include definitions of the technical terms used.</li> <li>The sources of all quotations should be clearly identified.</li> <li>Authors should avoid reference to unpublished and inaccessible materials. </li> </ul> <p> Entries should be objective/neutral analyses/surveys of the literature and offer a broad perspective of the topic rather than advocate a point of view. Authors should see their mission as that of introducing advanced undergraduates (or grad students and colleagues), who may have no special knowledge of the topic, to the main issues and arguments discussed in the most important pieces of primary and secondary literature on the topic, so as to bring their readers to a state where they can read that literature with insight and understanding. SEP entries should have <em>no other agenda</em> than to achieve this mission in a way that the balance of discussion in the entry is in proportion to, and reflects, the balance in the literature. Clarity of substance and style should also be one of the most important goals.</p> <p> <em>Encyclopedia</em> entries should therefore not be idiosyncratic or polemical, and should avoid ‘editorializing’ value judgments in the voice of the entry. The entry should not promote the author's work, but rather strive for balance by presenting the important arguments that have been put forward on both sides of an issue. Controversial claims should be identified as such. Authors should not use the first person pronouns “I”, “me”, “my” (or “we”, “us”, or “our” -- if the entry is coauthored) and should avoid such constructions as “as I (we) have argued (elsewhere/previously/in this essay) …” or “my (our) interpretation of this passage is …”, etc. Authors should not use their SEP entry to raise and advocate for or respond and defend against objections if those objections and responses aren't already in the published literature. Authors may, however, illuminate various sides of an issue by presenting potential objections and responses as long as the entry remains neutral and/or reflects the weight of scholarly opinion.</p> <p>Authors should also be circumspect with respect to the number of references to their own work, though obviously, since they are experts on the topic and typically will have written widely on it, occasional references may be appropriate. The editors of the <em>Encyclopedia</em> will ensure that entries do not overstep the bounds of propriety in this regard.</p> <p> Authors should not cite their own dissertations. Those who believe that it is necessary should seek an exception beforehand. The SEP editors will then provide a list of criteria that need to be met and if the author demonstrates that those criteria are satisfied, permission may be given. </p> <p> The length of entries should depend on the topic. SEP entries now have a reading length (i.e., not including the Bibliography) averaging 12,000 words. Entries may be shorter or longer depending on the breadth of the topic and the amount of literature to introduce and explain. Please contact us if the entry looks like it will grow to more than 12,000 words. We encourage authors to organize longer entries in a modular style, so that readers can understand later sections without having to read all of the earlier ones. In some cases, it helps to write a set of nested, cross-linked documents rather than write a single, linear document. By this we mean that overly detailed, highly technical, or highly scholarly material should be put into separate HTML (“supplementary”) documents and linked into the main entry. (See below.) In such circumstances the main (index.html) file for the entry should still provide a comprehensive overview of the entire topic. This way, the main entry should become readable by an intelligent undergraduate in a sitting of about an hour or two. More advanced readers can follow the links to the highly technical, detailed or scholarly material. Such a cross-linked set of documents will therefore be accessible to a wide audience. However, authors should create such “nested” entries only if it seems unlikely that a separate entry in the <em>Encyclopedia</em> will be created to discuss the supplementary material.</p> <h2><a id="revision"></a>2. Entry Revision</h2> <p> Because the <em>Encyclopedia</em> is designed to be a dynamic reference work, authors are responsible for maintaining and periodically updating their entries. Specifically, authors are expected: (1) to update their entries regularly (typically every 4-5 years), especially in response to important new research on the topic of the entry, and (2) to revise their entries <em>in a timely way</em> in light of any valid criticism they receive, whether it comes from the subject editors on our Editorial Board, other members of the profession, or interested readers.</p> <p> In connection with (1), authors should update the Bibliography and the Other Internet Resources sections of their entries regularly, to keep pace with significant new publications, both in print and on the web. If important new publications affect the currency of the main text, then the main text should be altered so as to reflect the important ideas in the new research. However, authors should ensure that the entry doesn鈥檛 continue to get longer with each revision. This may require retiring discussions that are no longer central, and/or streamlining existing passages to make room for the latest research. Since the Bibliography and Other Internet Resources don鈥檛 count towards the reading length, authors may add new works without reducing existing material in those sections. If an update looks like it will substantially increase the entry鈥檚 reading length, please be in touch with the Editors. (Recall that for most entries, an advanced undergraduate is meant to be able to understand, and finish, the entry within an hour or two.)</p> <p> In connection with (2), the validity of criticism shall be determined by the Editor, typically in consultation with the relevant members of the Editorial Board. The length of time required for a “timely” revision will be negotiable and will both respect the author's current commitments and reflect the seriousness of the criticism. However, entries which require revision but which are not revised within the negotiated timetable may be retired from the active portion of the <em>Encyclopedia</em> and left in the <em>Encyclopedia</em> Archives until such time as the entry is revised so as to engage the valid criticisms in question.</p> <h3>How to Revise Your Entry</h3>  <blockquote> <div style="border:1px solid; padding-left:1em"> <span style="color:#8c1515">Once an entry has been published, authors should no longer use Word or their own HTML-editor to revise the file (with two exceptions, see below). The HTML in published SEP entries has been carefully formatted so that it parses as valid at validator.w3.org. Word and other HTML-editors (with few exceptions) will damage the HTML, for they will rewrite our internationally compliant HTML with hundreds of unnecessary formatting instructions and generate an HTML file that fails to parse as HTML against international standards. Please DO NOT REVISE by downloading your entry and revising it in in Word or your own HTML editor. That will corrupt the file. Please follow the instructions below.</span> </div> </blockquote> <h4>Making Modifications:</h4> <p> There is a preferred, recommended, and easy-to-use protocol for making minor changes to your entry. If you would like to add/revise a paragraph, add an item to the Bibliography, fix a typo, etc., then the proper procedure to follow is to log in to our Author Interface at the URL that has been sent to you.</p> <p> Once logged in, initiate the action “Revise Entry on Server”. This will allow you to directly edit a copy of your entry on our machine (from whichever browser you are using). There is an Instructions/Help file for using this software. However, as you will see, when you use the Revise Entry function, you will be prompted to select the file you wish to edit. In most cases, you will select the main document, which is called “index.html” (some entries have multiple files, e.g., a main document “index.html” and supplementary documents). Note that when selecting the file, you have the option to:</p> <ul> <li>Edit a copy of the entry by using a Word-like (graphical) WYSIWYG (“what you see is what you get”) editor.</li> <li>Edit a copy of the HTML sourcefile directly through your browser. </ul> <p> If you choose the first option, to edit the file using a graphical, Word-like HTML editor:</p> <blockquote> <p>a new browser window will open up and you will be presented with a formatted and editable copy of your entry, with menu items at the top for adding italics, bold, etc. This should be familiar to you, as the menu icons for editing the entry will be similar to those you would use in Microsoft Word.</p> </blockquote> <p> If you choose the second option, to edit the HTML source:</p> <blockquote> <p>a new browser window will open up and you will be presented with a page on which the file you wanted to edit is divided up into segments, each containing a “View” box and an “Edit” box. You will find the material you wish to edit in the View box, since the text in this box is rendered, or formatted, HTML. Then you edit in the corresponding Edit box, which contains the HTML sourcefile (which is plain text with markup tags). It should be clear how to add content in the Edit box.</p> <p><span style="color:#8c1515">If you choose this option, please do not cut and paste from a Word document into an editing window unless you (1) first save the Word document as a “plain text” file, and then (2) cut and paste from the plain text file. Moreover, please do not cut and paste from a Word-generated HTML file into an editing window box unless you are sure that you are not pasting corrupted HTML code. You can cut and paste in HTML code, but you should be able to see the code itself and determine that it is simple HTML and not something that looks overly complicated.</span></p> </blockquote> <p> Every so often, you should SAVE your work, using the Save buttons at the left or at the top of the page. You may SAVE your work without submitting it for review, but when you believe you have completed the revisions you need to make, use the Save/Submit option, or return to the authors main menu page and use the Submit/Resubmit Privates Files to Editor function.</p> <p> The above procedure will work for most major, as well as minor modifications. If you wish to make a structural change to your entry, then the editors would be happy to help you reorganize the HTML in the file. They can create new sections and rearrange others. They can get the file into a state where you can then use the Revise Entry on Server function.</p> <p> Please note: If you are <em>revising</em> your entry, and you want to add or delete a footnote, you do not need to renumber the footnotes by hand. We have a script which will do this automatically. Please simply bring it to our attention and we renumber the notes for you. </p> <h4>Significant Structural Revisions or Rewriting Published Entries:</h4> <p> In some rare cases, where authors plan to make significant structural revisions or to rewrite their entries, they may write to us to obtain permission to update using Word or LaTeX. In that case, we will prepare a file for them to edit – we'll make sure that we generate a file in the appropriate format from the currently published entry. <p> In some still rarer cases, authors who can use a plain text editor to write raw HTML code can contact us and let us know that they are capable of doing so. We'll then send you a current HTML sourcefile to edit. We might ask to set up a test, to check that your plain text editor is not damaging the file.</p> <h2><a id="write"></a>3. Writing a New Entry in Word or LaTeX</h2> <p> Assuming that authors submit a document that is within the normal range of an average SEP entry, then the author may submit either a Word (or RTF) document, or a LaTeX document. SEP document editors will convert Word and LaTeX documents to HTML. Because the <em>Encyclopedia</em> is being served over the World Wide Web, all entries must eventually be formatted in the HTML (HyperText Markup Language) document format for delivery over the web. This is the formatting language that controls the way text, graphics, and links are displayed in web browsers. Entries prepared using other document formats have to be converted to HTML.</p> <p>Normally, the SEP will help authors convert entries prepared in Word, RTF, or LaTeX into HTML. However, authors should be aware that, unless they use LaTeX, the SEP doesn't have the resources to convert especially long entries or entries that have lengthy and detailed mathematical or logical formatting. LaTeX is the preferred format for such entries, since we now use HTML/MathJax, which allows us to embed LaTeX formatting tags within an HTML document (see <a href="https://www.mathjax.org/" target="other">MathJax</a> Authors that use other formats for these kinds of submission may be asked to provide some assistance, either by doing the conversion themselves or by reimbursing the SEP for the extra time its document editors must spend converting and formatting the documents in HTML. (All our documents are now being prepared so that they parse as valid forms of the version of HTML known “XHTML 1.0 Transitional”. This is just HTML 4 written in an XML language.)</p> <p>Please note that there are special instructions to follow for Entry Revision. See the section on <a href="#revision">Entry Revision</a> below.</p> <p> To begin writing an entry, authors should follow our instructions for downloading the sourcefile of the “Entry Template”. (These instructions were sent to you when you accepted your commission and they indicate that you can download the template by logging onto the authors' web interface, for which you have a login ID and password.) Alternatively, you may obtain the template directly from:</p> <ul> <li><a href="entries/template/index.doc">Word Template</a> (.doc)</li> <li><a href="entries/template/index.docx">Word Template</a> (.docx)</li> <li><a href="entries/template/index.tex">LaTeX Template</a> (.tex)</li> </ul> <p> Once the template is downloaded, the author may simply “Open” that file in Word, or use it as the basis of a LaTeX document. </p> <h2><a id="format"></a>4. Entry Format</h2> <p> The following constitute the “canonical” sections of an SEP entry. Each section must be present, though the final Acknowledgments section is optional.</p> <ul> <li><a href="#intro">Introduction (Definition)</a></li> <li><a href="#intlinks">Internal Links</a></li> <li><a href="#main">Main Sections of the Entry</a></li> <li><a href="#Bib">Bibliography</a></li> <li><a href="#Aca">Academic Tools</a></li> <li><a href="#Oth">Other Internet Resources</a></li> <li><a href="#Rel">Related Entries</a></li> <li><a href="#Ack">Acknowledgments</a> (optional)</li> </ul> <p> These are discussed in turn. </p> <h3><a id="intro"></a>Introduction</h3> <p> The Introduction should contain a brief definition of the subject. This may take one or two paragraphs, and if possible, these paragraphs should contain some statement of the subject's interest and significance. The main topics to be covered in the body of the entry may be mentioned here, so that the reader will get some idea of what is to follow.</p> <h3><a id="intlinks"></a>Internal Links</h3> <p> The internal links should be a list of the main sections of the entry, and each item in the list should be a link to that section. The HTML commands needed to do this are included in the template and in the annotated sourcefile.</p> <h3><a id="main"></a>Main Sections of the Entry</h3> <p> The structure and sectioning of the entry is at the discretion of the author. However, SEP sections should be numbered using the following scheme:</p> <blockquote> 1. Section One<br/> 2. Section Two<br/>     2.1 Subsection one of Section Two<br/>     2.2 Subsection two of Section Two<br/> 3. Section Three<br/>     3.1 Subsection one of Section Three<br/>         3.1.1 Subsubsection one of Subsection 3.1<br/>         3.1.2 Subsubsection two of Subsection 3.1<br/>     3.2 Subsection two of Section Three </blockquote> <p>Subsections and subsubsections should not be introduced unless there are at least two of them. </p> <p>We encourage authors to include a Chronology or “Life” section in Biographical entries. Moreover, a “History” section is called for in the discussion of many topics.</p> <h3><a id="Bib"></a>Bibliography</h3> <h4>SEP House Style for Bibliographies</h4> <p> Please use the following bibliographic format:</p> <blockquote> <ul class="hanging"> <li>Dodgson, Henrietta, 1885, “The Evidence for the Existence of Snarks”, <em>Journal of Ornithology</em>, 25(1): 22–44.</li> <li>Hanes, Aristo P., and Wendy Tate, 1999a, <em>Deliverance from Evil Bandersnatches</em>, London: Houghton & Miflin.</li> <li>––– (eds.), 1999b, <em>Papers on Alice</em>, Penrith: Bilgewater Press, 2nd edition.</li> <li>Wunderman, Bill, forthcoming, “Why One Shouldn't Gimble”, <em>Journal of the History of Technical Terminology</em>, first online 13 March 2021. doi:10.3344/xx3ed</li> <li>Madsen, Leslie, 1924, “Slithy Toves”, in Sarah Johnson (ed.), <em>History of Poetry</em>, Cambridge: Cambridge University Press, pp. 302–317.</li> <li>Tate, Wendy, 2002, “Remarks on Boojums”, in William Seeg, Robert Summer, and Dana Talker (eds.), <em>Reflections on the Foundations of Looking Glasses: Essays in Honor of Henry Dodgson</em> (Lecture Notes in Fantasy: Volume 15), Urbana, IL: American Association of English Fantasy Enthusiasts, pp. 410–419; reprinted in Tate (ed.) 2005, pp. 43–53, but page reference is to the original.</li> <li>Tate, Wendy (ed.), 2005, <em>The Provenance of Pure Fantasy: Essays in the Philosophy of Literature</em>, Oxford: Clearwater Press.</li> <li>Terrell, Nicholas, 1888 [1999], “How to Gimble”, <em>Proceedings of the Jabberwocky Society</em>, 32: 1–10; page reference is to the reprint in Aristo Hanes & Wendy Tate (eds.) 1999b, pp. 32–42.</li> </ul> </blockquote> <p> With this style of Bibliography, you can then cite these sources in your main text in the following ways, with placement of parentheses dependent on whether you are referring to the author, the work, or both, respectively:</p> <ul> <li>Terrell (1888 [1999, 7]) claims that snarks gimble on New England ponds in the early spring.</li> <li>It is argued in Hanes 1999a (Ch. 4) that bandersnatches can cause environmental damage.</li> <li>Some authors have claimed that snarks are extinct (Dodgson 1885, 23). </li> </ul> <p> Please note that we strive to eliminate the use of dates that would mislead the reader into thinking that work is published much later. So please avoid such anachronisms as “Plato 1962”, “Locke 1950”, “Confucius 2003”, etc. Instead, in the case where publication dates are not known, please just cite the title of the work. E.g., in a sentence discussing one of Plato's dialogues, you can simply cite “(<em>Parmenides</em>, 132a-b)”, and then list this in the Bibliography as:</p> <blockquote> <ul class="hanging"> <li>Plato, <em>Parmenides</em>, in <em>Plato: Complete Works</em>, John Cooper and Douglas Hutchinson (eds.), Indianapolis: Hackett, 1997.</li> </ul> </blockquote> <p>Similarly, cite sections of Locke's <em>Essay</em> by section number rather than by page number, so that those with other editions can find the passage you cite. So, for example, to cite Locke's <em>Two Treatises of Government</em>, you could refer to it as “Locke 1689” in the text (using the original year of publication), and then include the following listing in the Bibliography:</p> <blockquote> <ul class="hanging"> <li>Locke, John, 1689, <em>Two Treatises of Government</em>, in Peter Laslett (ed.), <em>Locke's Two Treatises of Government</em>, Cambridge: Cambridge University Press, 1960.</li> </ul> </blockquote> <p> And for citing Confucius’ <em>Analects</em>:</p> <blockquote> <ul class="hanging"> <li>Confucius, <em>Analects</em>, Edward Slingerland (trans.), Indianapolis: Hackett Publishing, 2003.</li> </ul> </blockquote> <p> Please also note: (1) The Bibliography section may be divided into subsections such as Primary Literature and Secondary Literature, or References Cited and Other Important Works, etc. and (2) The Bibliography is reserved primarily for <em>refereed</em> material, whether print-based or on the web.</p> <h4>Citations to Online Materials</h4> <p> Citations to online materials require special handling. If a journal article appears in an electronic journal that isn't printed, then a full URL should be identified. E.g., you would reference Alexander George's entry in the <em>Philosopher's Imprint</em> as follows:</p> <blockquote> <ul class="hanging"> <li>Chadha, Monima and Shaun Nichols, 2019, “Self-Conscious Emotions Without a Self”, <em>Philosopher’s Imprint</em>, 19(38): 1–16 [<a href="http://hdl.handle.net/2027/spo.3521354.0019.038" target="other">Chadha and Nichols 2019 available online</a>].</li> </ul> </blockquote> <p> However, sometimes an article is primarily in a print-based journal. That journal may have an online version, or the journal may not have an electronic version but instead the author has put a preprint at an archive site or on their own web page. We encourage authors to create links to online versions of refereed, published material, even if the only version online is a preprint of something that has been published. In these cases, a URL need not be identified explicitly (since the print publication information will suffice), but a specially annotated link should be included, as follows: </p> <ol type="a"> <li>Links which lead to online versions of a published paper or book at the <em>publisher</em>'s website, should be annotated “[Available online]”. These are independent archival versions, and any changes to the articles must conform with the policies of the publisher. Note that the SEP accepts links only to material that is freely available on the web.</li> <li>Links which lead to online preprints of a published paper at an <em>independent</em> archive site should be annotated “[Preprint available online]”. Since the preprint site is an independent archive, the author must conform to their policies for making changes to the preprinted articles.</li> <li>Links which lead to online preprints or reprints of a published article at the <em>author</em>'s website should be annotated “[Preprint available from the author]” or “[Reprint available from the author]”, respectively. This applies even to PDF reprints sent to the author from the publisher and hosted on the author's site, or scanned versions which the author has made of material published elsewhere. The reader should know that this is not an independent “archival” version. In cases where it is unclear whether the author's web site is serving a preprint or a reprint, the default annotation should be “[Preprint available from the author]”.</li> </ol> <p>None of the above applies if the article to be cited is not published or forthcoming in a refereed journal. In such cases, if the online material is simply self-archived (possibly on a preprint site such as arXiv.org or on the author's home page), then the citation information for references to those articles should be put into the Other Internet Resources section of the entry, possibly in a special “Preprint” section.</p> <h4>How to Cite SEP Entries in the Bibliography</h4> <p> Sometimes an author will have occasion to cite another SEP entry in the Bibliography, as opposed to just listing other SEP entries in the Related Entries section. (For example, if an author quotes a passage from another SEP entry.) Proper citation of SEP entries in the Bibliography should follow our citation guidelines, which indicate that one should cite only an “archived” version of an SEP entry. To cite an SEP entry in your Bibliography, such as Sukjae Lee’s entry on Occasionalism, you would list it as follows:</p> <blockquote> <ul class="hanging"> <li>Lee, Sukjae, “Occasionalism”, <em>The Stanford Encyclopedia of Philosophy</em> (Fall 2020 Edition), Edward N. Zalta (ed.), URL = <<a href="https://plato.stanford.edu/archives/fall2020/entries/occasionalism/">https://plato.stanford.edu/archives/fall2020/entries/occasionalism/</a>>.</li> </ul> </blockquote> <h3><a id="Aca"></a>Academic Tools</h3> <p>This section will be generated automatically by the SEP system. Authors need not add any content to this section.</p> <h3><a id="Oth"></a>Other Internet Resources</h3> <p> The author should cite material on the web that is of excellent value but which may not have undergone a referee process. The author serves as referee for these materials (and our subject editors will referee these choices). The items listed in this section can be segregated into subsections, such as:</p> <blockquote> <strong>Online Manuscripts</strong> <br /> … <br /> <strong>Websites</strong> <br /> … </blockquote> <p> To complete this section, authors are encouraged to conduct an online search of the web for webpages and websites with <em>high-quality, academic content</em> on the topic in question. Such webpages and websites should be written and maintained by qualified individuals having a clear expertise on the topic. The task of finding such external websites is made considerably simpler by using one of the premier search engines which rank sites on the basis of the number of links to them on the web (i.e., these links are like web citations). Here are some useful ones:</p> <blockquote>  <a href="http://www.google.com/" target="other">Google</a> </blockquote> <p> Please do not create links to websites that are not maintained by qualified individuals. In addition, authors should <em>not</em> link to their own homepages or to their own list of online publications, though if you have an online publication that is relevant to your topic, it may be appropriate to include a link to it along with other online papers that are relevant to the topic. (Remember that the Bibliography section is reserved for refereed publications and so if your online paper has also been refereed and published somewhere, it should be included in the Bibliography, if cited in the body of your entry, and not in the Other Internet Resources section.) Again, our subject editors will check that self-citations are within the bounds of propriety.</p> <p> Finally, the SEP prefers not to create links to websites or webpages that are behind subscription walls, since this disenfranchises those of our readers who cannot afford to pay the price of admission. So please confine the links you create here to “open access” resources.</p> <h3><a id="Rel"></a>Related Entries</h3> <p> Please list the names of the most important concepts and philosophers that occur in your entry. You may list keywords that do not appear as topics in our Table of Contents if you feel that they are important. We are running software which will notice the discrepancy and alert the Editor. A decision will be made whether or not to include a new entry on that topic. If we decide that the topic is too specialized or otherwise inappropriate for the <em>Encyclopedia</em>, we will eliminate this keyword from your list in the Related Entries section.</p> <h3><a id="Ack"></a>Acknowledgments</h3> <p>This section is optional. A short paragraph thanking those who contributed to the high quality of the entry is in order, however.</p> <h2><a id="footnotes"></a>5. The Use of Footnotes</h2> <p> Footnotes may be included. They can often help to shorten the main page of the entry to make it more readable. Please note, however, that they should not be used solely for citations, or even lists of citations. All citations should be included in the main text in parentheses, in the following format: (Author Year, page). Multiple citations should be separated by a semicolon.</p> <p> Please note: If you are <em>revising</em> your entry, and you want to add or delete a footnote, you do not need to renumber the footnotes by hand. We have a script which will do this automatically. Please simply bring it to our attention and we renumber the notes for you. </p> <h2><a id="symbols"></a>6. The Use of Special Symbols</h2> <p>Modern web browsers can now support most Unicode characters. So most of the characters used in Word and LaTeX can be converted to similar characters in HTML. There are some exceptions, however. In general, when writing an SEP entry in Word or LaTeX, it is best to stick to well-known and widely used symbols.</p> <p> If you have decided to write your entry in HTML, then as you read the final section below, note the subsection on Using Special Characters.</p> <h2><a id="writeHTML"></a>7. If You Choose To Write Your Entry in HTML (Optional)</h2> <p> We have adopted the “XHTML 1.0 Transitional” markup language as the standard for formatting <i>Encyclopedia</i> entries. If you choose to write your entry in HTML, you must submit a file that parses as valid XHTML 1.0 Transitional, according to the validating service at:</p> <ul> <li><a href="http://validator.w3.org/">http://validator.w3.org/</a></li> </ul> <p>It is far more work for us to fix broken HTML than it is to convert Word or LaTeX documents to HTML. So, unless you are confident that you can produce HTML that is clean and internationally compliant, we recommend that you use Word or LaTeX. </p> <p>For those who choose to submit an HTML sourcefile, you have two options: (a) write the document in raw HTML without the assistance of an HTML-editor, or (b) use an HTML-editor to graphically edit and format your document. In either case, you will need to download either our <a href="entries/sample/sample.tgz">Tar/Gzipped Annotated Sourcefiles</a>, or the <a href="entries/template/index.html">HTML Entry Template</a>. The Annotated Sourcefiles include “HTML comments” that explain the formatting, and include sample content that will have to be replaced by your own content. The Entry Template, by contrast, has no annotations or sample content. Once you download, unzip, and untar the Sourcefiles, or download the Entry Template file, you can open the HTML files in a plain text editor or a graphical HTML-editor and begin editing. (Note: if you want to see the annotations in the annotated sourcefiles, these will have to be opened in a plain text editor, for the HTML formatting code makes the comments invisible when rendered by graphical HTML-editing systems.) </p> <h3><a name="sup-links">Linking from the Main Entry to Supplementary Documents</a></h3> <p> Note that it is easy to create a link from your main entry to supplementary documents containing overly technical or scholarly material that would interfere with the presentation of the main ideas. To create a link from the main document to a supplementary document, suppose that the main document is entitled “index.html” and the supplementary document is entitled “supplement.html”. Now suppose that at the end of a paragraph, you wish place a labeled link to the supplementary document. Here is what the link might be displayed as:</p> <blockquote> ... . We discuss this last point in further detail in the following supplementary document: <blockquote> <a href="entries/sample/supplement.html">Supplement on [Title of Supplement]</a> </blockquote> </blockquote> <p> Authors using an HTML-editor will have to use the functions provided by their software to create such a link. However, authors who can edit their HTML sourcefiles directly would insert the following HTML code in order to produce this link to the supplementary document:</p> <blockquote> ...in the following supplementary document. <br /> <blockquote><br /> <a href="supplement.html" id="return-1">Supplement on [Title of Supplement]</a><br /> </blockquote> </blockquote> <p> Note that this can be done in other places in your main document, if you have more than one supplementary document. (You will have to name your supplements as “supplement1.html”, “supplement2.html”, etc.) You can find the sourcefile for the supplement template <a href="entries/sample/supplement.html">here</a> (use the View Source function of your browser after following this link).</p> <h3><a name="spe-cha">Using Special Characters</a></h3> <p> We allow the use of widely supported Unicode characters. We have drawn up a page of symbols, which we believe to be widely supported among current web browsers, though many do not work with older browsers and/or older operating systems (and this is noted at the top of every entry in the SEP which uses one of these special characters). </p> <p> So, if you need special punctuation characters, special accented Latin characters, Greek characters, logic and/or mathematical symbols, Polish characters, etc., please visit our page:</p> <blockquote> <a href="./symbols/entities.html">Widely Supported XHTML/HTML4 and Unicode Characters</a> </blockquote> <p> Note that you can use the formatting code that appears in either the 2nd or 3rd column of this table in your HTML source file. </p> <p> There are various tricks one can use in HTML for formatting these symbols in the complicated ways needed by logicians and mathematicians. For example, to get a web browser to display the word “Gödel” properly, note that you will find “ö” (= “&#246;”) in the list of Latin Characters (in the section by that name on the webpage listed above). It indicates that you can get the browser to display the umlauted character by placing either the character entity “&ouml;” or “&#246;” in your text. Thus, to produce the word “Gödel”, you place the expression “G&ouml;del” or “G&#246;del” in your HTML source file.</p> <p> We have set up table that shows you the HTML codes to use for more sophisticated kinds of mathematical and logical formatting. Please have a look at:</p> <blockquote> <a href="./symbols/math.html">Mathematics HTML Sampler</a> </blockquote> <p> As another example, note that the “set membership” relation ∈, the logical symbols ∀, ∃, and &equiv;, and the Greek symbol φ can all found in the list of symbols on our page <a href="./symbols/entities.html">Widely Supported XHTML/HTML4 and Unicode Characters</a>. Now to produce the formatted line:</p> <blockquote> ∃<em>x</em>∀<em>y</em>(<em>y</em>∈<em>x</em> &equiv; <em>y</em>∈<em>A</em> & φ) </blockquote> <p> use the following sequence of HTML markup in your entry, where <em> … </em> is the formatting environment for italics:</p> <blockquote> &exist;<em>x</em>&forall;<em>y</em>(<em>y</em>&isin;<em>x</em> &equiv; <em>y</em>&isin;<em>A</em> &amp; &phi;) </blockquote> <p> In some cases, however, the symbol you will need is not widely supported in web browsers. Therefore, if you do not find the symbol you need on our page <a href="./symbols/entities.html">Widely Supported XHTL/HTML4 and Unicode Characters</a>, you can check our page:</p> <blockquote> <a href="symbols/">Special Symbols Not Widely Supported</a> </blockquote> <p> For example, we have produced the following graphics for the “dproves” and the “not-dproves” signs, respectively:</p> <blockquote> <img src="symbols/dproves.jpg" alt="dproves" /> <br /> <img src="symbols/not-dproves.jpg" alt="not dproves" /> </blockquote> <p> These symbols can be found on the Special Symbols Not Widely Supported page and you can download them onto your machine from there. Follow the links to “dproves.jpg” and “not-dproves.jpg” in the table of special symbols. You can then save those graphics onto the drive of your local computer.</p> <p> If you are using an HTML-editor to create your entry, then you simply use your software's “add image” (“add graphic”) function to place these graphics on a line in your entry. However, those authors who are editing their HTML sourcefiles directly should use the following guidelines. To produce the formatted line:</p> <blockquote> <em>A</em> <img src="symbols/dproves.jpg" alt="dproves" /> <em>B</em> </blockquote> <p> place the file “dproves.jpg” into the directory containing your HTML entry and use the following HTML code in your entry:</p> <blockquote> <em>A</em> <img src="dproves.jpg" alt="dproves" /> <img src="dproves.jpg" alt="dproves" /> <em>B</em> </blockquote> <p> Note that you will not need to transfer the graphics to the same directory on plato.stanford.edu when you transfer your entry to us — the first time you view your file on our server after uploading it, our software will recognize the links to our graphics and it will automatically install copies of the needed graphic files into your upload directory.</p> <p> You may use any graphic found in our symbols page in this way. If you need a symbol not found on that page, write to the editor—symbols are easily constructed.</p> <h3><a name="for-rel">Formatting the Related Entries Section in HTML</a></h3> <p> If you would like to create the links to related entries yourself, then here is how you proceed. (This only works for published entries, since you won't be able to discover the canonical directory (folder) names for projected but unpublished entries.) Say you are writing an entry on Frege and you wish to create a link to the entry on Davidson in the Related Entries section. The line in the HTML sourcefile which does this will look like this:</p> <blockquote> <a href="../davidson/">Davidson, Donald</a> </blockquote> <p> The part of the code which creates the link is the bit:</p> <blockquote> <a href="...">...</a> </blockquote> <p> You fill in the first ellipsis with the location of the file you want to link to, and you fill in the second ellipsis with the label on the link you want a web browser to display. In the example, the location of the entry on Davidson is “../davidson/”. (The string “davidson” here is the canonical name of the directory containing the entry on Davidson.) This is server code which tells the browser to request the default file in the directory “davidson” which appears in the <em>parent</em> directory (“../”) of the current directory. In our example, since we are writing on Frege, we assume that the current directory contains the entry on Frege and so if the browser goes to the parent directory (which is the “entries” directory containing all the entries) and then down to the “davidson” directory, it will find the default file.</p> <p> Now you can find out the canonical name of the directory containing the entry on Davidson by visiting the entry on Davidson in the <i>Encyclopedia</i>. When you reach it, you will see that the URL is:</p> <blockquote> https://plato.stanford.edu/entries/davidson/ </blockquote> <p> The last field of this string is “davidson”, and that is the canonical name of the directory containing the entry on Davidson.</p> <h3><a name="for-foot">Formatting Footnotes in HTML</a></h3> <p>SEP entries are formatted so that the footnotes are placed into a separate HTML file called “notes.html” and linked into the text. The file notes.html is placed into the same directory on plato.stanford.edu as the entry. If you are using an HTML-editor to create your entry, then you will need to use the functions provided by the editing software in order to create footnotes as links to a footnote file. </p> <p> However, for those authors who are editing their HTML directly in order to create links from the text to the footnotes, here are some guidelines to follow. Suppose you want to add footnote number <em>x</em> at a point in the text:</p> <blockquote> ...some text.<sup>[<a href="#note-x" id="ref-x">x</a>]</sup> </blockquote> <p> To produce this in your HTML sourcefile, use the following HTML code at the point in the text where the footnote should occur: </p> <blockquote> ...some text.<sup>[<a href="notes.html#note-x" id="ref-x">x</a>]</sup> </blockquote> <p> This will place “[x]” as a superscript in the text, with “x” a link to the place in the notes.html file identified as id="note-x" (see below). The id="ref-x" marks the spot in the current file to which a “Return” link from the notes.html file will return (again, see below). Then, create another HTML file named “notes.html” and in that file you will try to produce something that looks like this:</p> <blockquote> <a href="#ref-x">x.</a> Body of the footnote goes here.… </blockquote> <p> To produce this line in the notes.html file, you would add the following HTML code:</p> <blockquote> <div id="note-x"><br /> <p> <br /> <a href="index.html#ref-x">x.</a> Body of the footnote goes here.…</p><br /> </div> </blockquote> <p> This will start a new paragraph and start the footnote with the symbol “x.” (“x.” will be a link back to id="note-x" in the main index.html file; the id="note-x" identifies the place in the notes.html file to which the footnote in the main text will be linked). Note: Users of the <em>Encyclopedia</em> can always use the “Back” or “Return” button on their browsers to get back to the text.</p> </div>  <div id="footer" class="scroll-block"> <div id="footer-menu"> <div class="menu-block"> <h4><i class="icon-book"></i> Browse</h4> <ul role="menu"> <li role="menuitem"><a href="contents.html">Table of Contents</a></li> <li role="menuitem"><a href="new.html">What's New</a></li> <li role="menuitem"><a href="https://plato.stanford.edu/cgi-bin/encyclopedia/random">Random Entry</a></li> <li role="menuitem"><a href="published.html">Chronological</a></li> <li role="menuitem"><a href="archives/">Archives</a></li> </ul> </div> <div class="menu-block"> <h4><i class="icon-info-sign"></i> About</h4> <ul role="menu"> <li role="menuitem"><a href="info.html">Editorial Information</a></li> <li role="menuitem"><a href="about.html">About the SEP</a></li> <li role="menuitem"><a href="board.html">Editorial Board</a></li> <li role="menuitem"><a href="cite.html">How to Cite the SEP</a></li> <li role="menuitem"><a href="special-characters.html">Special Characters</a></li> <li role="menuitem"><a href="tools/">Advanced Tools</a></li> <li role="menuitem"><a href="accessibility.html">Accessibility</a></li> <li role="menuitem"><a href="contact.html">Contact</a></li> </ul> </div> <div class="menu-block"> <h4><i class="icon-leaf"></i> Support SEP</h4> <ul role="menu"> <li role="menuitem"><a href="support/">Support the SEP</a></li> <li role="menuitem"><a href="support/friends.html">PDFs for SEP Friends</a></li> <li role="menuitem"><a href="support/donate.html">Make a Donation</a></li> <li role="menuitem"><a href="support/sepia.html">SEPIA for Libraries</a></li> </ul> </div> </div>  <div id="mirrors"> <div id="mirror-info"> <h4><i class="icon-globe"></i> Mirror Sites</h4> <p>View this site from another server:</p> </div> <div class="btn-group open"> <a class="btn dropdown-toggle" data-toggle="dropdown" href="https://plato.stanford.edu/"> <span class="flag flag-usa"></span> USA (Main Site) <span class="caret"></span> <span class="mirror-source">Philosophy, Stanford University</span> </a> <ul class="dropdown-menu"> <li><a href="mirrors.html">Info about mirror sites</a></li> </ul> </div> </div>  <div id="site-credits"> <p>The Stanford Encyclopedia of Philosophy is <a href="info.html#c">copyright © 2024</a> by <a href="https://mally.stanford.edu/">The Metaphysics Research Lab</a>, Department of Philosophy, Stanford University</p> <p>Library of Congress Catalog Data: ISSN 1095-5054</p> </div>  </div>  </div>   <script> $('.dropdown-toggle').dropdown(); </script> </body> </html>