-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathcommonnouns.tex
6114 lines (5064 loc) · 252 KB
/
commonnouns.tex
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
\chapter{Frames and descriptions}
% \chapter[Common nouns, intransitive verbs, frames, the Partee puzzle
% and passengers][Common Nouns and Frames]{Common nouns, intransitive verbs, frames, the Partee puzzle
% and passengers}
%\markboth{CHAPTER \thechapter. COMMON NOUNS AND FRAMES}{}
\label{ch:commonnouns}
\setcounter{equation}{0}
\section[Montague's treatment of common nouns and individual
concepts][Montague's treatment of common nouns]{Montague's treatment of
common nouns and individual concepts}
The treatment of common nouns in Chapter~\ref{ch:gram} is encapsulated
in Lex$_{\mathrm{CommonNoun}}$ and carried over into
Chapter~\ref{ch:propnames} where it was modified to accommodate
parametric contents.
The idea is that for a common noun such as \textit{dog} there should
be a corresponding predicate `dog' with arity
$\langle$\textit{Ind}$\rangle$ as well as a phonological type
``dog''. Then an utterance event of the type ``dog'' will be
associated with the content in \nexteg{a} whose foreground is of type
\nexteg{b}.
\begin{ex}
\begin{subex}
\item $\ulcorner\lambda c$:\textit{Cntxt} . $\lambda r$:\smallrecord{\smalltfield{x}{\textit{Ind}}}
. \smallrecord{\smalltfield{e}{dog($r$.x)}}$\urcorner$
\item
(\textit{Cntxt}$\rightarrow$(\smallrecord{\smalltfield{x}{\textit{Ind}}} $\rightarrow$ \textit{RecType}))
\end{subex}
\label{ex:dog}
\end{ex}
Once we have applied the foreground of \preveg{a} to a context
(modelled as a record) we will obtain the function \nexteg{a} of type
\nexteg{b}
\begin{ex}
\label{ex:non-paradog}
\begin{subex}
\item $\lambda r$:\smallrecord{\smalltfield{x}{\textit{Ind}}}
. \smallrecord{\smalltfield{e}{dog($r$.x)}}
\item
(\smallrecord{\smalltfield{x}{\textit{Ind}}} $\rightarrow$ \textit{RecType})
\end{subex}
\end{ex}
There is a correspondence between this and Montague's treatment of
common nouns.
\cite{Montague1973} introduces predicates corresponding to common
nouns which in his type system are of the type $\langle\langle
s,e\rangle,t\rangle$. The type $\langle s,e\rangle$ for Montague is
the type of individual concepts. These are modelled as functions from
world-time pairs (of type $s$) to individuals (of type $e$). The
reason that Montague used this type rather than the simpler type
$\langle e,t\rangle$, that is, the type of functions from individuals
to truth-values, has to do with his treatment of the Partee puzzle
concerning temperatures and prices which we will take up below. Much
subsequent research has abandoned Montague's analysis using
individual concepts and used the simpler type $\langle e,t\rangle$.
This alternative would correspond to \nexteg{} in our terms.
\begin{ex}
\begin{subex}
\item $\lambda x$:\textit{Ind}
. \smallrecord{\smalltfield{e}{dog($x$)}}
\item (\textit{Ind} $\rightarrow$ \textit{RecType})
\end{subex}
\end{ex}
\textit{Ind} corresponds to Montague's type $e$, the type of entities
or individuals. Instead of Montague's $t$, the type of truth values we
have \textit{RecType}. Record types serve as our propositions. Thus
instead of mapping to a truth value (for Montague, following Frege,
the denotation corresponding to a proposition), we map to the
proposition itself (see the discussion in Chapter~\ref{ch:gram}, Section~\ref{sec:gram-semantics}).
We will argue that (\ref{ex:dog}) is preferable to \preveg{} in that records which
are arguments to such a function are frames and that, among other
things, frames as arguments enable us to account for the Partee
puzzle. One way of seeing this is that we are using frames to replace
Montague's use of individual concepts to approach this problem. In
this way our proposal is closely related to work by \cite{Loebner2015}. We made this proposal in previous work
\citep{Cooper2010,Cooper2012}. Here we will present a modification of
that proposal which uses frames to introduce scales and measure
functions and yields a more general treatment of the semantics of
verbs like \textit{rise} than we were able to give in the earlier
treatment. In addition it gives us a way of treating nouns like
\textit{passenger} where, at least on some readings, we seem to be
predicating of passenger events, rather than individual passengers.
We will also relate our treatment to other recent work on the
introduction of frame semantics into formal semantics.
\section{The Partee puzzle}
% Perhaps the most recent discussion of the Partee puzzle is that of
% \cite{Lobnerinprep}. As we will see, his proposal is closely related
% to our own.
The puzzle is one that Barbara Partee raised while
sitting in on an early presentation of the material that led to
\cite{Montague1973}. In its simplest form it is that \nexteg{c}
should follow from \nexteg{a,b} given some otherwise apparently
harmless assumptions.
\begin{ex}
\begin{subex}
\item The temperature is rising
\item The temperature is ninety
\item Ninety is rising
\end{subex}
\label{ex:parteepuzzle}
\end{ex}
Clearly, our intuitions are that \preveg{c} does not follow from
\preveg{a,b}. The assumptions that the error relies on are those given
in \nexteg{}.
\begin{ex}
\begin{subex}
\item \textit{temperature} is a
predicate of individuals
\item \textit{is} in (\ref{ex:parteepuzzle}b) represents identity
between individuals
\end{subex}
\end{ex}
Montague's solution was to abandon \preveg{a} and say that
`temperature' is a predicate not of individuals but of
individual \textit{concepts}, in his terms functions from world-time
pairs to individuals, thus introducing intensionality into predication
by common nouns. When we say (\ref{ex:parteepuzzle}a) we are
predicating `rise' not of an individual but of a function.
When we say (\ref{ex:parteepuzzle}b) we are saying that the
\textit{value} of the function at the current world and time is
identical with ninety. The technical machinery that Montague uses to
achieve this involves his predilection for general treatments.
He treats all common nouns as being predicates of individual
concepts. But in the case of all nouns other than \textit{price} or
\textit{temperature} in his fragment he requires that the individual
concepts are rigid designators, that is, they are constant functions
which return the same individual for every world-time pair. Similarly
intransitive verbs will correspond to predicates of individual
concepts but in the case of verbs other than \textit{rise} and
\textit{change} (in his fragment) there will be a predicate of the
value of the individual concept which holds just in case the verb
predicate holds of the individual concept. Finally \textit{be} is
treated as representing identity of the values of individual concepts
and a given time and world
and not identity of the individual concepts. Thus two distinct
individual concepts can have identical values at a given world and
time.
Given this machinery we can analyze the Partee puzzle represented in
(\ref{ex:parteepuzzle}) as follows. When we say that the temperature
is rising we are predicating `rise' of an individual concept, a
function from world-time pairs. Montague does not say what it might
mean for such a function to rise. There is, however, something
obvious that we could say, namely that if $f$ is such that
temperature($f$) at world $w$ and time $t$, then rise($f$) is true at world $w$ and time $t$ just
in case there is some time $t'$, $t'< t$ (``$t'$ is earlier than $t$''), and some time $t''$,
$t<t''$, such that $f(w,t')$ is less than $f(w,t'')$. (We may assume
that $f$ returns a (real) number for any world and time.) When we say
that the temperature $f$ is ninety at world $w$ and time $t$, what we
mean is that $f(w,t)=90$ (assuming that the interpretation of
\textit{ninety} is an individual concept $g$ such that for any world,
$w$, and time, $t$, $g(w,t)=90$). From this is does not follow that
ninety is rising, that is, rise($g$). After all, we have just said
that \textit{ninety} corresponds to a constant function which always
returns the same value and rising functions have to return different
values at different times.
We have now shown that Montague's analysis prevents the offending
inference from going through but we must also show that the inference
does go through in ``normal'' cases according to his analysis.
Consider \nexteg{}.
\begin{ex}
\begin{subex}
\item The dog is barking
\item The dog is Fido
\item Fido is barking
\end{subex}
\end{ex}
Here we do want \preveg{c} to follow as a conclusion from the premises
\preveg{a,b}. When we say that the dog is barking we are predicating
`bark' of a constant function $f$ since for an individual
concept to fall under the predicate `dog' it must be rigid,
i.e. return the same object for each world and time. Furthermore,
there is a predicate, call it `bark$_*$', such that for any $w$ and $t$, `bark$_*$' holds of
$f(w,t)$ just in case
`bark' holds of $f$. So in effect by predicating `bark'
of $f$ at $w$ and $t$, we are predicating `bark$_*$' of $f(w,t)$.
(Given Montague's notion of proposition, bark($f$) and
bark$_*$($f(w,t)$) are the \textit{same} proposition since they are
true at exactly the same possible worlds and times.) When we
say that the dog is Fido at $w$ and $t$ what we mean is that
$f(w,t)=g(w,t)$ where $g$ is the individual concept corresponding to
\textit{Fido}. According to Montague's theory of proper names $g$ too
will be a constant function always returning the same individual, say,
`fido'. Is Fido barking given these assumptions, that is, is
bark($g$) true at $w$ and $t$? There are a couple of ways to make the
argument. Since both $f$ and $g$ are constant functions if they have
the same value at any world and time they will have the same value at
all worlds and times, that is, given the classical set theoretic view
of functions that Montague is using, $f$ and $g$ will in fact be the
same function. Thus if we predicate anything of $f$ it will also hold
of $g$, since they are identical. The other argument involves the
nature of the predicate `bark'. Since bark($f$) is equivalent to
bark$_*$($f(w,t)$) and, given that $f(w,t)=g(w,t)$, bark$_*$($f(w,t)$)
is equivalent to bark$_*$($g(w,t)$), which in turn is equivalent to
bark($g$), then bark($f$) and bark($g$) are equivalent. Thus if
bark($f$) is true, then so is bark($g$).
Despite the obvious ingenuity and formal correctness of this solution
it fell into disuse. As \cite{Loebner2015} points out one objection
is to the interpretation of (\ref{ex:parteepuzzle}) as an identity
statement rather than the location of the temperature value on a
scale. This point was made by \cite{Jackendoff1979}, a paper which
has given rise to a trickle of remarks and replies in
\textit{Linguistic Inquiry} over a period of thirty years:
\cite{Lobner1981,Lasersohn2005a,Romero2008}. Part of Jackendoff's
argument is that in addition to \nexteg{a} we can also say \nexteg{b},
just as we can say \nexteg{c}.
\begin{ex}
\begin{subex}
\item The temperature is ninety
\item The temperature is at ninety
\item The airplane is at 6000 feet
\end{subex}
\end{ex}
We do not, he argues, feel the temptation to conclude \nexteg{c} from
\nexteg{a,b}.
\begin{ex}
\begin{subex}
\item The airplane is at 6000 feet
\item The airplane is rising
\item 6000 feet is/are rising
\end{subex}
\end{ex}
So neither should we feel the temptation to draw the offending
conclusion in the temperature puzzle since even though we say
\textit{the temperature is ninety} we mean \textit{the temperature is
at ninety}. Jackendoff does not point out, however, that there is
an important difference between the temperature and the airplane case,
namely that \nexteg{} does not mean the same as \preveg{a}, and to the
extent that it means anything it means something absurd which involves an
equality between an airplane and 6000 feet.
\begin{ex}
The airplane is 6000 feet
\end{ex}
If Jackendoff were right that \textit{is} can mean \textit{is at} why
would this be the case? \cite{Lobner1981} has a stronger argument
against Jackendoff. He points out that we cannot conclude \nexteg{c}
from \nexteg{a,b}
\begin{ex}
\begin{subex}
\item The temperature of the air in my refrigerator is the same as the
temperature of the air in your refrigerator
\item The temperature of the air in my refrigerator is rising
\item The temperature of the air in your refrigerator is rising
\end{subex}
\end{ex}
\cite{Lasersohn2005a} gives the example in \nexteg{} based on Löbner's
example.
\begin{ex}
\begin{subex}
\item The temperature in Chicago is rising
\item The temperature in Chicago is the very same as the temperature
in St. Louis
\item The temperature in St. Louis is rising
\end{subex}
\end{ex}
These examples are meant to show that there are similar cases to the
original Partee puzzle where the construction seems clearly equative
rather than locative. Note that we can mention identity explicitly as
in \nexteg{}.
\begin{ex}
The temperature in Chicago is identical with the temperature in St. Louis
\end{ex}
\cite{Romero2008} discusses examples with prices where it seems
intuitive that there are two readings, one where the inference does
not go through and one where it does.
\begin{ex}
\begin{subex}
\item The prices in supermarket $A$ are (the very same as) the prices
in supermarket $B$
\item Most prices in supermarket $A$ are rising
\item Most prices in supermarket $B$ are rising
\end{subex}
\end{ex}
On one reading (not the preferred one, I think) \preveg{a} means that
at the current time the prices just happen to be the same. In this
case the inference does not go through. The other reading is that the
prices in the two supermarkets are pegged to each other, perhaps
because they are owned by the same chain even though they have
different names. (Note that this is not quite the same as saying that
the prices are \textit{necessarily} the same which is the case that
Romero discusses. This is a matter of business strategy, not logic.
The supermarket owners \textit{could} have chosen not to peg the
prices to each other.) In this case the inference does go
through.\footnote{Actually, there is a further complication with these
examples involving plural quantifiers, which Romero does not
discuss. We also need an assumption that the two supermarkets have
sufficiently similar stock. If most of the prices are rising in
supermarket $A$ and supermarket $B$ only stocks those items whose
prices are not rising in supermarket $A$, then even though the
prices in the two supermarkets are the same (and pegged to each
other), the prices in supermarket $B$ are not rising.}
Despite all this discussion there is an important intuition in
Jackendoff's observation that the interpretation of \textit{the
temperature is ninety} involves the placement of the temperature on
a scale. In a sense Montague was recognizing this by modelling
temperature in terms of his individual concepts. He was giving us a
function which returns for each world and time an individual
(presumably a number) representing the temperature. Thus he could
account for the fact that the temperature is different at different
times. The problem is, though, that possible worlds (that is, total
ways the universe could be) do not have a single temperature, even at
a single point of time. The notion of individual concept he has is
simply not fine-grained enough to deal with temperature. One can
understand why Montague might not have wanted to pursue this matter
further in PTQ. He wanted to include the treatment of temperature in
his general treatment of intensions (functions from possible worlds
and times to objects of various types) but in order to get temperature
right he would have had to change this. One strategy would be to use
possible situations (parts of possible worlds). Another strategy
would have been to use an additional index, not just worlds and times
but also locations. But if he had done this for temperature and
maintained a general theory of intensions he would
have had to make all intensions be functions defined on triples of worlds, times
and locations and this would have raised issues about the relationship
between intensionality and indexicality which he was probably wise to
avoid at that point in the development. Nevertheless, it is an
important issue which nags at some of the central assumptions of
formal semantics as Montague was proposing it: namely, the use of possible worlds and evaluation
with respect to a finite set of indices some of which are in the
domain of intensions and some of which are contextual parameters.
Löbner's early work on this topic \citep{Lobner1979,Lobner1981}
treated this problem by removing what he called \textit{functional
concepts} (\textit{Funktionalbegriffe}) from the general notion of
intension and allowing them to have different numbers and
types of argument roles. These insights led him in later work
\citep{Lobner2014,Loebner2015} to adopt a frame semantic approach
where the parameters that are relevant for interpretation can vary
between different words and phrases and there is no fixed set of
indices as there was in the original work on formal semantics. This
is very much the same kind of proposal as in
\cite{Cooper2010,Cooper2012} although the historical precursors we had in
mind were different. In my case, the precursors were early work on
situation semantics such as \cite{BarwisePerry1983} and frame
semantics of the kind suggested in \cite{Fillmore1982,Fillmore1985}
and taken as a foundation for FrameNet
\citep[][\url{https://framenet.icsi.berkeley.edu}]{RuppenhoferEllsworthPetruckJohnsonScheffczyk2006}.
In Löbner's case, the inspiration for frames comes from the
psychological work of \cite{Barsalou1992,Barsalou1992a,Barsalou1999}.
\section{Frames as records}
Our leading idea in modelling frames is that they correspond to
records and that the \textit{roles} (or \textit{frame elements} in the
terminology of FrameNet) are represented by the record fields.
Records are in turn what we use to model situations so frames and
situations in our view turn out to be the same. Given that we are
working in a type theory which makes a clear distinction between types
and the objects which belong to those types it is a little unclear
whether what we call frame should be a record or a record type. We
need both and we will talk of frames (records) and frame types (record
types). For example, when we look up the frame Ambient\_temperature
(\url{https://framenet2.icsi.berkeley.edu/fnReports/data/frameIndex.xml?frame=Ambient_temperature})
in FrameNet we will take that to be an informal description of a frame
type which can be instantiated by the kinds of situations which are
described in the examples there. In our terms we can characterize a
type corresponding to a very stripped down version of FrameNet's
Ambient\_temperature which is sufficient for us to make the argument
we wish to make. This is the type \textit{AmbTempFrame} defined in \nexteg{}.
\begin{ex}
\record{\tfield{x}{\textit{Real}} \\
\tfield{loc}{\textit{Loc}} \\
\tfield{e}{temp(loc, x)}}
\label{ex:AmbTempFrame}
\end{ex}
This is different from the earlier proposal we made in
\cite{Cooper2012} which is given in \nexteg{}.
\begin{ex}
\record{\tfield{x}{\textit{Ind}} \\
\tfield{e-time}{\textit{Time}} \\
\tfield{e-location}{\textit{Loc}} \\
\tfield{c$_{\mathrm{temp\_at\_in}}$}{temp\_at\_in(e-time, e-location, x)}}
\end{ex}
The new proposal in (\ref{ex:AmbTempFrame}) differs from the old one in two
ways. Firstly we have removed the field for time. This is because we
now want to treat time in terms of strings of events rather than
introducing time-points as such. This follows
Fernando's strategy (for example in \citealp{Fernando2011}) and
relates to the discussion of the Russell-Wiener construction of time
in \cite{Kamp1979}. Secondly we have made the type in the `x'-field
(the field which will contain `ninety' in our example) be
\textit{Real} (``real number'') rather than \textit{Ind}
(``individual''). As \cite{Lasersohn2005a} points out the issue was
raised early in the literature as to whether numbers (or temperature
measurements at any rate) should be treated
as individuals in these examples or should be counted as belonging to
a separate type \citep{Bennett1974,Thomason1979}. In our earlier work
we assumed that temperatures were to be considered as individuals
because we had no reason to do otherwise. In the current analysis,
however, we want to build in a notion of scale which involves a
mapping to real numbers and therefore we will model temperatures as
real numbers. As we will see this will lead to a slight complication
in the compositional semantics so there is still an open issue as to
whether this is the right decision.
A scale is a function which maps frames (situations) to a real
number. Thus a scale for ambient temperature will be of the type
\nexteg{a} and the obvious function to choose of that type is the
function in \nexteg{b} which maps any ambient temperature frame to the
real number in its `x'-field.
\begin{ex}
\begin{subex}
\item (\textit{AmbTempFrame} $\rightarrow$ \textit{Real})
\item $\lambda r$:\textit{AmbTempFrame} . $r$.x
\end{subex}
\label{ex:scaleambtempframe}
\end{ex}
Let us call \preveg{b} $\zeta_{\mathrm{temp}}$. As a first approximation we can take an event of
a temperature rise to be a string of two temperature frames,
$r_1^\frown r_2$, where $\zeta_{\mathrm{temp}}(r_1) <
\zeta_{\mathrm{temp}}(r_2)$. Using a notation where $T^n$ is the type of
strings of length $n$ each of whose members are of type $T$ and where
for a given string, $s$, $s[0]$ is the first member of $s$, $s[1]$ the
second and so on, a first approximation to the type of temperature
rises could be \nexteg{}.
\begin{ex}
\record{\tfield{e}{\textit{AmbTempFrame}$^2$}\\
\tfield{c$_{\mathrm{rise}}$}{$\zeta_{\mathrm{temp}}$(e[0]) $<$ $\zeta_{\mathrm{temp}}$(e[1])}}
\end{ex}
In the c$_{\mathrm{rise}}$-field of \preveg{} we are using $<$ as an
infix notation for a predicate `less-than' with arity
$\langle$\textit{Real}, \textit{Real}$\rangle$ which obeys the
constraint in \nexteg{}.
\begin{ex}
less-than($n$, $m$) is non-empty (``true'') iff $n<m$
\end{ex}
One way to meet this constraint is to specify the witness conditions
for `less-than($n$, $m$)' as in \nexteg{}.
\begin{ex}
$e$ : less-than($n$, $m$) iff $n\varepsilon e$, $m\varepsilon e$ and $n<m$
\end{ex}
A more general type for temperature rises is given by \nexteg{} where
we abstract away from the particular temperature scale used by
introducing a field for the scale into the record type. This, for
example, allows for an event to be a temperature rise independent of
whether it is measured on the Fahrenheit or Celsius scales.
\begin{ex}
\record{\tfield{scale}{(\textit{AmbTempFrame} $\rightarrow$ \textit{Real})}\\
\tfield{e}{\textit{AmbTempFrame}$^2$}\\
\tfield{c$_{\mathrm{rise}}$}{scale(e[0]) $<$ scale(e[1])}}
\label{ex:ambtempwithscale}
\end{ex}
This type, though, is now too general to count as the type of
temperature rising events. To be of this type, it is
enough for there to be some scale on which the rise condition holds
and the scale is allowed to be any arbitrary function from temperature
frames to real numbers. Of course, it is possible to find some
arbitrary function which will meet the rise condition even if the
temperature is actually going down. For example, consider a function
which returns the number on the Celsius scale but with the sign (plus
or minus)
reversed making temperatures above 0 to be below 0 and \textit{vice
versa}. There are two ways we can approach this problem. One is to
make the type in the scale-field a subtype of (\textit{AmbTempFrame}
$\rightarrow$ \textit{Real}) which limits the scale to be one of a
number of standardly
accepted scales. This may be an obvious solution in the case of
temperature where it is straightforward to identify the commonly used
scales. However, scales are much more generally used in linguistic
meaning and people create new scales depending on the situation at
hand. % (Horn ????)
This makes it difficult to specify the
nature of the relevant scales in advance and we therefore prefer our
second way of approaching this problem.
The second way is to parametrize the type of temperature rising
events. By this we mean using a dependent type which maps a record
providing a scale to
a record type modelling the type of temperature rising events
according to that scale. The function in \nexteg{} is a dependent
type which is related in an obvious way to the record type in
\preveg{}.
\begin{ex}
$\lambda r$:\smallrecord{\smalltfield{scale}{(\textit{AmbTempFrame}
$\rightarrow$ \textit{Real})}} .\\
\hspace*{2em}\record{\tfield{e}{\textit{AmbTempFrame}$^2$}\\
\tfield{c$_{\mathrm{rise}}$}{$r$.scale(e[0]) $<$ $r$.scale(e[1])}}
\end{ex}
According to (\ref{ex:ambtempwithscale}) an event will be a
temperature rise if there is some scale according to which the appropriate
relation holds between the temperatures of the two stages of the event
which we are comparing. According to \preveg{} on the other hand,
there is no absolute type of a temperature rise. We can only say
whether an event is a temperature rise with respect to some scale or
other. If we choose some non-standard scale like the one that
reverses plus and minus temperatures as we suggested above then what
we normally call a fall in temperature will in fact be a rise in
temperature \textit{according to that scale}. You are in principle
allowed to choose whatever scale you like, though if you are using the
type in a communicative situation you had better make clear to your
interlocutor what scale you are using and perhaps also why you are
using this scale as opposed to one of the standardly accepted ones.
Like the parametric contents we introduced in
Chapter~\ref{ch:propnames}, the dependent types introduce a
presupposition-like component to communicative situations. We are
assuming the existence of some scale in the context.
Why do we characterize the domain of the function in \preveg{} in
terms of records containing a scale rather than just scales as in
\nexteg{}?
\begin{ex}
$\lambda \sigma$:(\textit{AmbTempFrame}
$\rightarrow$ \textit{Real}) .\\
\hspace*{2em}\record{\tfield{e}{\textit{AmbTempFrame}$^2$}\\
\tfield{c$_{\mathrm{rise}}$}{$\sigma$(e[0]) $<$ $\sigma$(e[1])}}
\end{ex}
The intuitive reason is that we want to think of the arguments to such
functions as being contexts, that is situations (frames) modelled as
records. The scale will normally be only one of many informational
components which can be provided by the context and the use of a
record type allows for there to be more components present. In
practical terms of developing an analysis it is useful to use a record
type to characterize the domain even if we have only isolated one
parameter since if further analysis should show that additional
parameters are relevant this will mean that we can add fields to the
domain type thereby restricting the domain of the function rather than
giving it a radically different type.
And indeed in this case we will now show that there is at least one
more relevant parameter that needs to be taken account of before we
have anything like a reasonable account of the type of temperature
rise events. In (\ref{ex:AmbTempFrame}) we specified that an ambient
temperature frame relates a real number (``the temperature'') to a
spatial location. And now we are saying that a temperature rise is a
string of two such frames where the temperature is higher in the
second frame. But we have not said anything about how the locations
in the two frames should be related. For example, suppose I have a
string of two temperature frames where the location in the first is
London and the location in the second is Marrakesh. Does that
constitute a rise in temperature (assuming that the temperature in the
second frame is higher than the one in the first)? Certainly not a
temperature rise in London, nor in Marrakesh. If you want to talk
about a temperature rise in a particular location then both frames
have to have that location and we need a way of expressing that
restriction. Of course, you can talk about temperature rises which
take place as you move from one place to another and which therefore
seem to involve distinct locations. However, it seems that even in
these cases something has to be kept constant between the two frames.
One might analyse it in terms of a constant path to which both
locations have to belong or as a constant relative location such as
the place where a particular person (or car, or airplane) is. You
cannot just pick two arbitrary temperature frames without holding
something constant which ties them together. We will deal here with
the simple case where the location is kept constant.\footnote{Although
in astronomical terms, of course, even a location like London is a
relative location, that is, where London is according to the
rotation of the earth and its orbit around the sun. Thus the simple
cases are not really different from the cases apparently involving
paths.} We will say that the background information for judging an
event as a temperature rise has to
include not only a scale but also a location which is held constant in
the two frames. This is expressed in \nexteg{}.
\begin{ex}
$\lambda r$:\smallrecord{\smalltfield{fix}{\smallrecord{\smalltfield{loc}{\textit{Loc}}}}\\
\smalltfield{scale}{(\textit{AmbTempFrame}
$\rightarrow$ \textit{Real})}} .\\
\hspace*{2em}\record{\tfield{e}{(\textit{AmbTempFrame}\d{$\wedge$}\smallrecord{\smallmfield{loc}{$r$.fix.loc}{\textit{Loc}}})$^2$}\\
\tfield{c$_{\mathrm{rise}}$}{$r$.scale(e[0]) $<$ $r$.scale(e[1])}}
\label{ex:temprisefixloc}
\end{ex}
Here the `fix'-field in the context is required to be a record which
provides a location. One reason for making the `fix'-field a record
rather than simply a location is that we will soon see an example
where more than one parameter needs to be fixed. It will also help us
ultimately in characterizing a general type for a rising event (not
just a rise in temperature) if we can refer to the type in the
`fix'-field as \textit{Rec} (``record'') rather than to list a
disjunction of all the various types of the parameters that can be
held constant in different cases.
The temperature rise event itself is now required to be a string of
two frames which belong to a subtype of \textit{AmbTempFrame}, namely
where the `loc'-field has been made manifest and is specified to have
the value specified for `loc' in the `fix'-field. Here we are using
the record in the `fix'-field of the argument to the function to
partially specify the type \textit{AmbTempFrame} by fixing values for
some of its fields. One can think of the `fix'-record as playing the
role of a partial
assignment of values to fields in the type. To emphasize this
important role and to facilitate making general statements without
having to name the particular fields involved, we shall use the
operation of specification or anchoring introduced on p.~\pageref{pg:anchoring}ff. This operation maps a record
type, $T$, and a record, $r$ to the result of specifying $T$ with $r$,
which we notate as $T\parallel r$.
% \begin{ex}
% \smallrecord{\smalltfield{$\ell_1$}{$T_1$}\\
% \smalltfield{$\ell_2$}{$T_2$}\\
% \smalltfield{$\ell_3$}{$T_3$}}$\parallel$
% \smallrecord{\field{$\ell_2$}{$a$}\\
% \field{$\ell_3$}{$b$}\\
% \field{$\ell_4$}{$c$}} =
% \smallrecord{\smalltfield{$\ell_1$}{$T_1$}\\
% \smallmfield{$\ell_2$}{$a$}{$T_2$}\\
% \smallmfield{$\ell_3$}{$b$}{$T_3$}}
%
% provided that $a:T_2$ and $b:T_3$
% \end{ex}
% In a case where for example $a:T_2$ but not $b:T_3$ we would have
% \nexteg{}.
% \begin{ex}
% \smallrecord{\smalltfield{$\ell_1$}{$T_1$}\\
% \smalltfield{$\ell_2$}{$T_2$}\\
% \smalltfield{$\ell_3$}{$T_3$}}$\parallel$
% \smallrecord{\field{$\ell_2$}{$a$}\\
% \field{$\ell_3$}{$b$}\\
% \field{$\ell_4$}{$c$}} =
% \smallrecord{\smalltfield{$\ell_1$}{$T_1$}\\
% \smallmfield{$\ell_2$}{$a$}{$T_2$}\\
% \smalltfield{$\ell_3$}{$T_3$}}
%
%
% \end{ex}
% The result \preveg{} would also have obtained if $T_3$ had not been a
% type but a pair consisting of a dependent type and a sequence of
% paths, that is, the kind of thing which in our standard abbreviation
% we represent as a predicate with a label as argument such as
% `walk($\ell_1$)'. A precise definition of this operation is given in
% Appendix~\ref{app:specrec}.
Using this notation we can rewrite (\ref{ex:temprisefixloc}) as
\nexteg{}.
\begin{ex}
$\lambda r$:\smallrecord{\smalltfield{fix}{\smallrecord{\smalltfield{loc}{\textit{Loc}}}}\\
\smalltfield{scale}{(\textit{AmbTempFrame}
$\rightarrow$ \textit{Real})}} .\\
\hspace*{2em}\record{\tfield{e}{(\textit{AmbTempFrame}$\parallel$$r$.fix)$^2$}\\
\tfield{c$_{\mathrm{rise}}$}{$r$.scale(e[0]) $<$ $r$.scale(e[1])}}
\label{ex:temprisespecfix}
\end{ex}
We will call \preveg{} \textit{TempRiseEvent} and its domain type
\textit{TempRiseEventCntxt}. This means that given a record, $c$, of
type \textit{TempRiseEventCntxt} we can make a judgement such as that
given in \nexteg{}.
\begin{ex}
$e$ : \textit{TempRiseEvent}$(c)$
\end{ex}
That is, we judge that $e$ is a temperature rising event according to
the context $c$.
This is still a very simple theory of what a temperature rise event
may be but it will be sufficient for our current purposes. How might
we use this to specify a content for the intransitive verb
\textit{rise} in a sentence like \textit{the temperature is rising}?
First we define a predicated `rise' which takes two arguments which
are both records. Thus the arity of `rise' is $\langle$\textit{Rec},
\textit{Rec}$\rangle$. The first record can be an ambient temperature
frame and the second a temperature rise event context. We specify
a witness condition associated with `rise' in \nexteg{}.
\begin{ex}
$e$ : rise$(r,c)$ if
\begin{quote}
$r$ : \textit{AmbTempFrame},\\
$c$ : \textit{TempRiseEventCntxt} and \\
$e$ : \textit{TempRiseEvent}$(c)$ \d{$\wedge$}
\smallrecord{
\smalltfield{e}{\smallrecord{
\smallmfield{t$_0$}{$r$}{\textit{AmbTempFrame}}}}}
\end{quote}
\end{ex}
Note first that in \preveg{} we use `if' rather than `iff'. This is
not the only witness condition which we will associate with `rise'; it
represents a sufficient but not necessary condition. Note also that
the third condition specifies that $e$ is a temperature rise event and
that the first item in the string of two ambient temperature frames
thus specified is the temperature frame $r$, that is, the first
argument to the predicate. (Recall that a string $e_1e_2$ is modelled
as the record in \nexteg{}.)
\begin{ex}
\record{
\field{t$_0$}{$e_1$}\\
\field{t$_1$}{$e_2$}}
\end{ex}
The intuition is, then, that when we predicate `rise' of an
ambient temperature frame, we are saying that it is the initial frame
in a temperature rising event. We can use this predicate in the
characterization of a parametric content for the verb \textit{rise},
given in \nexteg{}.
\begin{ex}
$\ulcorner\lambda c$:\smallrecord{
\footnotesize{\textit{Cntxt}}\\
\smalltfield{$\mathfrak{c}$}{\textit{TempRiseEventCntxt}}} .
$\lambda r$:\smallrecord{\smalltfield{x}{\textit{Rec}}} . \record{
\tfield{e}{rise($r$, $c.\mathfrak{c}$)}}$\urcorner$
\end{ex}
However, the verb \textit{rise} can be used to talk about other kinds
of rising events than temperature rises and we will need different
parametric contents for other cases.
We move on
now to price rise events. We will take \nexteg{} to be the type of
price frames, \textit{PriceFrame}.
\begin{ex}
\record{\tfield{x}{\textit{Real}} \\
\tfield{loc}{\textit{Loc}} \\
\tfield{commodity}{\textit{Ind}} \\
\tfield{e}{price(commodity, loc, x)}}
\end{ex}
The fields represented here are based on a much stripped down version
of the FrameNet frame \texttt{Commerce\_scenario} where our
`commdodity'-field corresponds to the frame element called `goods' and
the `x'-field corresponds to the frame element `money'. A price rise
is a string of two price frames where the value in the `x'-field is
higher in the second. Here, as in the case of a temperature rise, we need to keep
the location constant. It does not make sense to say that a price
rise has taken place if we compare a price in Marrakesh with a price
in London, even though the price in London may be higher. In the case
of price we also need to keep the commodity constant, something that
does not figure at all in ambient temperature. We cannot say that a
price rise has taken place if we have the price of tomatoes in the
first frame and the price of oranges in the second frame. Thus,
following the model of (\ref{ex:temprisespecfix}), we can characterize
the dependent type of price rises as \nexteg{}.
\begin{ex}
$\lambda
r$:\smallrecord{\smalltfield{fix}{\smallrecord{\smalltfield{loc}{\textit{Loc}}\\
\smalltfield{commodity}{\textit{Ind}}}}\\
\smalltfield{scale}{(\textit{PriceFrame}
$\rightarrow$ \textit{Real})}} .\\
\hspace*{2em}\record{\tfield{e}{(\textit{PriceFrame}$\parallel$$r$.fix)$^2$}\\
\tfield{c$_{\mathrm{rise}}$}{$r$.scale(e[0]) $<$ $r$.scale(e[1])}}
\end{ex}
We call \preveg{} \textit{PriceRiseEvent} and its domain type
\textit{PriceRiseEventCntxt}. We can add a new witness condition
associated with `rise'.
\begin{ex}
$e$ : rise$(r,c)$ if
\begin{quote}
$r$ : \textit{PriceFrame},\\
$c$ : \textit{PriceRiseEventCntxt} and \\
$e$ : \textit{PriceRiseEvent}$(c)$ \d{$\wedge$}
\smallrecord{
\smalltfield{e}{\smallrecord{
\smallmfield{t$_0$}{$r$}{\textit{PriceFrame}}}}}
\end{quote}
\end{ex}
We can construct a parametric content for the verb \textit{rise} which
exploits this witness condition. This is given in \nexteg{}.
\begin{ex}
$\ulcorner\lambda c$:\smallrecord{
\footnotesize{\textit{Cntxt}}\\
\smalltfield{$\mathfrak{c}$}{\textit{PriceRiseEventCntxt}}} .
$\lambda r$:\smallrecord{\smalltfield{x}{\textit{Rec}}} . \record{
\tfield{e}{rise($r$, $c.\mathfrak{c}$)}}$\urcorner$
\end{ex}
Finally we consider a third kind of rising event discussed in
\cite{Cooper2012} based on the example in \nexteg{}.
\begin{ex}
As they get to deck, they see the Inquisitor, calling out to a Titan
in the seas. The giant Titan rises through the waves, shrieking at the
Inquisitor.
\medskip
\hfill {\footnotesize
\url{http://en.wikipedia.org/wiki/Risen_(video_game)}}
\hfill {\footnotesize accessed 4th February, 2010}
\end{ex}
Here what needs to be kept constant in the rising event is the Titan.
What needs to change between the two frames in the event is the height
of the location of the Titan. Thus in this example the
location is \textit{not} kept constant. In order to analyze this we
can use location frames of the type \textit{LocFrame} as given in
\nexteg{}.
\begin{ex}
\record{\tfield{x}{\textit{Ind}} \\
\tfield{loc}{\textit{Loc}} \\
\tfield{e}{at(x, loc)}}
\end{ex}
The dependent type, \textit{LocRiseEvent}, with domain type \textit{LocRiseEventCntxt}, for a rise in location event is \nexteg{}.
\begin{ex}
$\lambda
r$:\smallrecord{\smalltfield{fix}{\smallrecord{\smalltfield{x}{\textit{Ind}}
}}\\
\smalltfield{scale}{(\textit{LocFrame}
$\rightarrow$ \textit{Real})}} .\\
\hspace*{2em}\record{\tfield{e}{(\textit{LocFrame}$\parallel$$r$.fix)$^2$}\\
\tfield{c$_{\mathrm{rise}}$}{$r$.scale(e[0]) $<$ $r$.scale(e[1])}}
\end{ex}
Here the obvious scale function does not simply return the value of a
field in the location frame. What is needed is a scale based on the
height of the location. One way to do this would be to characterize
the type of locations, \textit{Loc}, as the type of points in three-dimensional
Euclidean space. That is, we consider \textit{Loc} to be an
abbreviation for \nexteg{}.
\begin{ex}
\record{\tfield{x-coord}{\textit{Real}}\\
\tfield{y-coord}{\textit{Real}}\\
\tfield{z-coord}{\textit{Real}}}
\end{ex}
Each of the fields in \preveg{} corresponds to a coordinate in
Euclidean space. A more adequate treatment would be to consider
locations as regions in Euclidean space but we will not pursue that
here. Treating \textit{Loc} as \preveg{} means that we can
characterize the scale function, $\zeta_{\mathrm{height}}$, as returning the height of the
location in the location frame, as in \nexteg{}.
\begin{ex}
$\lambda r$:\textit{LocFrame} . $r$.loc.z-coord
\end{ex}
If we wish to restrict the dependent type of rising events to vertical
rises we can fix the $x$ and $y$-coordinates of the location as in
\nexteg{}.
\begin{ex}
$\lambda
r$:\smallrecord{\smalltfield{fix}{\smallrecord{\smalltfield{x}{\textit{Ind}}\\
\smalltfield{loc}{\smallrecord{\smalltfield{x-coord}{\textit{Real}}\\
\smalltfield{y-coord}{\textit{Real}}}}
}}\\
\smalltfield{scale}{(\textit{LocFrame}
$\rightarrow$ \textit{Real})}} .\\
\hspace*{2em}\record{\tfield{e}{(\textit{LocFrame}$\parallel$$r$.fix)$^2$}\\
\tfield{c$_{\mathrm{rise}}$}{$r$.scale(e[0]) $<$ $r$.scale(e[1])}}
\end{ex}
We can now add a new witness condition associated with `rise', given
in \nexteg{}.
\begin{ex}
$e$ : rise$(r,c)$ if
\begin{quote}
$r$ : \textit{LocFrame},\\
$c$ : \textit{LocRiseEventCntxt} and \\
$e$ : \textit{LocRiseEvent}$(c)$ \d{$\wedge$}
\smallrecord{
\smalltfield{e}{\smallrecord{
\smallmfield{t$_0$}{$r$}{\textit{LocFrame}}}}}
\end{quote}
\end{ex}
We can use this predicate to create a parametric content for the
intransitive verb \textit{rise}, as in \nexteg{}.
\begin{ex}
$\ulcorner\lambda c$:\smallrecord{
\footnotesize{\textit{Cntxt}}\\
\smalltfield{$\mathfrak{c}$}{\textit{LocRiseEventCntxt}}} .
$\lambda r$:\smallrecord{\smalltfield{x}{\textit{Rec}}} . \record{
\tfield{e}{rise($r$.x, $c.\mathfrak{c}$)}}$\urcorner$
\end{ex}
We have now characterized three kinds of rising events. In
\cite{Cooper2010,Cooper2012} we argued that there is in principle no
limit to the different kinds of rising events which can be referred to
in natural language and that new types are created on the fly as the
need arises. The formulation in those works did not allow us to
express what all these particular meanings have in common. We were
only able to say that the various meanings seem to have some kind of
family resemblance. Now that we have abstracted out scales and
parameters to be fixed we have an opportunity to formulate something
more general. There are two things that vary across the different
dependent types that we have characterized for risings. One is the
frame type being considered and the other is the type of the record which
contains the parameters held constant in the rising event. If we
abstract over both of these we have a characterization of rising
events in general. This is given in \nexteg{}.
\begin{ex}
$\lambda
r$:\smallrecord{\smalltfield{frame\_type}{\textit{RecType}}\\
\smalltfield{fix\_type}{\textit{RecType}}\\
\smalltfield{fix}{fix\_type}\\
\smalltfield{scale}{(frame\_type
$\rightarrow$ \textit{Real})}} .\\
\hspace*{2em}\record{\tfield{e}{($r$.frame\_type$\parallel$$r$.fix)$^2$}\\
\tfield{c$_{\mathrm{rise}}$}{$r$.scale(e[0]) $<$ $r$.scale(e[1])}}
\end{ex}
\preveg{} is so general (virtually everything of content has been
parametrized) that it may be hard to see it as being used in the
characterization of the meaning of \textit{rise}. What seems
important for characterizing the meanings of \textit{rise} that a
speaker has acquired is precisely the collection of frame types, and
associated fix types and scales which an agent has developed through
experience. \preveg{} seems to be relevant to a kind of meta-meaning
which specifies what kind of contents can be associated with the word
\textit{rise}. In this sense it seems related to the notion of
\textit{meaning potential}, a term which has its origins in the work
of \cite{Halliday1977} where meanings are spoken of informally as
being ``created by the social system'' and charaterized as
``integrated systems of meaning potential'' (p. 199). The notion is much
discussed in more recent literature, for example, \cite{Linell2009},
where meaning potential is discussed in the following terms: ``Lexical
meaning potentials are (partly) open meaning resources, where actual
meanings can only emerge in specific, situated interactions''
(p. 330). The parametric contents for \textit{rise} that we have
presented here (and included in the summary of resources in
Section~\ref{sec:summresch5}) are examples of what Linell is calling here ``actual meanings''.
\section{Frames and common nouns}
\label{sec:compsemPartee}
A central aspect of our analysis of the Partee puzzle is that the
contents of common nouns are functions that take frames, that is
records, as arguments. Nevertheless, we make a distinction between
individual level predicates like `dog' whose arity is
$\langle\textit{Ind}\rangle$ and frame level predicates like
`temperature' whose arity is $\langle\textit{Rec}\rangle$. Leaving
aside for now the need for parametric contents, the content for
associated with an utterance event of type ``dog'' would be
(\ref{ex:non-paradog}a) repeated here as \nexteg{a}. This is contrasted with
the content for an utterance of type ``temperature'' given in
\nexteg{b}.
\begin{ex}
\begin{subex}
\item $\lambda
r$:\smallrecord{\smalltfield{x}{\textit{Ind}}} . \record{\tfield{e}{dog($r$.x)}}
\item $\lambda
r$:\smallrecord{\smalltfield{x}{\textit{Rec}}} . \record{\tfield{e}{temperature($r$.x)}}
\end{subex}
\label{ex:dogtemperaturecont}
\end{ex}
We make an exactly similar distinction between individual level and
frame level verb phrases. In \nexteg{} we present contents which can
be associated with utterances of type ``run'' and ``rise''
respectively.
\begin{ex}
\begin{subex}
\item $\lambda
r$:\smallrecord{\smalltfield{x}{\textit{Ind}}}
. \record{\tfield{e}{run($r$.x)}}
\item $\lambda
r$:\smallrecord{\smalltfield{x}{\textit{Rec}}} . \record{\tfield{e}{rise($r$.x)}}
\end{subex}
\end{ex}
The types which we associate with the individual level and frame level properties in
(\ref{ex:dogtemperaturecont}) and \preveg{} are given in \nexteg{}.
\begin{ex}
\begin{subex}
\item (\smallrecord{\smalltfield{x}{\textit{Ind}}} $\rightarrow$ \textit{RecType})