Wikipedia talk:Manual of Style (footnotes)/Archive 5

From Wikipedia, the free encyclopedia

Archive 1Archive 3Archive 4Archive 5Archive 6Archive 7Archive 10

Very confusing and unorganized page

This page needs a lot more clarity, and needs to be simplified. It is very hard to see what's going on. —The preceding unsigned comment was added by Danianjan (talkcontribs) 01:06, 27 June 2006 (UTC)

Overview of major changes this month

Disclaimer: I have very little technical knowledge of Cite.php, so I don't know the relative ease or difficulty in making these changes. I am, however, interested in improving and using the footnote and citation systems in Wikipedia. --J. J. 10:07, 29 June 2006 (UTC)

Purpose

User:NikoSilver initiated a "<ref> function" poll here from June 7th14th. For those new to the discussion, hopefully this section will help clarify and summarize the issues voted on and where we go from here. While the majority of voters support all of the proposals (33 to 5), I've found the extensive discussion to be a more relevant guage for each of the issues; this is why I've opted to summarize the discussion instead of the list of proposals as a whole.

Cite.php has become a huge project, so it's been necessary to illuminate, aggregate, and create a lot of bugs this month. For the sake of simplification (and my own sanity), I've had to leave some of the minor issues and bugs out of this summary. This is, after all, only a guideline, not a policy.

As a next step, I think it would be good to create a detailed, ongoing, scratch sheet /List of outstanding ref bugs and issues. This would help to centralize issues (big and small) scattered throughout these talk archives; it could also aggregate "forgotten" problems mentioned in Wikipedia:Footnotes#Disadvantages and future improvements and Meta:Cite/Cite.php#Issues (and its talk page). To get started on this list, take a look at this MediaZilla query: "MediaWiki extensions" > "Cite" with defaults for other options.

Procedure

The summary is ordered basically the same as the top to bottom discussion on this talk page, as well as the designated comments from this main article and Meta Cite.php pages. For those active in the poll, please go ahead and fix any obvious mistakes I may have made or use the "General responses" section at the end for more subjective opinions; I've marked my misunderstandings in italics. Also, instead of another messy round of debate below each DISAGREE/DISCUSSION point, I think extensive discussion should be centered around the linked bugs for most of the issues mentioned (6B below may be an exception, in which case it would probably be worth aggregating related debates on a /Same ref repetition issues subpage; e.g. Operation Auca discussion). Hopefully this will take us one step closer to integrating this summary into the main Footnotes article (and related Meta/Citations articles) depending on bug states.

Terminology

Basically, footnotes are a numbered list of supporting comments and/or citations added to the bottom of an article and referenced with a number in the main text (this is both a CMS and MLA practice, although the latter emphasizes Harvard references; can someone verify this for me? --J. J.). On paper, these would actually be called endnotes; this is why the footnotes section is often generically labeled ==Notes==. There are various opinions on whether or not citations/references should be mixed with footnotes/comments in the same section. While still functional in old articles, the use of templates for footnotes (Wikipedia:Footnote3) has deprecated. Templates are still actively used, however, with Harvard references (shows short text in article instead of just a numbered footnote style; see the Harvard link above).

List of issues mentioned

  1. Wikipedia:Footnotes#Disadvantages and future improvements is similar to the proposals and comments in this poll, but it needs to be updated. See particularly the mentioned bugzilla:5810 (still open): <clearrefs/> possibility when wanting more than one Notes section. Bug 6271, mentioned below, is a "grouping" work around to this problem.
  2. Meta:Cite/Cite.php#Issues also mentions several open bugs that haven't been mentioned here. These are just a few: bugzilla:2257 template numbering; bugzilla:4529 ref can't take template arguments; bugzilla:5567 should have id and name (for legacy); Meta:Talk:Cite/Cite.php#Suggestion:_sub-reference_attribute_for_ref_tags is related to bug 5885 below; FYI, Ævar's (the Cite creator) contributions are sparse.
  3. REJECTED 1 (but bug still open): Mix in one list, but differentiate footnotes and Harvard references e.g. <ref harv="(Smith 2003)">Smith, John (2003). ''Some Book Title'' Press: Nowhere.</ref>. While rejected in the poll, the related bugzilla:6272 is still open. (Correct me if I've misinterpreted this one. --J. J.)
  4. REJECTED 2: Have choice to use, exclusively, either footnotes style or Harvard style in one article.
  5. Discussion 1 (DISAGREE, but bug still open): Separate <ref> and e.g. <note> sections. DISAGREE, although it is AGREED to support bugzilla:6271 which proposes designating two or more <referencesF /> "groups". (I'm not clear if this proposal has agreed to support the bug for footnotes only, or if the intent is to separate footnotes (referencesF) and full bibliographic references (referencesB). Shouldn't there be a separate bug for the top-to-bottom reference grouping ,e.g. Comparison of operating systems? --J. J.)
  6. Discussion 2 (RESOLVED bug, but comments): Ability to turn off superscripted footnotes at will (using e.g. parenthesis or brackets around the numbers in normal text instead). (While resolved, I think bugzilla:6310 needs to explain how this is done with CSS or editing the Cite.php file. --J. J.)
  7. Discussion 3 (RESOLVED bug): Ability to include comment code within a reference, e.g. <ref>This is shown, <!--This is not--> this is shown, too.</ref>. Bugzilla:5384 resolved (as evidenced by my successful test).
  8. Discussion 4 (DISAGREE, but but still open): (A) Ability for hard returns in the edit box to affect final results within <ref> tags (instead of having to use <br>). (B) To allow easier reading within the edit box, have the parser ignore the [enter]s before and after the ref tags (see the commenting technique and spacing technique for details and a couple of satisfying workarounds). DISAGREE for both; they would require major changes to MediaWiki edit box code, although note the workarounds for 4B. Even though this group disagrees, bugzilla:6311 is still open.
  9. Discussion 5 (AGREE, bug still open): Ability to use refs in templates. See bugzilla:6312 for details.
  10. Discussion 6 (AGREE, bugs still open because of code complexity): (A) Ability to move text within selective refs to a central location, similar to the old Footnote3 mentality (see #Do_want). Bugzilla:5997 includes 6A, as well as (B) Fixing non-1st ref content (archived discussion); Bugzilla:5885 is specific to 6B; by consensus, this is one of the most important unresolved issues. Meta:Talk:Cite/Cite.php#Suggestion: sub-reference attribute for ref tags is a similar, alternative bug (although I don't think there is a MediaZilla bug for it yet).

General responses

Wonderful job! Only one important comment regarding the poll: All points have been agreed by 33vs5 users. The poll is in #Poll, and not in discussion. Those "disagree" comments were posted by users after the initiation of the poll. I apologize for rushing the poll and not giving the chance to these users to express their disagreement, but I guess the end result justifies my impatience. JJ, could you please amend your own text accordingly? Also, a suggestion: care to make ===Resolved=== and ===Rejected=== sections to get rid of those from the other ===Non-Resolved=== issues?:NikoSilver: 21:28, 29 June 2006 (UTC)

Oooh. Well, silly me. Guess I need to polish up on my WP poll-reading skills; kind of sad that I managed to miss the point after reading through everything so thoroughly. However, Wikipedia:Straw polls reads, "Wikipedia is not an experiment in democracy. Its primary method of finding consensus is discussion, not voting." I'll see what I can do to revise; we should be getting paid for this, Niko ;-) --J. J. 04:33, 30 June 2006 (UTC)
I've decided to keep the summary mainly the way it is with a couple of exceptions. I've added a justification to the end of the first paragraph of Purpose. I've also added <del> strikeouts to the resolved issues (only two of them). Even though they've been voted on, several of the "resolved" and "rejected" ideas still have active bugs and/or are still being discussed. Leaving the list the way it is makes it easy to refer to the issues by number, too. --J. J. 13:54, 6 July 2006 (UTC)

Inline references suck!

Holy f**king cow! What happened? Guys, I don't know how you managed to get consensus on this issue, but inline references utterly suck! They make it extremely difficult to author articles, they make it hard to maintain articles, they make it difficult to reference the same work more than once! This has got to be the most horrid style possible for managing references, and I am utterly disappointed to come to this page, to discover that its somehow been promoted as official policy! WTF! Who did this S**t? I'm sorry, but there is so much B.S. on W.P. already, that I certainly don't want the B.S. percolating upwards into the reaches of WP policy! Sorry for the foul language and exclamation marks, but really, this one takes the cake! Get a grip, folks, revert, and ban the inline-refrence style! Arghh! linas 15:15, 2 July 2006 (UTC)

I agree, inline references are a bitch. They make paragraphs look like they're double spaced, and make editors go "huh, wheres the text I wanted to edit" cause theres so much garbage inline. Fresheneesz 20:59, 9 September 2006 (UTC)
Err, what? Could you please be more specific what you mean by "style"? If it's inline citation in general, your complaints are likely to be as effective as beating your head against a brick wall; if it's footnotes in particular, you might note the disclaimer at the top of the page: "N.B. This format is not mandatory; editors are free to use a different method. See How and where to cite sources." Kirill Lokshin 15:43, 2 July 2006 (UTC)
Kirill, I think it is clear that Linas is referring to Cite.php and the <ref>Really long list of authors, probably five or six or something (XXXX) This is a really long reference to a paper that was published in the conference proceedings of the 6th international conference of the association of foo bar, XXXX, pp. 1024-1030</ref> - FrancisTyers · 16:16, 2 July 2006 (UTC)
Well, it would be even worse to cite something like that Harvard-style (since you'd not only have the really long list of authors in the markup, but in the final article text as well), so I'm not sure what he's proposing as an alternative. Kirill Lokshin 16:20, 2 July 2006 (UTC)
I'm not proposing harvard style, although what you describe wouldn't be a problem, e.g. (Firstguy et al. XXXX) and then in the references section you can give the full list. My complaint is solely that it is currently impossible with Cite.php to put full text references outside the body of the article, e.g. in a References or Notes section, like with Footnotes3. - FrancisTyers · 16:59, 2 July 2006 (UTC)
Well, that depends on what you mean by "full text". You're correct insofar as there's no intuitive way to reduce the in-text references to single tags (e.g. <ref name="foo-123"/>) in all cases (although I do recall that someone had found a clever, if complicated, way of doing so); but neither is there anything preventing the use of short-form citations in footnotes (e.g. <ref>Smith et al., 123.</ref>) with the bulk of the reference information contained in a separate "References" section. Kirill Lokshin 17:08, 2 July 2006 (UTC)
Nothing prevents you if you discount the almost unbearable ugliness of the resulting layout (a pseudo-footnote to point to a Harvard reference that is not directly linked to the citation itself... yuck! It's hard to imagine anything uglier).
Btw. For an example of a way to group references and used named tags, see User:CitationTool/Hybrid referencing. It's not perfect, until the MediaWiki developers act on a patch I've provided. But it's pretty good for some situations. It will be better when we can do the same thing, but with references at bottom. LotLE×talk 17:22, 2 July 2006 (UTC)
Considering that the format I suggested is the one recommended by the Chicago Manual of Style for footnotes, I suspect the ugliness may be a matter of opinion ;-) Kirill Lokshin 17:41, 2 July 2006 (UTC)
Do you have evidence of that? I don't have a Chicago Manual, but I certainly can't recall it ever recommending such a dreadful thing. I agree about the form of the short citation, which is just Harvard referencing. But putting a Harvard ref in a (pseudo-footnote)?! LotLE×talk 17:51, 2 July 2006 (UTC)
Oh, sure. From the fifteenth edition: "The short form, as distinct from an abbreviation, should include enough information to remind readers of the full title or to lead them to the appropriate entry in the bibliography..." (16.41), "The most common short form consists of the last name of the author and the main title of the work cited, usually shortened if more than four words..." (16.42), and "First note citation in a work with full bibliography: 1. Doniger, Splitting the Difference, 23." (16.3, emphasis theirs). The fourteent edition, if I recall correctly, suggested omitting the title and only using the author name and page number.
(A possible source of confusion: I intended the number above to be a page reference, not a publication year. Sorry if that wasn't very clear.) Kirill Lokshin 18:19, 2 July 2006 (UTC)
I think that part of the issue, incidentally, is the proliferation of templates like {{cite book}}. I can see where heavy use of them would cause the resulting layout to appear utterly absurd. For those of us who just write up the references by hand, however, it looks much simpler, as there's no need to point from templates to other templates. Kirill Lokshin 17:44, 2 July 2006 (UTC)
I don't understand the question. The very first example on this page, Wikipedia:Footnotes, is an example of an inline reference. I am trying to say that not only are inline references bad, but they are so bad that they should be banned from WP. There could not possibly be a poorer design for adding references to a text. Thus, I was utterly aghast to find that somehow this style had become "recommended". I used swear-words, because this idea is so mind-bogglingly bad that I was left speech-less, jaw-agape, unable to find any other words that captured my feelings. linas 16:08, 2 July 2006 (UTC)
I don't think you'll find much support for your view, frankly. Despite the occasional flaws in implementation, the inline reference system has finally allowed us to begin working on properly sourcing all of the various things in Wikipedia without depending on fragile and difficult-to-use template schemes. Kirill Lokshin 16:11, 2 July 2006 (UTC)
I wholeheartedly support your view Linas, unfortunately I think your stand-off-ish approach will cause more problems than it will solve :) Try and enunciate your complaints in slightly more reserved language ;) - FrancisTyers · 16:13, 2 July 2006 (UTC)

The stand-off seems unavoidable. Clearly, 30 people voted for this thing, and five against. To reply to Kirill, template schemes are neither fragile, nor are they difficult to use. For example, in Principle of least action, we had

...is often given to [[Pierre Louis Maupertuis]], who wrote about it in 1744{{ref|Mau44}} and 1746{{ref|Mau46}}. However, scholarship indicates that ...

I find the above to be eminently readable and editable. The markup is robust against error; there's nothing fragile about it. Its certainly not difficult to insert a reference. Then some anonymous editor did a drive-by conversion of the above, and turned it into:

...is often given to [[Pierre Louis Maupertuis]], who wrote about it in 1744<ref name="mau44">P.L.N. de Maupertuis, ''Accord de différentes lois de la nature qui avaient jusqu'ici paru incompatibles.'' (1744) Mém. As. Sc. Paris p. 417.</ref> and 1746<ref name="mau46">P.L.N. de Maupertuis, ''Le lois de mouvement et du repos, déduites d'un principe de métaphysique.'' (1746) Mém. Ac. Berlin, p. 267.</ref>. However, scholarship indicates that ...

I can't begin to imagine why Kirill thinks that the later is less fragile, or is easier to use, than the former. Its just begging for typesetting errors, grammatical errors, poor flow. Its just plain eye-throbbingly difficult to read. Whenever one has something difficult to read, it will lead to errors and mistakes. Reference markup should be easy, clear, simple to use and convenient for the author. It should not be some machine-like monstrosity invented by some computer programmer who doesn't actually author articles, and has no sense of usability or ease-of-use issues. linas 17:18, 2 July 2006 (UTC)

You're discounting the other portion of the citations here, of course. For your examples, they would be:
{{note|Mau44}} P.L.N. de Maupertuis, ''Accord de différentes lois de la nature qui avaient jusqu'ici paru incompatibles.'' (1744) Mém. As. Sc. Paris p. 417. {{note|Mau46}} P.L.N. de Maupertuis, ''Le lois de mouvement et du repos, déduites d'un principe de métaphysique.'' (1746) Mém. Ac. Berlin, p. 267.
versus:
<references/>
The fragility in the first scheme is evident if the order of the two cited sentences is switched. Since the {{ref}} and {{note}} templates will no longer have the same ordering, the resulting footnote numbers will lead the reader to the incorrect citation. This, in my view, is far worse than any amount of inconvenience to the editors. Kirill Lokshin 17:41, 2 July 2006 (UTC)
I'm not discounting the other portion. There is a major advantage to having all of the references in one place. For one, it allows for an eventual conversion to bibtex, which is the defacto standard used elsewhere on the net (see for example, CiteSeer, ACM, CiteBase, Google Scholar.) I believe the bibtex standard is what WP should be using, instead of trying to reinvent something, badly. In particular, proper bibtex citation in WP would allow these other major citation engines to actually find and reference WP articles.
I don't understand the complaint about numbering: this sounds like a bug in the code. The answer is to fix the bug in the code, instead of forcing the user to go through some cumbersome contortions to work around it.
The separation between content and presentation has been the underlying principle of computer authorship for 40 years. Its the principle behind HTML, and SGML, and BookMaster another decade before that, and is carried forward by newer concepts, like Cascading Style Sheets. The inline-reference style is a big step backwards in technology. linas 18:08, 2 July 2006 (UTC)
BiBTeX ftw! - FrancisTyers · 18:56, 2 July 2006 (UTC)
It's not a feature of the code, fundamentally, because the various {{note}} templates aren't linked in any way. We can either number the footnotes according to the order they appear in the article body, or according to the order they're listed in the "Notes" section; but we cannot do both. Kirill Lokshin 18:19, 2 July 2006 (UTC)

I created my own little sandbox on my user page (see new section below) to play with these two methods of notation (citation/referencing/sourcing/whatever). Feel free to read it and add some more examples. I may be missing some key advantages or disadvantages to either one of them that don't show up in my meager little experiment. From what I could tell, I couldn't find any solid advantage to the bookcite method: except for its optional strutcured bibliographic record implemntation. Though many find that too cumbersome, it can be easily mixed with the unstructured freeflow bibliographic record. The hybrid proposal metnioned above allows the use of the structured bibliographic record within the Cite.php solution. —The preceding unsigned comment was added by Cplot (talkcontribs) 16:42, 2 Jul 2006 (UTC)

I heartily agree. The content of the references should be in the References section, where it is rendered. — Omegatron 00:14, 3 July 2006 (UTC)
I would reservedly agree with this if we had a system that a) preserved numbering order if things get shuffled around and b) made it clear there was an error (<strong class="error"> works) if the reference got divorced from its referent. In the template system, there is neither, and so screw-ups routinely happen and aren't spotted for ages, which makes them a nightmare to fix. More than once I've had to spend a half-hour or more digging through page history to figure out where a {{ref}} was supposed to point to. —Simetrical (talk  contribs) 20:24, 3 July 2006 (UTC)
Honestly, I just don't understand the "numbering problem". If the programmers can make <ref> have correct numbering, then why in the world would they be unable to make {{ref}} have the correct numbering? Why not just go back and fix {{ref}} to number correctly? For Pete's sake, the only difference is the shape of the brackets !! linas 13:33, 6 July 2006 (UTC)
Let's try this explanation again, shall we:
  • <ref> numbers footnote references in the article correctly. The footnotes at the bottom are automatically listed in the corresponding order when <references/> is added.
  • {{ref}} numbers footnote references in the article correctly. The footnotes at the bottom are manually listed by adding {{note}} templates. There is no automatic ordering involved in this step; the footnotes at the bottom are numbered exactly as the {{note}} templates are ordered. If the {{note}} templates are in a different order than the actual footnotes in the article, the numbers won't match up.
This really isn't difficult. Kirill Lokshin 15:03, 6 July 2006 (UTC)
The problem is this: no developer currently wants to implement any of these requests. They won't get done until one of the handful of active committers wants to implement them. Simple as that. —Simetrical (talk  contribs) 05:28, 7 July 2006 (UTC)

Look at the bigger picture

Cplot and linas, I've done my best to look through your contributions and respond the the referencing comments and questions you've made in the past week. While I appreciate your fervor and several good ideas, please take the time to read through the recent poll and summary on this talk page. A lot of the issues you mention have been debated for many months on this and similar-topic talk pages. This is why I recommended creating a /List of outstanding ref bugs and issues; no one's commented on that suggestion yet, though.

On a more positive note, I think you've pinpointed two crucial issues to the whole Cite.php system. Cplot summarizes them nicely: "Both methods try to separate presentation from content. But they also both confuse citations, notes and sources."

  1. "Part of what I hope to introduce with this proposal is more separation between content and presentation. By treating nested notations semantically as simply notations regardless of how they're presented (parenthetical, footnote, endnote, cursor hover [sic], etc), we can leave the presentation details to the moment of presentation. The reader can determine through preferences or changing environment settings (e.g., buttons on the top of the page) how much detail is displayed and where it is displayed."
  2. Also at the heart of the issue is clarifying definitions of and procedures for notes, citations, sources, and references; I would even add Wikipedia:Embedded Citations to the list! --J. J. 14:08, 6 July 2006 (UTC)
Thanks for the comment RockOfVicotry. So much of the discussion here and elsewhere seems to be driven by some seemingly minor shortcomings in the Wikimedia software. I haven't looked at what bugs and features have been highly prioritized by the software developers, but from my experience here, sorting out these note, citation, reference and source issues seems the most glaring of all (perhaps I just don't use wikimedia in ways that demonstrate the other bugs). BTW when I mention "cursor hover" I meant what some I think call a tooltip (another way of presenting a note; hover over tooltip to see what I mean).
In terms of the big picture, let me just explain my understanding of the separation between semantic content and presentation (visual and otherwise) as I've come to understand it (coming from my reading of W3 goals and initiatives). So much of the debates here are fueled (as far as I can tell) by presentation concerns. Another way to think about it is in terms of how the reader experiences an article. I may prefer seeing citations parenthetically placed within the main body of the text. Another reader may prefer to have those same citations separated into footnotes (or some other arrangement). Yet another reader, may have no interest at all in verifying the sources and would just as soon not see any citation whatsoever (but may want to see minor qualifiers like this one parenthetically placed in the text). Ideally, with properly designed server and client (i.e., browsers) software. All of those presentation preferences can be handled late in the process: separate from the task of composing and editing that begins the process. So something like the <ref> element could evolve to handle all sorts of these notes. For example, by adding an attribute to it <ref subtext="1"> or <ref subtext="2">, the markup indicates the semantic intent of the editor (how important and integral is this note to understanding the text). I understand all notes to be subordinate to the text. A subtext attribute would permit the author/editor to indicate how subordinate. The other suggestion in my proposal is to add an attribute called source that could be used on various elements such as <ref> <cite>. This way an editor could only need to enter something like <cite sourec="ISBN:0691002606">pp 24-38</cite> and they would be done (wikimedia would help them find and enter that source attribute through some form driven interface). From that simple entry WikiMedia would generate parenthetical reference not or footnote citation depedning on the presentation settings and also automatically add the source to the "Reference List". When the available software adequately supports the separation of semantics from presentation, decisions about presentation can be left until the page is actually assembled. As browsers add support XSLT, these presentation decisions (such as parenthetical or footnote citations) could even be left to the page loading phase.
This is not to say that there are no semantic editing concerns here too. Many have suggested it's confusing to read source markup where the ref element contains long notes or even cite templates in a block of text. Also it's often confusing to click on a "Footnote" section only to correct a footnote, only to find one element: "<references /> in the edit box. Althought these things may be confusing I think those issues are small compared to the problems of maintaining text and its associated subtext when a large group of individuals is collaborating on the project: even more so when many may be new to wikimedia and unfamiliar with the guidelines. I'm actually quite impressed at how well this all works. But I do think it's a very good idea to keep subtext (notes) with the main text in terms of semantic markup. Doing this helps ensure that reordering or deleting blocks of text don't break the references to the subtext.
All the long-term goals aside, we have to work with what's available now. So I've been exploring the features of WikiMedia to try to discern how to best meet the goals of separating semantics from presentation right now and down the line. My essay proposal was a first stab at that. Based on what I see from the software right now, I think it's best to use the ref element (without names) for notes and citations (or possibly Harvard citations inline), combined with a manually arranged "Source List" or "Reference List", probably using Harvard Reference templates or cite templates as documented here (though incompletely).
Nobody likes to maintain reference lists and with some modest improvements in the software, much of the burden for this could be lifted off of the editors. By moving the burden to the software, it also assures a certain level of conformity to policies: policies of structured markup that need conformance as opposed to policies of presentation that could be completely user controlled eventually. I hear over and over again that novice editors are intimidated or confused by the cite and Harvard reference templates. So presenting more automated tools using html forms could improve the process greatly, and even avoid the reentry of the same source every-time it's used throughout wikipedia. Wiki is already becoming the leading repository for encyclopedic content, zoological species database, quotations, dictionary definitions, etc. Why not make it the leading catalogue of referenced sources: streamlining the tasks of editors in the process. Just a few more of my thoughts on the big picture. --Cplot 00:37, 7 July 2006 (UTC)
"I haven't looked at what bugs and features have been highly prioritized by the software developers, but from my experience here, sorting out these note, citation, reference and source issues seems the most glaring of all (perhaps I just don't use wikimedia in ways that demonstrate the other bugs)." See this for a general idea of some of the more serious bugs, and this for a simultaneously over- and underinclusive list of feature requests that the developers may be prioritizing more highly (although that's dicier, because non-devs can change the priority field for some reason). —Simetrical (talk  contribs) 05:28, 7 July 2006 (UTC)

Possible solutions for notes, citations, and sources (and references)

Since I think such a long proposal may become unwieldy on an already lenghty talk page, I decided to move the proposal to my own user domain. I also took the liberty of bringing the comments over to the associated talk page. I hope that's not a faux pas. You're all welcome to come edit away in thie new space. --Cplot 01:53, 3 July 2006 (UTC)

I suppose I should provide some summary of the proposal here. Following this link will take you to the full proposal. Basically I'm trying to think through the disctintions between notations, citations, references and sources. From that analysis I propose two strategies. First to alter the manual of style to to disentangle these issues. Second, to develop a list of feature requests for MediaWiki software developers to make the job of adding and editing content even easier down the line. I think this proposal addresses a lot of the concerns I've seen raised here on this page, which is why I metnioned it here. --Cplot 04:30, 3 July 2006 (UTC)

My observations

Looking at things semantically, a note is just a (typically brief) amount of content, that, while it has a place in the flow of content, is usually presented outside the flow of content. In print, ways of presenting the note outside the flow of content include placing it at the bottom of the page, placing it in the margin, and placing in at the end of the chapter or other textual division. Not all of these readily translate to electronic media. Parenthetical inline references are, in my opinion, an example of notes with very mild separation from the flow of content: the note is left in place, but merely placed in parentheses.

With this semantic definition of a note, a note simply has content and a place in the text. The <ref></ref> tag, used well, as in today's featured article Caedmon, fills these semantic requirements nicely, as do the older templates {{inote}} and {{hnote}}, though all differ in the presentation they produce.

Some have complained that when notes are longer than a few words, their presence in the flow of text impedes editing. This will be a complaint with almost any semantic notational system, because a note has a place in the flow of content, so some sort of placeholder must be left to indicate its place. Most semantic markup systems, such as TeX and TEI, do leave notes inline. Yet if this complaint is to be addressed by changes in software, rather than ask for something specific to notes, I would ask for something more general, to cover the general problem of daunting, involved markup having to appear on a page and impede editing.

Ordinarily, templates would solve this problem. But templates are an unattractive solution here, because any given note will only appear once, and probably not appear on other pages, and creating a template for every lengthy note is tedious, and editing them is troublesome for the unitiated, since they aren't actually on the page. So the software feature I would ask for, is the ability to define a local template: a template defined on the same page as the article, and used only on that article page.

Now, since some appear to use the words 'citation' and 'reference' to apply to at least two different things, I will say that when I say 'reference,' I mean a (usually brief, usually abbreviated) snippet of bibliographic information, used to note that some part of the content refers to some outside source. Examples include Smith, p. 32; Macbeth II. ii.; and John 3:16. References are often notes, or parts of notes, so if notes are taken care of, so are references: the reference is simply the content of a note, or part of that content.

I'll call a 'citation' a full, structured, presentation of bibliographic information, with the purpose of allowing someone else to actually find the cited work. In my opinion, the various {{cite}} templates handle this nicely, and are structured enough to be readily converted to BibTeX or some other format, if someone desired to do so. Shimmin 14:32, 7 July 2006 (UTC)

Nicely stated. I totally agree with your point of view. I woudl add that a reference in your terminology is semantically more than just part of a note. It also provides a linkage of some sort to the cited source (to use your terms). So semantically, it is special content within the note. --Cplot 18:10, 7 July 2006 (UTC)
I'm trying to imagine how your "local template" would work. It seems like we're going to have to make some major changes to the MediaWiki software in order to address these syntax/semantics issues! In the meantime, I still think our priority should be to differentiate endnotes, references, citations, sources, parenthetical notes, cursor tooltips, and embedded citations! Shimmin, can you elaborate on "if notes are taken care of, so are references"? See also bugzilla:6271#c7. --J. J. 13:54, 10 July 2006 (UTC)
Shimmin, can you elaborate on "if notes are taken care of, so are references"? What I mean by this is that a reference, by which I mean a brief snippet of bibliographic information indicating that a particular bit of content is based on or refers to a particular source, is simply a common application of a note, by which I mean more generally content that, while having a place in the flow of content, is presented elsewhere, such as at the end or in the margin. The displaced content of a note can be one or more references, commentary on the text, or a mixture of the two. The recently featured article Caedmon includes many notes, most of which contain one or more references.
Cplot does correctly point out that a reference is somewhat special compared to other "note" content, because it may be desirable to link the reference to a full bibliographic citation elsewhere on the page. If the citation is given an id so that it may be targetted by a link, then this is as do-able as having the note include a wikilink to some other article, and not a significant complication. Again, see Caedmon for a well-executed example. Shimmin 00:49, 15 July 2006 (UTC)

Ref after punctuation and the no consensus trap

I had a good laugh at this edit summary: written by Slim. My "original research" was rather an "after having received another wiki scar" by those that disagree with the ref after punct. It's a bit unfair to reestablish this "no consensus" trap again. But anyway, guidelines seem not to have that much meaning on Wikipedia anyway ;). --Ligulem 23:07, 4 July 2006 (UTC)

Oh sorry, Ligulem, I didn't realize it was you who had added it, in despair perhaps. :-) All publishers put footnotes after punctuation to the best of my knowledge. I have never seen it done otherwise. Are people suggesting we should write this [1]? Or even this [2]!! The footnote is not part of the sentence. It is an extra sign that is offering a comment on the sentence. SlimVirgin (talk) 23:22, 4 July 2006 (UTC)
No need to convince me ;). I even wrote a piece of software that can convert articles to ref after punct. But when doing that on a series of articles I got biten by the no consensus thing ;). After that, I thought that it would be best to write down the state of affairs. And yes, there are people on this wiki that want to have it like this [3]. Just scroll up. --Ligulem 23:58, 4 July 2006 (UTC)
Your software is incredibly useful. I can't believe any editor would support writing this [4]! I think people have just misunderstood, or don't realize what publishers do. Anyone who doubts this should simply open any book that has footnotes in it. SlimVirgin (talk) 00:10, 5 July 2006 (UTC)

see above #Period/Full Stop and reference location and #Every sentence should have a reference?. --Philip Baird Shearer 07:32, 5 July 2006 (UTC)

Philip, can you name a single publisher who places footnotes before punctuation, or a style guide that recommends it? SlimVirgin (talk) 17:11, 5 July 2006 (UTC)
Amen, Slim. --J. J. 19:17, 5 July 2006 (UTC)
As a side note (possibly shooting myself in my foot): Paul Wicks wrote on my talk:
I'm another one that doesn't like it but will go along with it. In my area (neuropsychology) most journals have refs inside punctuation, with the exception of JNNP. This is somewhat infuriating when you have to move them all when resubmitting a paper there that's been rejected from elsewhere! Still, I shall endeavour to do this on future articles to maintain consistency.--PaulWicks 09:09, 4 June 2006 (UTC)
(archived thread, diff). --Ligulem 21:38, 5 July 2006 (UTC)

Is it possible that part of the argument is that people are talking about different things? In the styles that use parenthetical inline citations (MLA, APA, Harvard, &c.) the citation typically precedes the punctuation. In the styles that I am familiar with that use numerically-labeled foot- or endnotes (such as Chicago), the marker typically follows the punctuation. Shimmin 22:24, 5 July 2006 (UTC)

SV I am not the one putting a perscripton on to others to force them to do what I think is better. In the world of written published material it is unusual for different editors to jointly edit a paragraph when they may not agree with what should be in the paragraph. As such I think that before the period helps clarify the the reference is for that specific sentence only. But all this is discussed with examples higher up the page.

Usually I would suggest a complete deletion of such a paragraph in this guidline, if we can not agree on such an issue, but I think you point about "recommended by the Chicago Manual of Style" is useful information which should be kept here. Hence the reason for trying to construct a balanced paragrah. As can be seen from Ligulem survey there are a lot of pages which use before period notation and even if one assumes only 10% were intentional and that on average 10 of those pages were edited by the same editor, that is still a lot of editors who have done this intentionally.

Given time either editors will accept CMS recommendation is a vaild point and it will become the norm or they will not. But what I do not want are revert wars over this issue with this page being used as a club in such revert wars to say that this is the only way to do things because the guideline says so. But again I have expressed these views higher up the page in more detail and I do not think it constructive to broaden them in this section. What I would like to do is work on a compromise wording which we can all live with. BTW my broadband supplier went belly up this week so my replies to posts to this page in the immidiate future may intermittant .--Philip Baird Shearer 11:32, 6 July 2006 (UTC)

This statement from you sounds a bit like there was a revert war over this issue. Just for the records: there was none in wich I was involved and I can't imagine that there is anyone else who endevoured to undertake to move the punctuations around refs on a list of articles grater that 20. What I find bemusing is, that all featured articles do it like stated in this guideline here. Strange is, that Philip refuses to give a list or area of articles that should not be changed (e.g. along the lines "we do it on military articles like this, please leave it there"). And I can tell you that I changed a whole lot of articles where nobody cared at all where the punctuation is. And it was indeed very random where they were (even inside the very same article). And the claim that there a lot of editors who want it like Philip is simply wrong. It is in fact rather the other way round. This whole thing here is rather ridiculous. In fact Philip extended his refusal over entire wikipedia by asking me to stop changing articles to conform to what is the majority style. But if editors do it on all their featured articles by themselves, then it is ok. Very odd. But this seems to be the wiki-way (Maybe I should create a sockpuppet for each edit ;). At least please don't write it on this guildeline as if there was any consensus on this. Write how it is: more or less ridiculously random, with people disagreeing on the majority. That's why this is not an Encyclopedia. And it will probably never be. Or do you think the folks at Encyclopedia Britannica do it using one style on page X and the other way on page Y? They would laugh on us. And they probably do. Right they are. --Ligulem 12:13, 6 July 2006 (UTC)
Not to be overly pedantic, but merely because editors have done something intentionally doesn't mean it isn't completely wrong. Again, is there any style guide that recommends—or even allows—the numbers to precede closing punctuation? Kirill Lokshin 12:38, 6 July 2006 (UTC)
I agree that the ref should be put after punctuation. Until the question of how broad consensus is is cleared up, though, I'm not going to be changing anything. —Simetrical (talk  contribs) 05:31, 7 July 2006 (UTC)
I wonder whether people are confusing putting refs before punctuation and footnotes before it, as Shimmin suggested? Paul wrote above that neuropsychology journals put refs before punc, but surely they don't put footnotes before it. That is, you might write a Harvard ref before a period, as in: Wikipedia is a great website (SlimVirgin 2006). But you wouldn't place a footnote before the period, as in: "Wikipedia is a great website [5]. Footnotes always (including in neuropsychology journals, surely) go after punctuation. SlimVirgin (talk) 07:09, 7 July 2006 (UTC)
Mmm, there could be other reasons too. Does anyone have a really old (typewriter days) style guide? Where are non-superscript note numbers (e.g. Foo[1] versus Foo1) placed? Kirill Lokshin 12:24, 7 July 2006 (UTC)

Here is an example. A UK mobile phone company is offering a broadband connction. In their brochure all the references to footnotes come before the full stop. But on the internet page offering the same thing, they have stripped the stops for some reason so you will have to take my word for it . However on as secondary page they have forgotten to strip a couple of stops see after footnote 2 and 3 (NB there are 2 2s) . --Philip Baird Shearer 11:46, 18 July 2006 (UTC)

I think perhaps you're finding examples of people who've simply made a mistake. Can you produce a book published by a mainstream publisher that puts footnotes before punctuation? SlimVirgin (talk) 13:07, 18 July 2006 (UTC)

While I would generally put refs after punctuation, there are cases when it doesn't make sense (for instance when a reference is about two different things{REFONE} in the same phrase, which is inside parentheses{REFTWO}). I wouldn' write "parentheses){REFTWO}" in this case, as that would indicate that the reference is about the whole parentheses expression, whereas it's only meant to be a reference for the second part. Nightstallion (?) 11:57, 18 July 2006 (UTC)

I don't follow your examples, Nightstallion. SlimVirgin (talk) 13:07, 18 July 2006 (UTC)
I'll try again: If I've got "(A[ref1] and B[ref2])" it's clear that [ref1] refers to A and [ref2] refers to B. If we write "(A[ref1] and B)[ref2]", however, it would *strongly* suggest that [ref] refers to A and [ref2] refers to the whole expression in parentheses, i.e. "(A and B)". Do you get what I mean? Check the first paragraph of list of European Union member states by accession for an example (the parentheses expression after European Coal and Steel Community). Nightstallion (?) 09:23, 20 July 2006 (UTC)
I believe that footnotes go after commas, periods, exclamation points, question marks, colons, semicolons, and closing quotation marks, but before dashes, spaces, and closing parentheses. Other punctuation marks would probably have to be dealt with on a case-by-case basis. —Simetrical (talk  contribs) 01:12, 19 July 2006 (UTC)
I can agree with that. Nightstallion (?) 09:28, 20 July 2006 (UTC)

A style guide with references to footnotes before the stop CEDEFOD Manuscripts for publication in English(PDF) --Philip Baird Shearer 12:29, 18 July 2006 (UTC)

Here is an EU style guide (PDF see section 8). In this guide as in the last one they place footnotes in brackets but before the stop (1 ).

Those two links appear to be from the same people, and they do that because they're using parentheses for some reason, so what they're doing is basically putting a number in parentheses as if it were a Harvard reference, like this (SlimVirgin 2006). But they're doing it like this (1). It's correct to put Harvard refs inside punctuation.
Philip, can you please find one English-language book by one mainstream publisher that puts footnotes before punctuation; then we'll have something solid to go on. SlimVirgin (talk) 13:13, 18 July 2006 (UTC)

A recent edit by Dbiv has changed the guideline to suggest that footnotes before punctuation are preferred in British English. I'm wondering if that is actually the case: the Oxford Journal of Legal Studies, for example, states that the "footnote number follows any closing punctuation", as does the Cambridge Law Journal. Kirill Lokshin 23:27, 18 July 2006 (UTC)

I just reverted that. It was clearly made without any prior discussion and in contradiction with what we are actually finding. Circeus 01:31, 19 July 2006 (UTC)

The Disadvantages and future improvements section

Overall I think the project page is well written, concise and to the point. However the section "Disadvantages and future improvements" reads too much like a back-and-forth debate for the average reader. I suggest the salient points should be drawn out of that, summarized and perhaps reference made to other articles (i.e., preserving most of the links that are already there). Basically, trying to convey what readrs should get out of that discussion that elevantes it to the main page rather than here on the discussion page (where hopefully readers learn to check out for all their esoteric goodness). --Cplot 00:43, 7 July 2006 (UTC)

Citation of different locations/page numbers in a work

What is the best way to refer to different pages in a book? For example, should I say:

The flowers of the Gangliopensis are green, and attract bees.[6] In stark contrast, the Gangliofoosis has red flowers, and is pollenated by elephants.[7]

thereby making two endnotes for one source? Is there a better way? --Slashme 10:23, 10 July 2006 (UTC)

I think the way you've done it is fine. There have been several bug recommendations for this issue, but no solutions; see particularly Meta:Talk:Cite/Cite.php#Suggestion:_sub-reference_attribute_for_ref_tags. There really isn't any consensus on this issue, which is why I keep emphasizing policies to differentiate citations from references. See several of my July comments above for more details. --J. J. 14:18, 10 July 2006 (UTC)
I would make a separate "References" section full of fancy {{cite book}} tags and just put hand-written author-[title]-page citations in the footnotes themselves. (Some people don't seem to like the idea of doing any of this by hand, though, so YMMV.) Kirill Lokshin 15:03, 10 July 2006 (UTC)

A complicated page

I was wondering if anyone had advice on a ref system for Planetary habitability. When I started the ref's I used fn/fnb for explanatory footnotes and the mn/mnb for actual references. The latter is Wikipedia:Footnote4, which I've discovered is defunct and used on only a few articles. However, I further complicated it by separating my primary and secondary sources, which I think is useful on a long ref list for people looking to pick out good sources from generic ones; footnote4 allows me to do this as the numbers can be off sequence (ie., primary 1, 3, 6 followed by secondary 2, 4, 5). Is there anyway to keep the page ordered exactly as it is now, but with an accepted ref system? Marskell 14:20, 18 July 2006 (UTC)

What happened to the "Every sentence should have a reference?" discussion?

Philip Baird Shearer provided a link to #Every sentence should have a reference? above, but this section seems to have disappeared - I can't find it on this page or in the archives, am I missing something? Thanks, heqs 22:32, 24 July 2006 (UTC)

I just went to this page's history and clicked on Philip's July 5th entry. To answer your question, it's now in the archive. Centrix didn't create the archive link correctly. --J. J. 03:01, 26 July 2006 (UTC)
Cheers. heqs 09:43, 26 July 2006 (UTC)

Notes

Position of footnotes

Where does the footnote go if it applies to a huge section?

Ref system slowing down editorial work

Introductory section

Style recommendation

Standard reference name format

Thoughts from someone new to endnotes.

Quotation marks

Nightmare

Space after punctuation before reference mark

Distracting highlights

New references format

Cite templates

Notes

Why, god, why?

Help! Footnotes gone crazy!

Template FootnotesSmall

Footnotes missing

jump-back bug?

Two column forms

Is this a guideline?

Spacing of multiple references

"Notes" versus "References" section title

Guideline for formatting when there are general references?

Footnotes and References

Aesthetic Issues

ref tags and Cite.php

Why would anyone who goes looking for WP:FOOT ever expect to end up at WP:Footnotes?

Related Articles

Wikiwand AI