Difference between revisions of "Resources"

From FachschaftSprachwissenschaft
Jump to: navigation, search
(Added too links to code)
(Web: Added some stuff about Academic Writing)
Line 41: Line 41:
 
[http://www.drni.de/niels/cl/hacks/tuebingerspruechle.sty Style file] by [[User:DrNI|Niels Ott]] for the official statement to be included (and signed) in every ''Schriftliche Hausarbeit'' or ''written summary''. Usage: <code>\SpruechleAufsagen{YourName}</code>. If you want another statement to be displayed, use <code>\renewcommand{\DasTuebingerSpruechle}{YourBlaBlaHere}</code>. (See also [http://www.drni.de/blog/archives/516-Erklaerung-zur-Hausarbeit-als-LaTeX-Paket.html this blog post].)
 
[http://www.drni.de/niels/cl/hacks/tuebingerspruechle.sty Style file] by [[User:DrNI|Niels Ott]] for the official statement to be included (and signed) in every ''Schriftliche Hausarbeit'' or ''written summary''. Usage: <code>\SpruechleAufsagen{YourName}</code>. If you want another statement to be displayed, use <code>\renewcommand{\DasTuebingerSpruechle}{YourBlaBlaHere}</code>. (See also [http://www.drni.de/blog/archives/516-Erklaerung-zur-Hausarbeit-als-LaTeX-Paket.html this blog post].)
  
== Web ==
+
== Web and Miscellaneous Resources ==
 
This is the section about resources you stumbled upon in the Web that might be of interest to your fellow students.
 
This is the section about resources you stumbled upon in the Web that might be of interest to your fellow students.
 
=== Linguistics ===
 
=== Linguistics ===
Line 49: Line 49:
 
==== LaTeX for Linguists ====
 
==== LaTeX for Linguists ====
 
[http://www.essex.ac.uk/linguistics/clmt/latex4ling/ This site] is just the single most helpful place in the Web if you are a linguist who wants to get his stuff done in the superior-to-all-other-type-setting-systems-typesetting-system LaTeX. It covers most everything ranging from Chomsky-style examples, over how to do trees, Discourse Representation Structures, all sorts of HPSG-esque matrices, to linguistic bibliographies and is surely worth a read.
 
[http://www.essex.ac.uk/linguistics/clmt/latex4ling/ This site] is just the single most helpful place in the Web if you are a linguist who wants to get his stuff done in the superior-to-all-other-type-setting-systems-typesetting-system LaTeX. It covers most everything ranging from Chomsky-style examples, over how to do trees, Discourse Representation Structures, all sorts of HPSG-esque matrices, to linguistic bibliographies and is surely worth a read.
 +
 +
=== Academic Writing ===
 +
 +
This section contains references to style guides in academic (English) writing. You may find this useful if you're currently taking classes in Academic Writing, writing your B.A., M.A. or even some other thesis or term paper. Some of the links are rather technical and deal with the intricacies of writing larger documents in LaTeX (you are not going to write your paper in anything else, are you now?), others refer to genera guidelines about style, content and language of such documents.
 +
 +
==== Thesis in LaTeX ====
 +
 +
* [http://theoval.sys.uea.ac.uk/~nlct/latex/thesis/ Using LaTeX to Write a PhD Thesis] seems to be a nice site explaining how to handle your papers (especially larger PhD-thesis-like papers) in LaTeX. Thanks to Katya for pointing us to the link.
 +
 +
==== Style Guidelines: Reports ====
 +
 +
Typically, an ISCL student has to write at least one report during the course of their studies: the internship report. Those links will hopefully help you to get on the right track.
 +
 +
* The [http://www.lc.unsw.edu.au/onlib/report.html Report Wrting FAQ] may help you with writing a typical internship report paper.
 +
 +
* Another "handbook" about writing [http://www.ecf.toronto.edu/~writing/handbook-lab.html lab reports] that may contain nice hints for internship reports.
 +
 +
* A handbook on writing [http://www.ecf.toronto.edu/~writing/handbook-shrtrept.html short reports].
 +
 +
* A handbook on writing [http://www.ecf.toronto.edu/~writing/handbook-progress.html progress reports].
 +
 +
===== Some Hints =====
 +
 +
Thanks to Janina Radó, who is currently (as of SS2008) teaching the Academic Writing course for those useful hints:
 +
 +
* The only parts with subjective information are the introduction and the conclusion.  The rest is purely factual.  That should also be reflected in the language -- avoid 1st person if possible, use neutral/ impersonal forms ("was necessary", "this was solved by developing ..." "this lead to an improvement...").  Don't overdo passive voice, though.  1st person is really only needed if you use it to distinguish things you did alone from those you did as part of a group -- and you can even get around that one.
 +
* The report proper is the task-results part.  That is already done, so it should be described using past tense.  In the rest of the paper you'll typically want to use present tense.
 +
* The report should not read like a diary.  There is no need to present the process you went through to arrive at the solution, unless it is important on its own.  That is, do not describe dead-ends in great detail simply to justify why you didn't get to complete the project.  Mention (or discuss, as appropriate) them only if they are the kind of example that others may want to learn from.  Also, the time you spent on a particular subpart does not need to be reflected in the length of the corresponding description.
 +
* There is no  need to talk about obvious "subtasks" such as reading up on the method you were going to use, unless it took up a huge amount of your internship.  The report is about how you used your skills and what new skills you learned, demonstrated though the actual thing you "created" -- it is taken for granted that you can read and learn things that way.
 +
* Although the presentation is a better place to mention this, you may still want to include a sentence or two in the conclusion about the general atmosphere at the company you were at, how much help you were given and how much you were allowed to try out your own ideas.  This is not a requirement and I'm not sure whether students ever look at previous reports before they select a place for their internships, but Dale may remember reading that this place was great (or a great horror) and advise students accordingly.

Revision as of 18:05, 29 June 2008

This page is for sharing literature and tools to help everybody in their studies. Examples include wordlists, books freely available on the Web, LaTeX style files, software you have written... go ahead!

If you make your own content available, please specify under what license or at least what conditions you would like to release it.

Papers online

This section is for papers that you can cite without woes: They have been published in an official journal and are available online in that same version. Please pay attention to that when adding to this section!

For electronic papers: Make sure you are at a university computer or connected to the university network via VPNC. This way, you can download many papers for free that otherwise require registration and payment.

Books

Books freely available on the Net. If you do not find what you're looking for, you might want to try WikiBooks

Linguistics

Literature about Phonology, Morphology, Syntax, Semantics, Pragmatics, Logic from a natural language perspective and all sorts of new research topics (DRT, OT, LFG, *TAG, Tree Languages...)

Computer Science

Books about programming languages, algorithms, theoretical computer science... Please do not confuse this section with the one about Computational Linguistics.

Blackburn, Bos and Striegnitz: Learn Prolog Now!

Free Online Book about the logic programming language.

Covington: Prolog Programming in Depth

Prolog Programming in Depth can serve you as a very nice reference to Prolog, as it is a searchable PDF and also very straight forward and systematically arranged. As an introduction to Prolog it is also more accessible than The Art of Prolog. You can download a draft of it here. (In case it becomes unavailable, you can ask me about providing you with the PDF)

J. Tang: Write Yourself a Scheme in 48 Hours

This may serve as a nice introduction to functional programming languages and/or parsing routines in Haskell. While Haskell is still not being widely used for NLP, that may very well change in the future, as it provides most of what NLP-interested people want: performance, ease of use, robustness, proximity (in syntax and semantics) to mathematical and logical paradigms, functional programming, type signatures, built-in lambda calculus... whatnot. During the course of this book you are also going to write a Scheme parser based on the Parsec library for Haskell. It is available from the author or as a WikiBook

Computational Linguistics

Books which neither fall into the domain of pure computer science, nor linguistics, but rather concern themselves with topics on both ends.

Code

Code you've written and like to share. Please do not forget to add a license for it.

  • BananaSplit: dictionary-based, simplistic compound splitter that works both as a library and as an application, written by Niels Ott.
  • ClusterLib: Java library for hierarchical bottom-up clustering by Ramon Ziai and Niels Ott.

LaTeX

Tübinger Sprüchle

Style file by Niels Ott for the official statement to be included (and signed) in every Schriftliche Hausarbeit or written summary. Usage: \SpruechleAufsagen{YourName}. If you want another statement to be displayed, use \renewcommand{\DasTuebingerSpruechle}{YourBlaBlaHere}. (See also this blog post.)

Web and Miscellaneous Resources

This is the section about resources you stumbled upon in the Web that might be of interest to your fellow students.

Linguistics

Online collections of papers? Tips for a linguist's survival in our world of studies? Here they go.

Semantics Archive

The Semantics Archive is an online collection of various papers concerning natural language semantics. An invaluable resource for anyone interested in the meaning of words, phrases and discourse.

LaTeX for Linguists

This site is just the single most helpful place in the Web if you are a linguist who wants to get his stuff done in the superior-to-all-other-type-setting-systems-typesetting-system LaTeX. It covers most everything ranging from Chomsky-style examples, over how to do trees, Discourse Representation Structures, all sorts of HPSG-esque matrices, to linguistic bibliographies and is surely worth a read.

Academic Writing

This section contains references to style guides in academic (English) writing. You may find this useful if you're currently taking classes in Academic Writing, writing your B.A., M.A. or even some other thesis or term paper. Some of the links are rather technical and deal with the intricacies of writing larger documents in LaTeX (you are not going to write your paper in anything else, are you now?), others refer to genera guidelines about style, content and language of such documents.

Thesis in LaTeX

  • Using LaTeX to Write a PhD Thesis seems to be a nice site explaining how to handle your papers (especially larger PhD-thesis-like papers) in LaTeX. Thanks to Katya for pointing us to the link.

Style Guidelines: Reports

Typically, an ISCL student has to write at least one report during the course of their studies: the internship report. Those links will hopefully help you to get on the right track.

  • Another "handbook" about writing lab reports that may contain nice hints for internship reports.
Some Hints

Thanks to Janina Radó, who is currently (as of SS2008) teaching the Academic Writing course for those useful hints:

  • The only parts with subjective information are the introduction and the conclusion. The rest is purely factual. That should also be reflected in the language -- avoid 1st person if possible, use neutral/ impersonal forms ("was necessary", "this was solved by developing ..." "this lead to an improvement..."). Don't overdo passive voice, though. 1st person is really only needed if you use it to distinguish things you did alone from those you did as part of a group -- and you can even get around that one.
  • The report proper is the task-results part. That is already done, so it should be described using past tense. In the rest of the paper you'll typically want to use present tense.
  • The report should not read like a diary. There is no need to present the process you went through to arrive at the solution, unless it is important on its own. That is, do not describe dead-ends in great detail simply to justify why you didn't get to complete the project. Mention (or discuss, as appropriate) them only if they are the kind of example that others may want to learn from. Also, the time you spent on a particular subpart does not need to be reflected in the length of the corresponding description.
  • There is no need to talk about obvious "subtasks" such as reading up on the method you were going to use, unless it took up a huge amount of your internship. The report is about how you used your skills and what new skills you learned, demonstrated though the actual thing you "created" -- it is taken for granted that you can read and learn things that way.
  • Although the presentation is a better place to mention this, you may still want to include a sentence or two in the conclusion about the general atmosphere at the company you were at, how much help you were given and how much you were allowed to try out your own ideas. This is not a requirement and I'm not sure whether students ever look at previous reports before they select a place for their internships, but Dale may remember reading that this place was great (or a great horror) and advise students accordingly.