At the end of the semester, you will be expected to hand in a conference-style report, typed or printed from a computer file, on 8.5 by 11 inch paper (stapled in the upper left-hand corner, with your own title page [not the priner's cover page!]), describing the project you worked on this semester. (Please do not use folders or covers, unless your report is too thick to be stapled.) I strongly suggest that you learn to use Latex and ispell. The intended audience is the person who will be continuing your project next semester, so the report should be self-contained and detailed enough to tell that (possibly hypothetical) person exactly what has been done, why it was done, what problems were faced, how you solved them, what needs to be done next, and how to get started doing it. In the real world, you will be expected to write papers, either for presentation at conferences, publication in journals, or presentation to your boss or co-workers. No one reads computer programs except the programmer him- or herself, or someone else who has to modify the program. Users and other people want to read about the program, what it does, how it works, etc., and to see it in action. Consequently, the main product of your work is the paper, not the program or the demo! In the paper, you should say what you have done, and say (in English summary, not in programming detail) how you have done it. It should also include your annotated demo. You should read Goldfain, Albert (2003), "Computationally Defining 'harbinger' via Contextual Vocabulary Acquisition" [PDF], to see an example of a such a paper. Thus, each report must consist of the following components: * descriptive title (not: "CVA Project") * your name, the course number (CSE 727), & date completed (e.g., May 10, or whatever). * abstract of the project (a 1-paragraph summary) o consisting of brief, 1-or-2-sentence summaries of each of the following points (b-f, below) * This is the sort of information you might find yourself having to give, extemporaneously, in a job interview, in an informal discussion at a conference/convention, or even in a "real" job when your boss sees you in the hall or even in the mall :-) * This should be completely self-contained; i.e., it should be understandable by someone who is not familiar with our CVA project, as well as by someone who does not bother to read the rest of your paper! And your paper should not assume that the reader has read the abstract! o Do not assume that your hypothetical reader will have access to the abstract or, if they do have access, that they will read it. Consequently, your paper should include--and probably begin with-- any important information from the abstract. * description of the project (the body of the paper), including: # brief descriptions of the CVA project and SNePS # the role of your task in the overall project, e.g., which passage you're working on, what you're trying to do with it, etc. # what you have accomplished, including: 1. a report on any human protocols you ran 2. an annotated transcript of your demos including commented SNePS representations of the sentence and prior knowledge. o syntax and semantics of new SNePS case frames, o full explanation of any SNePS networks. # what the immediate next steps in your part of the project are * i.e., what you would have done had you had another week or so to work on it) # what longer-term future steps need to be taken * list of references (if appropriate) o Please be sure to cite only published materials (or unpublished papers from websites): Do not cite websites unless there is a very good reason to do so. If in doubt, ask me. 10. Please prepare all documents using a word processor (preferably LaTeX), and hand in hard copy to me on or before the due date announced in the syllabus. 11. For inclusion on the CVA website, I would also like online versions of: 1. your complete report, with all appendices (preferably in PDF format) 2. your demo file (plain ASCII text, not .doc) 3. a transcript of your demo (plain ASCII text, not .doc) * For further information on how to prepare your report, as well as pointers on grammar, etc., see my webpage "How to Write". * To see what some other reports look like, browse through the "Progress Reports" section of the CVA website.