370 likes | 418 Views
Explore the intricate structure of Bantu verb phrases, diving deep into morphology and variables to grasp the complex linguistic patterns. Discover essential elements and their significance in sentence construction.
E N D
The Bantu Verb Phrase morphology (variables) rampant
4. s/he did not cook for her/him (yesterday) hasiyamudekhere
‘s/he did not cook for her/him (yesterday)’ Hasiyamudekhere [xasíjam↓údeex↓éére]
Joe arisire ngombe ama-dimwa Joe fed 9cattle 6-corn ‘Joe fed the cattle corn’ [a - Ø - r - íís - ir - ↓é] SP - TA - ROOT – DSUF - ASP - MODE 1 - HP - eat - CAUS - HP – (HP)
Hasiyamudekhere ‘s/he did not cook for her/him (yesterday)’ [xasí - j - a - m↓ú - deex - ↓éér - e] NEG - SP - TA - OP - Root - DSuf/ASP? - MODE NEG -1(9)- PHP - 3ps - cook – APP/PHP? - PHP
The Slots (NEG) + SP + T/A + (OP) + Root + (DS + (DS2 + (DS3))) + (ASP) + Mode 1 2 3 4 5 <- - - - - 6 - - - - - - > 7 8 semantically obligatory optional
Bantu Noun Classes Bantu Noun Classes (singular/plural) 1/2 Primarily human 3/4 Non-human animates; body parts; plants 5/6 Mass nouns; 0-singular nouns: some animals, plants and body parts 7/8 The "thing" class: utensils, instruments: some body parts 9/10 The "N-class": mostly loanwords and names of animals 11/10 Things having length; some body parts 12/13 Diminutive or derogatory 14/6 Ideas; abstract nouns 15/6 Gerundial / infinitival verb forms: 16 Locative (roughly ‘at’) 17 Locative (roughly ‘on’) 18 Locative (roughly ‘in, into’) 24 Locative (roughly ‘at, to’) 20/4 Augmentative; sometimes derogatory
The Slots (NEG) + SP + T/A + (OP) + Root + (DS + (DS2 + (DS3))) + (ASP) + Mode 1 2 3 4 5 <- - - - - 6 - - - - - - > 7 8 semantically obligatory optional
(NEG) + SP + T/A + (OP) +ROOT + (DS + (DS + (DS))) + (Aspect) + Mood 1ps 1ps 1pp 1pp 2ps 2ps 2pp RP 2pp 1 PHP 1 REVERS REVERS REVERS 2 HP 2 STAT STAT STAT 3 JN 3 CAUS CAUS CAUS PERF NEG + 4 + Pres + 4 + ROOT + APP + APP + APP + HAB + MOOD(fv) 5 still 5 RECIP RECIP RECIP 6 just 6 PASS PASS PASS 7 HF 7 INTENS INTENS INTENS 8 PHF 8 ... ... ... 9 RF 9 10 10 11 11 12 12 13 13 14 14 15 15 16 16 ... REFLEXIVE ...
Why Everything is Important The top VP means ‘she cooked for him’; the bottom means ‘she cooked him’.
Initial Attempt – full view One slant: a data structure is ultimately a metaphor for a real-world domain.
Initial Attempt – full view One slant: a data structure is ultimately a metaphor for a real-world domain. Admitted: all metaphors ultimately breakdown
Initial Attempt – full view One slant: a data structure is ultimately a metaphor for a real-world domain. Admitted: all metaphors ultimately breakdown The issue then becomes: which metaphor gets the most miles?
So Far How to account for the following properties of the slots: • some are obligatory, some are optional. • with the exception of the Verb Root, the potential for each slot is one from a small and fixed set. • each non-root morpheme will have a fixed phonological form determined by its semantic definition and its slot. (NEG) + SP + T/A + (OP) + Root + (DS + (DS2 + (DS3))) + (ASP) + Mode
morphology (NEG) + SP + T/A+(OP) + Root + (DS + (DS2 + (DS3))) + (ASP) + Mode <xs:complexType name=”Morphology”> <xs:mixedType> <xs:sequence> <xs:element name=”NEG” type=”xs:string” fixed=”xasí” minOccurs=”0”/> <xs:complexType name=”SubjectPronoun”/> <xs:complexType name=”TenseAspect”/> <xs:complexType name=”ObjectPronoun” minOccurs=”0” maxOccurs=”2”/> <xs:element name=”VerbRoot” type=”xs:string”/> <xs: complexType name=”DerivSuff” minOccurs=”0” maxOccurs=”3”/> <xs:complexType name=” TenseAspect2”/> <xs:complexType name=”Mode” type=”xs:string” default=”a”/> /xs:sequence> </xs:mixedType> </xs:complexType>
morphology <xs:complexType=”Morphology”> <xs:mixedType> <xs:sequence> <xs:element name=”NEG” type=”xs:string” fixed=”xasí” minOccurs=”0”/> <xs:complexType name=”SubjectPronoun”/> <xs:complexType name=”TenseAspect”/> <xs:complexType name=”ObjectPronoun” minOccurs=”0” maxOccurs=”2”/> <xs:element name=”VerbRoot” type=”xs:string”/> <xs: complexType name=”DerivSuff” minOccurs=”0” maxOccurs=”3”/> <xs:complexType name=” TenseAspect2”/> <xs:complexType name=”FinalVowel” type=”xs:string” default=”a”/> /xs:sequence> </xs:mixedType> </xs:complexType>
One more wrinkle SP + Tense SP + Tense 1 + PHP 1 + RP a + a a + á
One more wrinkle THE SOLUTION SP + Tense SP + Tense 9 + PHP 9 + RP y + a y + á
Pronouns so far: • subject slot obligatory, object slot optional • morphological categories the same for both w/ addition of REFLEXIVE for object slot. • phonological forms of some same for both slots, others differ depending on slot.
Summary The following devices in Schema capture the patterns in the pronoun system of a natural language: • group (ref) • sequence • choice • MinOccurs / MaxOccurs
Benefits Hoped for: • migratable, extensible, best practice • data structure includes all details • entry contains no non-present information Unanticipated: • constraints on model reflect constraints on domain • could easily be configured to generate UR
TO DO (LEARN) • convert Schema to XSLT. • learn programming to have TENSE specification access SP, if Class 1, then Class 9, and also to automatically insert Aspect specification when applicable.
TO BE DONE: Bantu terminology DS: derivational suffix, radical extension, thematic extension, extension, thematic... APP: applied, applicative, directional, prepositional...
From other fields: KEVIN: Computers and Writing, an annual conference in our field. Two of the keynotes, Nancy Kaplan and Stuart Moulthrop, both hit on this point, although not XML specifically. They used "code" as a trope for "know how to do everything yourself," which includes the literal code. Sort of a Zen and Motorcycle Maintenance kind of argument, but also an argument that, as people who teach "writing," we should quit arguing that the "writing" is separate from the code. If we want to control all aspects of "writing," that is going to include the code.