Week 1, (Course Project Proposal and Report Notes), Week 2, Week 3, (end of diary)
Once a course project is approved, you must write and submit a printout of your project proposal to the course instructor by 9am on Tuesday, November 4. This proposal is worth 5 course marks. It should be about a page long and consist of a 3-paragraph proposal text (3.5 marks total) (with the first paragraph motivating why your topic is of interest (1 mark), the second summarizing previous work on this topic (1.5 marks), and the third summarizing the focus of your survey or the approach you will use in constructing your software system (1 mark)) followed by at least five full-information literature references particular to the topic of your project which must each be cited at least once in your proposal text (1.5 marks total) (0.3 marks per reference up to 5 references).
Once the project proposal is submitted, you have until noon on Friday, December 5, to do your project and submit a printout of your project report. In general, In general, this project will entail (as a minimum) a 15-20 page report (double-spaced) with 10-30 literature references (for a literature-survey project) or a 5-8 page report (double-spaced) with 5-15 references in addition to the software (for a software project). All included references MUST be cited in the body of the report. Though purely Web-based references (e.g., blogs, reference manuals) are acceptable, please try where at all possible to obtain literature-based references, e.g., books, book chapters, journal papers, conference papers; in those cases, You MUST give full references listing all reference information appropriate to the type of reference, author names, publication year, full paper title, book title with editors, journal name, journal volume and number, publisher, page numbers.
The length and reference-number requirements above may vary depending on the nature of the chosen project and whether or not this project is being done by one or more people; this should be settled with the course instructor. Ideally, the submitted project should be on the same topic as that described in your project proposal. However, it being an imperfect world, if any difficulties do arise, chat with your course instructor as soon as possible so appropriate action, e.g., revision of stated goals and/or scope of project, can be taken.
If course enrollment is low enough (see the course outline), each project will also have an associated short in-class presentation scheduled in the last two weeks of course lectures. Details of talk format and scheduling will be posted in early November after project proposals are submitted and marked.
Here's to each of you choosing and carrying out a fun course project!
mop | mops | [s] |
pot | pots | [s] |
pick | picks | [s] |
kiss | kisses | [(e)s] |
mob | mobs | [z] |
pod | pods | [z] |
pig | pigs | [z] |
pita | pitas | [z] |
razz | razzes | [(e)z] |
Note that the phonetic form of the plural-morpheme /s/ is a function of the last sound (and in particular, the voicing of the last sound) in the word being pluralized. A similar voicing of /s/ often (but not always) occurs between vowels, e.g., "Stasi" vs. "Streisand".
dal | dallar | ``branch'' |
kol | kollar | ``arm'' |
kul | kullar | ``slave'' |
yel | yeller | ``wind'' |
dis | disler | ``tooth'' |
g"ul | g"uller | ``race'' |
The form of the vowel in the plural-morpheme /lar/ is a function of the vowel in the word being pluralized.
In Turkish, complete utterances can consist of a single word in which the subject of the utterance is a root-morpheme (in this case, [c"op], "garbage") and all other (usually syntactic, in languages like English) relations are indicated by suffix-morphemes. As noted above, the vowels in the suffix morphemes are all subject to vowel harmony. Given the in principle unbounded number of possible word-utterance in Turkish, it is impossible to store them (let alone their versions as modified by vowel harmony) in a lexicon.
These rules can also hold when a Cantonese speaker writes English text, e.g., "Phone Let Kloss."
dosutoru | ``duster'' |
sutoroberri` | `strawberry'' |
kurippaa` | `clippers'' |
sutoraiki | ``strike'' |
katsuretsu | ``cutlet'' |
parusu | ``pulse'' |
gurafu | ``graph'' |
Japanese has a single phoneme /r/ for the liquid-phones [l] and [r]; moreover, it also allows only very restricted types of multi-consonant clusters. Hence, when words that violate these constraints are borrowed from another language, those words are changed by the modification to [r] or deletion of [l] and the insertion of vowels to break up invalid multi-consonant clusters.
/fikas/ | "strong" | /fumikas/ | "to be strong" |
/kilad/ | "red" | /kumilad/ | "to be red" |
/fusl/ | "enemy" | /fumusl/ | "to be an enemy" |
katab | kutib | "to write" |
kattab | kuttib | "cause to write" |
ka:tab | ku:tib | "correspond" |
taka:tab | tuku:tib | "write each other" |
/adus/ | "take a bath" | /odasadus/ |
/bali/ | "return" | /bolabali/ |
/bozen/ | "tired of" | /bozanbozen/ |
/dolan/ | "recreate" | /dolandolen/ |
(MEANINGFUL WHISPER: Do you see anything that makes reduplication qualitatively different from all other phonological and morphological processes that we have considered here? (Hint: a^n b^n => ww))
"[[the [quick [brown [fox]]]] [jumped over [the [lazy [dog]]]]]".
SOV | "She him loves." | 45% | Pashto, Latin, Japanese, Afrikaans |
SVO | "She loves him." | 42% | English, Hausa, Mandarin, Russian |
VSO | "Loves she him." | 9% | Hebrew, Irish, Zapotec, Tuareg |
VOS | "Loves him she." | 3% | Malagasy, Baure |
OVS | "Him loves she." | 1% | Apalai, Hixkaryana |
OSV | "Him she loves." | < 1% | Warao |
(MEANINGFUL WHISPER: Is such embedding of constituents qualitatively different from other syntactic patterns considered above? (Hint: a^n b^n))
Hence, ambiguity inherent in grammars and lexicons adds yet another type of ambiguity into natural language processing (BKL, pp. 317-318).
S -> aA A -> bS A -> b
S -> aC C -> aC C -> bC C -> b
S -> aC C -> aC C -> bC C -> E E -> b
S -> aA A -> aA A -> bB A -> b B -> aA B -> bB B -> b
S -> {*vcd}V S -> {*unvcd}U V -> {*vcd}V V -> {*unvcd}U V -> {P}z U -> {*vcd}V U -> {*unvcd}U U -> {P}s
Created: July 11, 2025
Last Modified: September 17, 2025