{"id":329,"date":"2014-02-25T22:51:03","date_gmt":"2014-02-25T22:51:03","guid":{"rendered":"http:\/\/www.americanlinguistics.org\/?page_id=329"},"modified":"2023-11-08T15:51:39","modified_gmt":"2023-11-08T15:51:39","slug":"presenting-data","status":"publish","type":"page","link":"https:\/\/www.americanlinguistics.org\/?page_id=329","title":{"rendered":"Presenting data"},"content":{"rendered":"

When presenting data in blocks or datasets in a linguistics paper (or, for that matter, presenting definitions or lists in inset blocks), it is important to keep in mind two basic principles:<\/p>\n

    \n
  1. the data must be presented first, as soon as possible after first mention, before being discussed in detail;<\/li>\n
  2. the data must be introduced in a general way alerting the reader as to why they are there, what they are intended to illustrate, and what the reader should look for in the dataset, and they should be immediately explicated afterwards, highlighting the specific details in the dataset that are of interest, and how these contribute to the paper.<\/li>\n<\/ol>\n

    The first principle ensures that readers do not have to flip back and forth between the data and the text, and that they do not have to follow a discussion of something hitherto unseen. The second principle prepares the reader ahead of time for what is coming and makes it easy to find the salient features of a dataset, and afterwards ensures that readers understand the examples and how you are interpreting them for the purposes of your writing.<\/p>\n

    An example for this type of writing might be drawn from a discussion of causative constructions, where the aim is to illustrate the morphological causative and introduce to the reader to the idea that there are some typological problems with the traditional distinction drawn between the semantic roles of Agent and Causer. We would want to begin this discussion by giving an example of a simple verb from Upper Necaxa Totonac, followed by a sentence containing its causative derivative, as in (1):<\/p>\n\n\n\n\n\n\n
    (1)<\/td>\na.<\/td>\nkit na\u1e2dksk\u00faxa \u010du\u02d0w\u00e1 wa\u02d0ts\u00e1<\/td>\n<\/tr>\n
    <\/td>\n<\/td>\nkit<\/td>\nna\u2013\u1e2dk\u2013sk\u00fax\u2013a<\/td>\n\u010du\u02d0w\u00e1<\/td>\nwa\u02d0ts\u00e1<\/td>\n<\/tr>\n
    <\/td>\n<\/td>\nI<\/td>\nFUT<\/span>\u20131SG.SUB<\/span>\u2013work\u2013IMPF<\/span><\/td>\nnow<\/td>\nhere<\/td>\n<\/tr>\n
    <\/td>\n<\/td>\n\u2018I\u2019ll work here now.\u2019<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n\n\n\n\n\n
    <\/td>\nb.<\/td>\nli\u02d0la\u0330\u0294apu\u02d0c\u00ed\u02d0 ak\u0161n\u00ed \u1e2d\u0161kintama\u02d0skux\u00fa\u02d0 a\u0330\u02d0xcanan\u00fa<\/td>\n<\/tr>\n
    <\/td>\n<\/td>\nli\u02d0\u2013la\u0330\u0294apu\u02d0c\u00ed\u02d0<\/td>\nak\u0161n\u00ed<\/td>\n\u1e2d\u0161\u2013kin\u2013ta\u2013ma\u02d0\u2013skux\u2013\u00fa\u02d0<\/td>\na\u0330\u02d0xcanan\u00fa<\/td>\n<\/tr>\n
    <\/td>\n<\/td>\nINST<\/span>\u2013be.sad<\/td>\nwhen<\/td>\nPAST<\/span>\u20131OBJ<\/span>\u20133PL.SUB<\/span>\u2013CS<\/span>\u2013work\u2013CS<\/span><\/td>\nback.then<\/td>\n<\/tr>\n
    <\/td>\n<\/td>\n\u2018It was sad when they made me work back then.\u2019<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    (1) contrasts the monovalent verb skux-<\/em><\/span> \u2018work\u2019 with its causative derivative, ma\u02d0skux\u00fa\u02d0<\/em><\/span> \u2018make sby work\u2019, which is bivalent. The new semantic actant in (1b) becomes the subject, and the original subject of the base \u2014 generally referred to as the “Causee” \u2014 is realized as a direct object. The new semantic actant has the role of Causer, which differs from Agent by virtue of being the initiator of an unspecified event that in turn triggers the event expressed by the verbal base (Langacker 1987). In languages with morphological causatives, verbs whose subjects express prototypical Agents tend to be underived stems whereas those whose subjects are clearly Causers tend to be derived. However, both within and across languages there is a certain fuzziness as to where the line between the two roles is drawn, and which predicates are derived or underived.<\/p>\n

    How not to present data in a paper<\/h4>\n

    Do not discuss data that you haven\u2019t presented yet<\/p>\n

    WRONG<\/h6>\n

    Upper Necaxa Totonac displays some apparent irregularities in the expression of subject and object agreement in cases where the subject is first- or second-person and the object is second- or first-person, and one or both is plural, as seen in (2). These forms are three-way ambiguous; the 1 > 2 form in (2a), for instance, which consists of the first-person subject prefix \u1e2dk-<\/em><\/span>, the plural object marker ka\u02d0-<\/em><\/span>, and the second-person object suffix -n<\/em><\/span>, has not only the expected 1sg > 2pl reading, it is also used in situations where 1pl > 2pl and 1pl > 2sg. Likewise, the form in (2b) has three readings, 2sg > 1pl, 2pl > 1pl, 2pl > 1sg, although in this case it consists of a non-compositional configuration of affixes, the first-person object prefix kin-<\/em><\/span>, the first-person plural subject suffix -w<\/em><\/span>, and the reciprocal prefix la\u02d0-<\/em><\/span>.<\/p>\n\n\n\n\n\n\n
    (2)<\/td>\na.<\/td>\n\u1e2dka\u02d0t\u1e75\u0301ksn\u1e2d<\/td>\n<\/tr>\n
    <\/td>\n<\/td>\n\u1e2dk\u2013ka\u02d0\u2013t\u1e75ks\u2013n\u1e2d<\/td>\n<\/tr>\n
    <\/td>\n<\/td>\n1SG.SUB<\/span>\u2013PL.OBJ<\/span>\u2013hit\u20132OBJ:PFV<\/span><\/td>\n<\/tr>\n
    <\/td>\n<\/td>\n\u2018I hit you guys\u2019 or \u2018we hit you guys\u2019 or \u2018we hit you\u2019<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n\n\n\n\n\n
    <\/td>\nb.<\/td>\nkila\u02d0t\u1e75\u0301ksw\u1e2d<\/td>\n<\/tr>\n
    <\/td>\n<\/td>\nkin\u2013la\u02d0\u2013t\u1e75ks\u2013w\u1e2d<\/td>\n<\/tr>\n
    <\/td>\n<\/td>\nINST<\/span>\u2013RCP<\/span>\u2013hit\u20131PL.SUB:PFV<\/span><\/td>\n<\/tr>\n
    <\/td>\n<\/td>\n\u2018you hit us\u2019 or \u2018you guys hit us\u2019 or \u2018you guys hit me\u2019<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
    RIGHT<\/h6>\n

    Upper Necaxa Totonac displays some apparent irregularities in the expression of subject and object agreement in cases where the subject is first- or second-person and the object is second- or first-person, and one or both is plural. These forms are three-way ambiguous, as seen in (3), which shows a verb expressing action of the first-person on the second (1 > 2):<\/p>\n\n\n\n\n\n\n
    (3)<\/td>\n\u1e2dka\u02d0t\u1e75\u0301ksn\u1e2d<\/td>\n<\/tr>\n
    <\/td>\n\u1e2dk\u2013ka\u02d0\u2013t\u1e75ks\u2013n\u1e2d<\/td>\n<\/tr>\n
    <\/td>\n1SG.SUB<\/span>\u2013PL.OBJ<\/span>\u2013hit\u20132OBJ:PFV<\/span><\/td>\n<\/tr>\n
    <\/td>\n\u2018I hit you guys\u2019 or \u2018we hit you guys\u2019 or \u2018we hit you\u2019<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    The form in (3) consists of the first-person subject prefix \u1e2dk-<\/em><\/span>, the plural object marker ka\u02d0-<\/em><\/span>, and the second-person object suffix -n<\/em><\/span>. This is the form expected for the 1sg > 2pl reading, but it is also used in situations where 1pl > 2pl and 1pl > 2sg.<\/p>\n

    In a similar vein, the form in (4) expresses action of 2 on 1 and has three readings, 2sg > 1pl, 2pl > 1pl, 2pl > 1sg:<\/p>\n\n\n\n\n\n\n
    (4)<\/td>\nkila\u02d0t\u1e75\u0301ksw\u1e2d<\/td>\n<\/tr>\n
    <\/td>\nkin\u2013la\u02d0\u2013t\u1e75ks\u2013w\u1e2d<\/td>\n<\/tr>\n
    <\/td>\nINST<\/span>\u2013RCP<\/span>\u2013hit\u20131PL.SUB:PFV<\/span><\/td>\n<\/tr>\n
    <\/td>\n\u2018you hit us\u2019 or \u2018you guys hit us\u2019 or \u2018you guys hit me\u2019<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    Unlike (3), however, this form consists of a non-compositional configuration of affixes\u2014the first-person object prefix kin-<\/em><\/span>, the first-person plural subject suffix -w<\/em><\/span>, and the reciprocal prefix la\u02d0-<\/em><\/span>.<\/p>\n

    Do not concentrate all your data into a single long set then discuss it<\/p>\n

    WRONG<\/h6>\n

    Upper Necaxa Totonac has a total of six valency-increasing morphemes, two causatives and three applicatives:<\/p>\n\n\n\n\n\n\n
    (5)<\/td>\na.<\/td>\nkima\u02d0\u026cka\u02d0kn\u00ed\u02d0ya\u0330<\/td>\n<\/tr>\n
    <\/td>\n<\/td>\nkin\u2013ma\u02d0\u2013\u026cka\u02d0k\u2013ni\u02d0\u2013ya\u0330<\/td>\n<\/tr>\n
    <\/td>\n<\/td>\n1OBJ<\/span>\u2013CS<\/span>\u2013hot\u2013CS<\/span>\u2013IMPF:2SG.SUB<\/span><\/td>\n<\/tr>\n
    <\/td>\n<\/td>\n\u2018you are making me hot\u2019<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n\n\n\n\n\n
    <\/td>\nb.<\/td>\nma\u0330\u0294ajikw\u00e1nl\u1e2d tsa\u0330m\u00e1 \u0294aw\u00e1\u0330\u010da\u0330<\/td>\n<\/tr>\n
    <\/td>\n<\/td>\nma\u0330\u0294a\u2013jikw\u00e1n\u2013l\u1e2d<\/td>\ntsa\u0330m\u00e1<\/td>\n\u0294aw\u00e1\u0330\u010da\u0330<\/td>\n<\/tr>\n
    <\/td>\n<\/td>\nSTM<\/span>\u2013afraid\u2013PFV<\/span><\/td>\nthat<\/td>\nboy<\/td>\n<\/tr>\n
    <\/td>\n<\/td>\n\u2018he frightened the boy\u2019<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n\n\n\n\n\n
    <\/td>\nc.<\/td>\nna\u0330k\u0161o\u0330\u0294on\u1e2dy\u00e1\u02d0n \u1e2d\u0161tap\u00e1\u026c<\/td>\n<\/tr>\n
    <\/td>\n<\/td>\nna\u2013\u1e2dk\u2013\u0161o\u0330\u0294\u00f3\u2013n\u1e2d\u2013ya\u02d0\u2013n<\/td>\n\u1e2d\u0161\u2013tap\u00e1\u026c<\/td>\n<\/tr>\n
    <\/td>\n<\/td>\nFUT<\/span>\u20131SG.SUB<\/span>\u2013pay\u2013BEN<\/span>\u2013IMPF<\/span>\u20132OBJ<\/span><\/td>\n3PO<\/span>\u2013price<\/td>\n<\/tr>\n
    <\/td>\n<\/td>\n\u2018I\u2019ll pay you its price\u2019<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n\n\n\n\n\n
    <\/td>\nd.<\/td>\n\u0161u\u02d0n\u00fa\u02d0k nali\u02d0\u0294e\u02d0chi\u02d0k\u00e1n \u0161a\u0330\u02d0<\/td>\n<\/tr>\n
    <\/td>\n<\/td>\n\u0161u\u02d0n\u00fa\u02d0k<\/td>\nna\u2013li\u02d0\u2013\u0294e\u02d0\u2013chi\u02d0\u2013kan<\/td>\n\u0161a\u0330\u02d0<\/td>\n<\/tr>\n
    <\/td>\n<\/td>\nbark<\/td>\nFUT<\/span>\u2013INST<\/span>\u2013back\u2013tie\u2013IDF<\/span><\/td>\nsweatlodge<\/td>\n<\/tr>\n
    <\/td>\n<\/td>\n\u2018they will tie it onto the sweatlodge with bark\u2019<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n\n\n\n\n\n
    <\/td>\ne.<\/td>\nnakinta\u0330\u02d0p\u00edna\u0330<\/td>\n<\/tr>\n
    <\/td>\n<\/td>\nna\u2013kin\u2013ta\u0330\u02d0\u2013pin\u2013a\u0330<\/td>\n<\/tr>\n
    <\/td>\n<\/td>\nFUT<\/span>\u20131OBJ<\/span>\u2013CMT<\/span>\u2013go:2SUB<\/span>\u2013IMPF:2SG.SUB<\/span><\/td>\n<\/tr>\n
    <\/td>\n<\/td>\n\u2018you will go with me\u2019<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n\n\n\n\n\n
    <\/td>\nf.<\/td>\ntala\u0330\u0294\u00e1\u0330\u026c ja\u0330\u02d0 \u1e2d\u0161tama\u02d0ki\u02d0n\u1e2d\u0301\u02d0 \u1e2d\u0161lu\u02d0wa\u0330k\u00e1\u0330n<\/td>\n<\/tr>\n
    <\/td>\n<\/td>\nta\u2013la\u0330\u0294\u2013a\u0330n\u2013\u026c<\/td>\nja\u0330\u02d0<\/td>\n\u1e2d\u0161\u2013ta\u2013ma\u02d0k\u00ed\u02d0\u2013n\u1e2d\u02d0<\/td>\n\u1e2d\u0161\u2013l\u00fa\u02d0wa\u0330\u2013ka\u0330n<\/td>\n<\/tr>\n
    <\/td>\n<\/td>\n3PL.SUB<\/span>\u2013ALTV<\/span>\u2013go\u2013PFV<\/span><\/td>\nwhere<\/td>\nPAST<\/span>\u20133PL.SUB<\/span>\u2013keep\u2013PF<\/span><\/td>\n3PO<\/span>\u2013snake\u2013PL.PO<\/span><\/td>\n<\/tr>\n
    <\/td>\n<\/td>\n\u2018they went to where they kept their snake\u2019<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    The first two valency-increasers are causatives. (5a) shows the cross-linguistically typical causative that adds a volitional agent to the event expressed by the verb; (5b) shows the stimulus morpheme ma\u0330\u0294a-<\/em><\/span>, which typically adds a non-human or inanimate causer, or is used to form verbs expressing caused internal or psychological states. (5c) illustrates the benefactive suffix,
    \n-n\u1e2d<\/em><\/span>,\u00a0which adds a beneficiary, maleficiary, recipient, or experiencer to an event. The instrumental applicative, li\u02d0-<\/em><\/span>, shown in (5d), typically adds an instrument, but can also add motives. The comitative ta\u0330\u02d0-<\/em><\/span> seen in (5e) adds a co-actor that performs the action described by the verb along with the subject. The final applicative, the allative la\u0330\u0294-<\/em><\/span>, adds a goal to a limited set of motion verbs, mostly those based on the verbs a\u0330n<\/em><\/span> \u2018go\u2019 and min<\/em><\/span> \u2018come\u2019.<\/p>\n

    RIGHT<\/h6>\n

    Upper Necaxa Totonac has a total of six valency-increasing morphemes, two causatives and three applicatives. The causatives are ma\u02d0- -ni\u02d0<\/em><\/span> \u2018causative\u2019 (6a) and ma\u0330\u0294a-<\/em><\/span> \u2018stimulus\u2019 (6b):<\/p>\n\n\n\n\n\n\n
    (6)<\/td>\na.<\/td>\nkima\u02d0\u026cka\u02d0kn\u00ed\u02d0ya\u0330<\/td>\n<\/tr>\n
    <\/td>\n<\/td>\nkin\u2013ma\u02d0\u2013\u026cka\u02d0k\u2013ni\u02d0\u2013ya\u0330<\/td>\n<\/tr>\n
    <\/td>\n<\/td>\n1OBJ<\/span>\u2013CS<\/span>\u2013hot\u2013CS<\/span>\u2013IMPF:2SG.SUB<\/span><\/td>\n<\/tr>\n
    <\/td>\n<\/td>\n\u2018you are making me hot\u2019<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n\n\n\n\n\n
    <\/td>\nb.<\/td>\nma\u0330\u0294ajikw\u00e1nl\u1e2d tsa\u0330m\u00e1 \u0294aw\u00e1\u0330\u010da\u0330<\/td>\n<\/tr>\n
    <\/td>\n<\/td>\nma\u0330\u0294a\u2013jikw\u00e1n\u2013l\u1e2d<\/td>\ntsa\u0330m\u00e1<\/td>\n\u0294aw\u00e1\u0330\u010da\u0330<\/td>\n<\/tr>\n
    <\/td>\n<\/td>\nSTM<\/span>\u2013afraid\u2013PFV<\/span><\/td>\nthat<\/td>\nboy<\/td>\n<\/tr>\n
    <\/td>\n<\/td>\n\u2018he frightened the boy\u2019<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    Of the two, ma\u02d0- -ni\u02d0<\/em><\/span> is the cross-linguistically typical causative that adds a volitional agent to the event expressed by the verb; the stimulus morpheme ma\u0330\u0294a-<\/em><\/span>, on the other hand, typically adds a non-human or inanimate causer, or is used to form verbs expressing caused internal or psychological states.<\/p>\n

    The first of the four applicatives is the benefactive suffix, -n\u1e2d<\/em><\/span> shown in (7):<\/p>\n\n\n\n\n\n\n
    (7)<\/td>\nna\u0330k\u0161o\u0330\u0294on\u1e2dy\u00e1\u02d0n \u1e2d\u0161tap\u00e1\u026c<\/td>\n<\/tr>\n
    <\/td>\nna\u2013\u1e2dk\u2013\u0161o\u0330\u0294\u00f3\u2013n\u1e2d\u2013ya\u02d0\u2013n<\/td>\n\u1e2d\u0161\u2013tap\u00e1\u026c<\/td>\n<\/tr>\n
    <\/td>\nFUT<\/span>\u20131SG.SUB<\/span>\u2013pay\u2013BEN<\/span>\u2013IMPF<\/span>\u20132OBJ<\/span><\/td>\n3PO<\/span>\u2013price<\/td>\n<\/tr>\n
    <\/td>\n\u2018I\u2019ll pay you its price\u2019<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    This suffix adds a beneficiary, maleficiary, recipient, or experiencer to an event.<\/p>\n

    The example in (8) illustrates the instrumental applicative, li\u02d0-<\/em><\/span>:<\/p>\n\n\n\n\n\n\n
    (8)<\/td>\n\u0161u\u02d0n\u00fa\u02d0k nali\u02d0\u0294e\u02d0chi\u02d0k\u00e1n \u0161a\u0330\u02d0<\/td>\n<\/tr>\n
    <\/td>\n\u0161u\u02d0n\u00fa\u02d0k<\/td>\nna\u2013li\u02d0\u2013\u0294e\u02d0\u2013chi\u02d0\u2013kan<\/td>\n\u0161a\u0330\u02d0<\/td>\n<\/tr>\n
    <\/td>\nbark<\/td>\nFUT<\/span>\u2013INST<\/span>\u2013back\u2013tie\u2013IDF<\/span><\/td>\nsweatlodge<\/td>\n<\/tr>\n
    <\/td>\n\u2018they will tie it onto the sweatlodge with bark\u2019<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    Not unexpectedly, this prefix typically adds an instrument to the event expressed by its base, but may also be used to add a motive for the event.<\/p>\n

    The comitative applicative adds a co-actor to the event:<\/p>\n\n\n\n\n\n\n
    (9)<\/td>\nnakinta\u0330\u02d0p\u00edna\u0330<\/td>\n<\/tr>\n
    <\/td>\nna\u2013kin\u2013ta\u0330\u02d0\u2013pin\u2013a\u0330<\/td>\n<\/tr>\n
    <\/td>\nFUT<\/span>\u20131OBJ<\/span>\u2013CMT<\/span>\u2013go:2SUB<\/span>\u2013IMPF:2SG.SUB<\/span><\/td>\n<\/tr>\n
    <\/td>\n\u2018you will go with me\u2019<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    As shown in (9), the co-actor performs the action described by the verb along with the subject.<\/p>\n

    The final applicative, the allative la\u0330\u0294-<\/em><\/span>, adds a goal to an event:<\/p>\n\n\n\n\n\n\n
    (10)<\/td>\ntala\u0330\u0294\u00e1\u0330\u026c xa\u0330\u02d0 \u1e2d\u0161tama\u02d0ki\u02d0n\u1e2d\u0301\u02d0 \u1e2d\u0161lu\u02d0wa\u0330k\u00e1\u0330n<\/td>\n<\/tr>\n
    <\/td>\nta\u2013la\u0330\u0294\u2013a\u0330n\u2013\u026c<\/td>\nxa\u0330\u02d0<\/td>\n\u1e2d\u0161\u2013ta\u2013ma\u02d0k\u00ed\u02d0\u2013n\u1e2d\u02d0<\/td>\n\u1e2d\u0161\u2013l\u00fa\u02d0wa\u0330\u2013ka\u0330n<\/td>\n<\/tr>\n
    <\/td>\n3PL.SUB<\/span>\u2013ALTV<\/span>\u2013go\u2013PFV<\/span><\/td>\nwhere<\/td>\nPAST<\/span>\u20133PL.SUB<\/span>\u2013keep\u2013PF<\/span><\/td>\n3PO<\/span>\u2013snake\u2013PL.PO<\/span><\/td>\n<\/tr>\n
    <\/td>\n\u2018they went to where they kept their snake\u2019<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    The allative applicative combines with only a limited set of motion verbs, mostly those based on the verbs a\u0330n<\/em><\/span> \u2018go\u2019 and min<\/em><\/span> \u2018come\u2019.<\/p>\n

    Do not just give complex data and then expect the reader<\/em> to figure them out<\/p>\n

    WRONG<\/h6>\n

    Lushootseed oblique-centred relative clauses like that in (11) require nominalization of the embedded verb:<\/p>\n\n\n\n\n\n\n\n
    (11)<\/td>\nx\u030c\u02b7ul\u2019 \u010d\u0259d \u026cul\u0259\u0294ux\u030c\u02b7tx\u02b7 ti\u0294\u0259\u0294 \u026cads\u0294\u0259\u026ctx\u02b7<\/td>\n<\/tr>\n
    <\/td>\nx\u030c\u02b7ul\u2019<\/td>\n\u010d\u0259d<\/td>\n\u026cu=l\u0259=\u0294ux\u030c\u02b7\u2013tx\u02b7<\/td>\nti\u0294\u0259\u0294<\/td>\n\u026cu=ad=s=\u0294\u0259\u026c\u2013tx\u02b7<\/td>\n<\/tr>\n
    <\/td>\nonly<\/td>\n1SG.SUB<\/span><\/td>\nIRR<\/span>=PROG<\/span>=go\u2013ECS<\/span><\/td>\nPROX<\/span><\/td>\nIRR<\/span>=2SG.PO<\/span>=NM<\/span>=eat\u2013ECS<\/span><\/td>\n<\/tr>\n
    <\/td>\n\u2018I will just be taking [them] what you will feed [them] with\u2019<\/td>\n<\/tr>\n
    <\/td>\n(Hess 1998: 58, line 56)<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    As in all such relatives, the nominalized clause realizes its \u201csubject\u201d as a possessor.<\/p>\n

    RIGHT<\/h6>\n

    Lushootseed oblique-centred relative clauses like that shown in the sentence in (12) require nominalization of the embedded verb, here \u0294\u0259\u026ctx\u02b7<\/em> \u2018feed sby with sth\u2019:<\/p>\n\n\n\n\n\n\n\n
    (12)<\/td>\nx\u030c\u02b7ul\u2019 \u010d\u0259d \u026cul\u0259\u0294ux\u030c\u02b7tx\u02b7 ti\u0294\u0259\u0294 \u026cads\u0294\u0259\u026ctx\u02b7<\/td>\n<\/tr>\n
    <\/td>\nx\u030c\u02b7ul\u2019<\/td>\n\u010d\u0259d<\/td>\n\u026cu=l\u0259=\u0294ux\u030c\u02b7\u2013tx\u02b7<\/td>\nti\u0294\u0259\u0294<\/td>\n\u026cu=ad=s=\u0294\u0259\u026c\u2013tx\u02b7<\/td>\n<\/tr>\n
    <\/td>\nonly<\/td>\n1SG.SUB<\/span><\/td>\nIRR<\/span>=PROG<\/span>=go\u2013ECS<\/span><\/td>\nPROX<\/span><\/td>\nIRR<\/span>=2SG.PO<\/span>=NM<\/span>=eat\u2013ECS<\/span><\/td>\n<\/tr>\n
    <\/td>\n\u2018I will just be taking [them] what you will feed [them] with\u2019<\/td>\n<\/tr>\n
    <\/td>\n(Hess 1998: 58, line 56)<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    In this example, the headless relative clause ti\u0294\u0259\u0294 \u026cads\u0294\u0259\u026ctx\u02b7<\/em><\/span> \u2018what you will feed them with\u2019 refers to the food, the oblique object of the verb \u0294\u0259\u026ctx\u02b7<\/em><\/span> \u2018feed sby with sth\u2019; because the referent of the clause is an oblique object, the clause is nominalized with the nominalizing clitic s=<\/em><\/span> and second person is realized as a possessive prefix, ad=<\/em><\/span>, rather than as a subject clitic.<\/p>\n

    Do not simply end a section or a topic with a dataset<\/p>\n

    WRONG<\/h6>\n

    A very common error writers make, usually in conjunction with the \u201cdon\u2019t discuss data you haven\u2019t presented” error, is giving data or placing an inset and then simply moving on to the next topic:<\/p>\n

    Datasets (and insets) should always be followed by a wrap-up either of the data (an explanation of the example) or of the topic<\/p>\n

    RIGHT<\/h6>\n

    A very common error writers make, usually in conjunction with the \u201cdon\u2019t discuss data you haven\u2019t presented” error, is giving data or placing an inset and then simply moving on to the next topic:<\/p>\n

    Datasets (and insets) should always be followed by a wrap-up either of the data (an explanation of the example) or of the topic<\/p>\n

    Avoiding this error\u00a0ensures good continuity and flow in your paper, and adhering to it usually forces you to think carefully about whether, indeed, you have made it clear enough to the reader what the data they just saw were actually about. It also gives you a chance to add corollary information that might be helpful to the discussion, such as the observation that following this last rule avoids the error of ending a paragraph with a dataset as well (since paragraphs usually enjoy some topical unity). Good stylistic practice usually dictates that the paragraph following a dataset not be indented (in styles with indentation on the first line of every paragraph).<\/p>\n","protected":false},"excerpt":{"rendered":"

    When presenting data in blocks or datasets in a linguistics paper (or, for that matter, presenting definitions or lists in inset blocks), it is important to keep in mind two basic principles: the data must be presented first, as soon as possible after first mention, before being discussed in detail; the data must be introduced … Continue reading Presenting data<\/span> →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"page-templates\/general.php","meta":{"_exactmetrics_skip_tracking":false,"_exactmetrics_sitenote_active":false,"_exactmetrics_sitenote_note":"","_exactmetrics_sitenote_category":0,"footnotes":""},"class_list":["post-329","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/www.americanlinguistics.org\/index.php?rest_route=\/wp\/v2\/pages\/329","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.americanlinguistics.org\/index.php?rest_route=\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.americanlinguistics.org\/index.php?rest_route=\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.americanlinguistics.org\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.americanlinguistics.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=329"}],"version-history":[{"count":86,"href":"https:\/\/www.americanlinguistics.org\/index.php?rest_route=\/wp\/v2\/pages\/329\/revisions"}],"predecessor-version":[{"id":2912,"href":"https:\/\/www.americanlinguistics.org\/index.php?rest_route=\/wp\/v2\/pages\/329\/revisions\/2912"}],"wp:attachment":[{"href":"https:\/\/www.americanlinguistics.org\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=329"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}