Received: from ARIZVM1.CCIT.ARIZONA.EDU by UICVM (Mailer R2.07) with BSMTP id
 8111; Wed, 14 Nov 90 14:12:56 CST
Received: from ARIZVM1 (LANGENDT) by ARIZVM1.CCIT.ARIZONA.EDU (Mailer R2.07)
 with BSMTP id 1249; Wed, 14 Nov 90 13:12:37 MST
Date:         Wed, 14 Nov 90 13:03:31 MST
From:         Terry Langendoen <LANGENDT@ARIZVM1>
Subject:      Markup of examples from Jackendoff, Semantic Structure
To:           Steve Anderson <anderson@sapir.cog.jhu.edu>,
              Nicoletta Calzolari <glottolo@icnucevm>,
              Mitch Marcus <mitch@linc.cis.upenn.edu>,
              Geoffrey Sampson <geoff@ling.leeds.ac.uk>,
              Beatrice Santorini <beatrice@unagi.cis.upenn.edu>,
              Gary Simons <gary@txsil.lonestar.org>,
              Lou Burnard <LOU@VAX.OXFORD.AC.UK>,
              Michael Sperberg-McQueen <U35395@UICVM>
 
This is the first of a series of sample markups using the encoding
scheme of Chapter 6 of the Preliminary Draft of the TEI.
I picked examples from Jackendoff's new book because they are
quite straightforwardly interpretable in terms of our scheme.
Let me have your comments and suggestions at your earliest
convenience.  I will be sending out additional samples over the
next week or so.
**********************************************************************
Jackendoff, Ray S. 1990. Semantic Structures. Cambridge, MA: MIT Press.
 
First example, on p.99.  In (38b) and in subsequent diagrams, the
corners of large brackets are indicated by "+" and a preceding or
following "-" to show orientation.
 
(38) a. Bill gave Harold $5 for mowing the lawn.
 
         +-                                           -+
     b.  | CAUSE ([BILL], [GO ([$5], [TO [HAROLD]])])  |
         | [EXCH [MOW ([HAROLD], [LAWN])]]             |
         +-                                           -+
 
Expanded version of (38b), which interprets the round brackets as
enclosing "arguments".  These are identified as ARG1 and ARG2.
Note that each pair of brackets corresponds to <tag>f.str</tag>.
One embedded f.str does not have a name; it's there simply to indicate
subordination.  (It corresponds to the structure opened by the
bracket preceding "EXCH" in (38b).)
       +-      +-                                   -+ -+
       | CAUSE | ARG1  [BILL]                        |  |
       |       |            +-                   -+  |  |
       |       | ARG2  GO   | ARG1  [$5]          |  |  |
       |       |            | ARG2  [TO [HAROLD]] |  |  |
       |       +-           +-                   -+ -+  |
       |  +-      +-     +-                -+ -+ -+     |
       |  | EXCH  | MOW  | ARG1  [HAROLD]   |  |  |     |
       |  |       |      | ARG2  [LAWN]     |  |  |     |
       +- +-      +-     +-                -+ -+ -+    -+
 
Proposed encoding of (38b).
 
<f.str>
  <feature>
    <f.name>CAUSE</f.name>
    <f.str>
      <feature>
        <f.name>ARG1</f.name>
        <f.str><terminal>BILL</terminal></f.str>
      </feature>
      <feature>
        <f.name>ARG2</f.name>
        <f.str>
          <feature>
            <f.name>GO</f.name>
            <f.str>
              <feature>
                <f.name>ARG1</f.name>
                <f.str><terminal>$5</terminal></f.str>
              </feature>
              <feature>
                <f.name>ARG2</f.name>
                <f.str>
                  <feature>
                    <f.name>TO</f.name>
                    <f.str><terminal>HAROLD</terminal></f.str>
                  </feature>
                </f.str>
              </feature>
            </f.str>
          </feature>
        </f.str>
      </feature>
    </f.str>
  </feature>
  <feature>
    <f.str>
      <feature>
        <f.name>EXCH</f.name>
        <f.str>
          <feature>
            <f.name>MOW</f.name>
            <f.str>
              <feature>
                <f.name>ARG1</f.name>
                <f.str><terminal>HAROLD</terminal></f.str>
              </feature>
              <feature>
                <f.name>ARG2</f.name>
                <f.str><terminal>LAWN</terminal></f.str>
              </feature>
            </f.str>
          </feature>
        </f.str>
      </feature>
    </f.str>
  </feature>
</f.str>
 
 
Second example, on p. 97.  In (30b), "Poss" is written as a
subscript on the previous item "GO".  From the text, we understand
that it is to be interpreted as a positively specified feature named
"POSSESSIVE".
 
(30) a. Bill obtained the book (in order) to give it to Harry.
 
     b. +-                                               -+
        | CAUSE ([BILL], [GO Poss ([BOOK], [TO [BILL]])]) |
        |                        +-                -+     |
        | [FOR [GO Poss ([BOOK], | FROM [BILL]      | )]] |
        |                        | TO [HARRY]       |     |
        +-                       +-                -+    -+
 
This diagram can be expanded as (38b) is, with "Poss" spelled out as a
feature whose value is "+".
      +-        +-                                     -+   -+
      |  CAUSE  | ARG1   [BILL]                         |    |
      |         |       +-   +-                  -+ -+  |    |
      |         | ARG2  | GO | POSSESSIVE    +    |  |  |    |
      |         |       |    | ARG1  [BOOK]       |  |  |    |
      |         |       |    | ARG2  [TO [BILL]]  |  |  |    |
      |         +-      +-   +-                  -+ -+ -+    |
      |  +-      +-     +-                         -+ -+ -+  |
      |  | FOR   | GO   | POSSESSIVE    +           |  |  |  |
      |  |       |      | ARG1  [BOOK]              |  |  |  |
      |  |       |      |      +-               -+  |  |  |  |
      |  |       |      | ARG2 | FROM   [BILL]   |  |  |  |  |
      |  |       |      |      | TO     [HARRY]  |  |  |  |  |
      +- +-      +-     +-     +-               -+ -+ -+ -+ -+
 
Proposed encoding of example (30b).
 
<f.str>
  <feature>
    <f.name>CAUSE</f.name>
    <f.str>
      <feature>
        <f.name>ARG1</f.name>
        <f.str><terminal>BILL</terminal></f.str>
      </feature>
      <feature>
        <f.name>ARG2</f.name>
        <f.str>
          <feature>
            <f.name>GO</f.name>
            <f.str>
              <feature>
                <f.name>POSSESSIVE</f.name><plus>
              </feature>
              <feature>
                <f.name>ARG1</f.name>
                <f.str><terminal>BOOK</terminal></f.str>
              </feature>
              <feature>
                <f.name>ARG2</f.name>
                <f.str>
                  <feature>
                    <f.name>TO</f.name>
                    <f.str><terminal>BILL</terminal></f.str>
                  </feature>
                </f.str>
              </feature>
            </f.str>
          </feature>
        </f.str>
      </feature>
    </f.str>
  </feature>
  <feature>
    <f.str>
      <feature>
        <f.name>FOR</f.name>
        <f.str>
          <feature>
            <f.name>GO</f.name>
            <f.str>
              <feature>
                <f.name>POSSESSIVE</f.name><plus>
              </feature>
              <feature>
                <f.name>ARG1</f.name>
                <f.str><terminal>BOOK</terminal></f.str>
              </feature>
              <feature>
                <f.name>ARG2</f.name>
                <f.str>
                  <feature>
                    <f.name>FROM</f.name>
                    <f.str><terminal>BILL</terminal></f.str>
                  </feature>
                  <feature>
                    <f.name>TO</f.name>
                    <f.str><terminal>HARRY</terminal></f.str>
                  </feature>
                </f.str>
              </feature>
            </f.str>
          </feature>
        </f.str>
      </feature>
    </f.str>
  </feature>
</f.str>
 
Third example, on p.111. The elements "c", "Place" and "Event"
are all subscripts interpreted as features.  "c" means "Contact".
 
(25) c. Beth stroked the cat on the neck.
           +-                                          -+
           |       GO c ([BETH], [VIA c [AT c [CAT]]])  |
           |       [ Place  ON ([NECK])]                |
           +- Event                                    -+
 
The diagram in (25c) can also be expanded, as above, but the expansion
is not shown here.
 
Proposed encoding for (25c).
 
<f.str>
  <feature>
    <f.name>EVENT</f.name><plus>
  </feature>
    <f.name>GO</f.name>
    <f.str>
      <feature>
        <f.name>CONTACT</f.name><plus>
      </feature>
      <feature>
        <f.name>ARG1</f.name>
        <f.str><terminal>BETH</terminal></f.str>
      </feature>
      <feature>
        <f.name>ARG2</f.name>
        <f.str>
          <feature>
            <f.name>VIA</f.name>
            <f.str>
              <feature>
                <f.name>CONTACT</f.name><plus>
              </feature>
              <feature>
                <f.name>AT</f.name>
                <f.str>
                  <feature>
                    <f.name>CONTACT</f.name><plus>
                  </feature>
                  <feature>
                    <f.str><terminal>CAT</terminal></f.str>
                  </feature>
                </f.str>
              </feature>
            </f.str>
          </feature>
        </f.str>
      </feature>
    </f.str>
  </feature>
  <feature>
    <f.str>
      <feature>
        <f.name>PLACE</f.name><plus>
      </feature>
      <feature>
        <f.name>ON</f.name>
        <f.str>
          <feature>
            <f.name>ARG1</f.name>
            <f.str><terminal>NECK</terminal></f.str>
          </feature>
        </f.str>
      </feature>
    </f.str>
  </feature>
</f.str>
 
Terry Langendoen             phone: (+1 602) 621-6898
Department of Linguistics    bitnet: langendt@arizvm1
University of Arizona        internet: langendt@arizvm1.ccit.arizona.edu
Tucson, AZ 85721 USA         fax: (+1 602) 621-9424