LISTSERV mailing list manager LISTSERV 16.5

Help for TEI-L Archives


TEI-L Archives

TEI-L Archives


TEI-L@LISTSERV.BROWN.EDU


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Monospaced Font

LISTSERV Archives

LISTSERV Archives

TEI-L Home

TEI-L Home

TEI-L  December 1991

TEI-L December 1991

Subject:

Lexical structure encoding

From:

Terry Langendoen <[log in to unmask]>

Reply-To:

Terry Langendoen <[log in to unmask]>

Date:

Mon, 2 Dec 1991 12:01:47 MST

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (610 lines)

<tei.1>
<tei.header>
<file.description>
<title.statement>
<title>The construction of pointers for lexical encoding</title>
<statement.of.responsibility>
<role>author</role><name>D. Terence Langendoen</name>
</statement.of.responsibility>
<extent.statement></extent.statement>
<publication.statement>
Version for circulation on TEI-L file server on December 2, 1991.
</publication.statement>
<source.description>Revision of material contained in
<citn>TEI AI1 W9, section entitled <title.part>The construction of entity
definitions for lexical encoding</title.part></citn>.
</source.description>
</file.description>
<revision.history>
<change.note>
<who>DTL</who>
<date>1 December 1991</date>
<what>wrote first draft</what>
<rev.number>0</rev.number>
</change.note>
<change.note>
<who>DTL</who>
<date>2 December 1991</date>
<what>revisions and corrections</what>
<rev.number>1</rev.number>
</change.note>
</revision.history>
</tei.header>
<text>
<body>
<div1 name=section>
<head>Introduction
<div2 name=subsection>
<head>Background
<p>In <citn>TEI AI1 W9</citn>, Eanass Fahmy and I proposed a method for
constructing and using entities for representing the morphological
structures of the words in a document. At the Myrdal meeting, Steven
DeRose suggested that using pointers would provide for more control over
validation, make it easier to make changes and corrections to marked-up
texts, and speed up parsing and processing generally. This suggestion
met with approval at the Myrdal meeting, and I agreed to recast the
method in terms of pointers. While I have, in the interests of time,
limited the domain of application to the same sets of feature
structures, features and values as in <citn>TEI AI1 W9</citn>, I have
chosen to use a two-character, rather than a one-character, coding
scheme for feature names and values, in anticipation of the need to
extend the method to a larger subset of the features and values in
<citn>TEI AI1 W2</citn>. I also represent the person and number
features associated with verbs as part of a feature structure which is
the value of a feature named <term>agreement</term>, as in <citn>TEI AI1
W2</citn>.
<div2>
<head>Various assumptions about certain elements and attributes
<p>In this document, the following elements and attributes have been
renamed as follows.
<list type=ordered>
<enum>1. <item><tag>f.struct</tag> becomes <tag>fs</tag>
<enum>2. <item><tag>feature</tag> becomes <tag>f</tag>
<enum>3. <item><tag>atomic</tag> becomes <tag>atm</tag>
<enum>4. <item><tag>xref</tag> becomes <tag>x</tag>
<enum>5. <item><tag>f.s.or</tag> becomes <tag>or</tag>
<enum>6. <item><term>target</term> becomes <term>t</term>
</list>
<p>The following new tags and attributes are used.
<list type=ordered>
<enum>1. <item><tag>fs.lib</tag>
<enum>2. <item><tag>f.lib</tag>
<enum>3. <item><tag>any</tag>
<enum>4. <item><tag>default</tag>
<enum>5. <item><tag>unknown</tag>
<enum>6. <item><tag>not.applicable</tag>
<enum>7. <item><tag>no.claim</tag>
<enum>8. <item><term>element</term>, an attribute of <tag>x</tag>,
<tag>and</tag>, <tag>not</tag> and <tag>or</tag>, which takes as values
the names of elements.
</list>
<p>I propose <tag>fs.lib</tag> and <tag>f.lib</tag> to group together in
<term>libraries</term> sets of predefined <tag>fs</tag>s and
<tag>f</tag>s, with <term>id</term>s that can be pointed to from the
text or from within the libraries. I propose <tag>any</tag>,
<tag>default</tag>, <tag>unknown</tag>, <tag>not.applicable</tag> and
<tag>no.claim</tag> as empty tags to designate the predefined values for
underspecification spelled out in <citn>TEI AI1 W2</citn>.
<div1>
<head>Conventions for forming ID values
<div2>
<head>Two-character coding scheme for feature names and values
<p>First I give a two-character code for each of the feature names and
values in <citn>TEI AI1 W9, Coding of word-level features and values,
Coding of recurrent features and values, and Feature and value codes for
single categories</citn>.
<list.gl>
<head.term>feature name or value <head.gloss>code
<gl.term>category (part-of-speech) <gl.gloss>ps
<gl.term>noun <gl.gloss>nn
<gl.term>pronoun <gl.gloss>pn
<gl.term>adjective <gl.gloss>aj
<gl.term>article <gl.gloss>ar
<gl.term>adverb <gl.gloss>av
<gl.term>verb <gl.gloss>vb
<gl.term>preposition <gl.gloss>pp
<gl.term>coordinator <gl.gloss>cd
<gl.term>subordinator <gl.gloss>sb
<gl.term>particle <gl.gloss>pt
<gl.term>interjection <gl.gloss>ij
<gl.term>punctuation <gl.gloss>pu
<gl.term>person <gl.gloss>pe
<gl.term>first <gl.gloss>r1
<gl.term>second <gl.gloss>r2
<gl.term>third <gl.gloss>r3
<gl.term>number <gl.gloss>nu
<gl.term>singular <gl.gloss>sg
<gl.term>plural <gl.gloss>pl
<gl.term>gender <gl.gloss>ge
<gl.term>feminine <gl.gloss>fe
<gl.term>masculine <gl.gloss>ma
<gl.term>neuter <gl.gloss>ne
<gl.term>case <gl.gloss>ca
<gl.term>nominative <gl.gloss>nm
<gl.term>genitive <gl.gloss>gt
<gl.term>dative <gl.gloss>dt
<gl.term>accusative <gl.gloss>ac
<gl.term>degree <gl.gloss>de
<gl.term>positive <gl.gloss>g1
<gl.term>comparative <gl.gloss>g2
<gl.term>superlative <gl.gloss>g3
<gl.term>initial-capital <gl.gloss>il
<gl.term><tag>minus</tag> <gl.gloss>c0
<gl.term><tag>plus</tag> <gl.gloss>c1
    <!--<term>common</term> replaces <term>proper</term>
        to simplify the coding scheme -->
<gl.term>common <gl.gloss>co
<gl.term><tag>minus</tag> <gl.gloss>m0
<gl.term><tag>plus</tag> <gl.gloss>m1
<gl.term>possessive <gl.gloss>po
<gl.term><tag>minus</tag> <gl.gloss>s0
<gl.term><tag>plus</tag> <gl.gloss>s1
<gl.term>agreement <gl.gloss>ag
    <!--takes an <tag>fs</tag> as value whose <tag>f</tag>s are
        <term>person</term> and <term>number</term> -->
<gl.term>first singular <gl.gloss>r1sg
<gl.term>second singular <gl.gloss>r2sg
<gl.term>third singular <gl.gloss>r3sg
<gl.term>first plural <gl.gloss>r1pl
<gl.term>second plural <gl.gloss>r2pl
<gl.term>third plural <gl.gloss>r3pl
<gl.term>tense <gl.gloss>te
<gl.term>present <gl.gloss>pr
<gl.term>past <gl.gloss>pa
<gl.term>mood <gl.gloss>md
<gl.term>indicative <gl.gloss>in
<gl.term>imperative <gl.gloss>im
<gl.term>subjunctive <gl.gloss>sj
<gl.term>verb-form <gl.gloss>vf
<gl.term>finite <gl.gloss>fi
<gl.term>infinitive <gl.gloss>nf
<gl.term>gerund <gl.gloss>gr
<gl.term>participle <gl.gloss>pc
<gl.term>auxiliary <gl.gloss>au
<gl.term><tag>minus</tag> <gl.gloss>x0
<gl.term><tag>plus</tag> <gl.gloss>x1
<gl.term>orientation <gl.gloss>or
<gl.term>open <gl.gloss>op
<gl.term>close <gl.gloss>cl
<gl.term>matched <gl.gloss>mt
<gl.term>unary <gl.gloss>un
</list.gl>
<p>Second, the underspecification tags are given the following codes.
<list.gl>
<head.term>feature name or value <head.gloss>code
<gl.term><tag>any</tag> <gl.gloss>00
<gl.term><tag>default</tag> <gl.gloss>01
<gl.term><tag>unknown</tag> <gl.gloss>97
<gl.term><tag>not.applicable</tag> <gl.gloss>98
<gl.term><tag>no.claim</tag> <gl.gloss>99
</list.gl>
<div2>
<head>Formation of identifiers
<div3 name=subsubsection>
<head>Identifiers for <tag>f</tag>s
<p>Identifiers for <tag>f</tag>s are formed as in <citn>TEI AI1
W2</citn> by joining the code for the <term>name</term> and the
<term>value</term>, but without the hyphen. For example, the
<tag>f</tag> whose name is <term>number</term> and whose
value is <term>singular</term> receives the identifier
<term>nusg</term>, as in the following illustration.
<xmp id=ex1><![ CDATA [
<f id=nusg name=number><atm>singular
]]</xmp>
<p>Here is another example, this time using an underspecified value.
<xmp id=ex2><![ CDATA [
<f id=nu01 name=number><default>
]]</xmp>
<div3>
<head>Identifiers for <tag>fs</tag>s
<p>Identifiers for <tag>fs</tag>s are formed as in <citn>TEI AI1
W2</citn> by joining the codes for the values of the enclosed
<tag>f</tag>s.
<note place=foot>However, if an underspecified value is used, the code
for the name and the second digit of the value must be used if the
underspecified value is to appear in the <tag>fs</tag>
identifier.</note>
For example, the <tag>fs</tag> that designates a singular common noun
with no initial capital and which is understood by default as third
person (such as <cited.word>antiquity</cited.word>), can receive the
identifier <term>nnsgm1ilc0</term>, as in the following illustration.
<note place=foot>I assume that no coding for the default person value is
necessary in this situation.</note>
<xmp id=ex3><![ CDATA [
<fs id=nnsgm1ilc0>
   <x f t=psnn>
   <x f t=nusg>
   <x f t=com1>
   <x f t=ilc0>
   <x f t=pe01>
</fs>
]]</xmp>
<p>As the preceding illustration shows, the <tag>fs</tag> encloses
<tag>x</tag>s which point to the <tag>f</tag>s that they comprise.
<note place=foot>The <term>f</term> value is the value of the
<term>element</term> attribute of <tag>x</tag>.</note>
The intended semantics is that the <tag>f</tag>s that are pointed to are
copied (except for their <term>id</term> attributes) into the positions
of the <tag>x</tag>s. The <tag>x</tag>s could be given their own
<term>id</term> attributes if desired.
<p>The situation with <tag>f</tag>s which have <tag>fs</tag>s as values,
is somewhat more complicated. Suppose that a <tag>fs</tag> has an
<tag>f</tag> whose name is <term>agreement</term> whose value is another
<tag>fs</tag>, which encloses two <tag>f</tag>s, one whose name is
<term>person<term> with the value <term>third</term> and the other whose
name is <term>number</term> with the value <term>singular</term>.
The outer <tag>fs</tag> will have an identifier with the sequence
<term>r3sg</term> in it, and will contain an <tag>x</tag> which points
to an <tag>f</tag> with the identifier <term>agr3sg</term>. The latter
<tag>f</tag> will contain an <tag>fs</tag> with the identifier
<term>r3sg</term>, and this <tag>fs</tag> will contain two
<tag>x</tag>s, one pointing to an <tag>f</tag> with the identifier
<term>per3</term> and the other pointing to an <tag>f</tag> with the
identifier <term>nusg</term>. The situation is illustrated as follows.
<xmp id=ex4><![ CDATA [
<fs id=...r3sg...>
   <x f t=...>
      ...
   <x f t=agr3sg> -------------+
   <x f t=...> |
      ... |
</fs> |
                                |
<f id=agr3sg name=agreement> <--+
   <x fs t=r3sg> --------+
                         |
<fs id=r3sg> <-----------+
   <x f t=per3> ------------+
   <x f t=nusg> ------------x---+
</fs> | |
                            | |
<f id=per3 name=person> <---+ |
   <atm>third |
                                |
<f id=nusg name=number> <-------+
   <atm>singular
]]</xmp>
<p>For example, if the structure to be encoded is that of a present
tense, indicative, auxiliary verb showing third person singular number
agreement, such as <cited.word>has</cited.word> or
<cited.word>is</cited.word>, the incomplete <tag>fs</tag> in the
preceding illustration could be fleshed out as follows.
<xmp id=ex5><![ CDATA [
<fs id=vbr3sgprinx1>
   <x f t=psvb>
   <x f t=agr3sg>
   <x f t=tepr>
   <x f t=mdin>
   <x f t=vf01>
   <x f t=aux1>
</fs>
]]</xmp>
<div3>
<head>Identifiers for ambiguous structures
<p>Suppose one wished to mark up an occurrence of
<cited.word>thinner</cited.word> as ambiguous between an interpretation
as a singular noun and a comparative adjective. One way would be as a
disjunction of two <tag>x</tag>s with its own identifier formed by
concatenation from the identifiers for the <tag>x</tag>s, as in the
following illustration; the <tag>x</tag>s in turn point to the
<tag>fs</tag>s which make up the choice.
<xmp id=ex6><![ CDATA [
<or x id=nnsgajg2>
   <x fs t=nnsg>
   <x fs t=ajg2>
</or>
]]</xmp>
<p>A more elaborate example is provided by
<cited.word>fast</cited.word>, which one might wish to mark up as a
singular noun, a verb of some sort, an adjective or an adverb. A
possible encoding of this structure is the following.
<xmp id=ex7><![ CDATA [
<or x id=nnsgvbvf9ajg1avg1>
   <x fs t=nnsg>
   <x fs t=vbvf9>
   <x fs t=ajg1>
   <x fs t=avg1>
</or>
]]</xmp>
<p>Next suppose one wished to mark up an occurrence of
<cited.word>was</cited.word> as showing either first or third person
agreement. The <tag>or</tag> can be used to group either <tag>atm</tag>
or <tag>f</tag>, the latter requiring us to repeat the name of the
<tag>f</tag>. Since we have not seen the need to provide identifiers
for <tag>atm</tag>s (though it is certainly possible to do so), we will
take the latter option, despite its wordiness. First, we construct the
value of the <term>agreement</term> <tag>f</tag>.
<xmp id=ex8><![ CDATA [
<fs id=r1r3sg>
   <or x id=per1per3>
      <x f t=per1>
      <x f t=per3>
   </or
   <x f t=nusg>
</or>
]]</xmp>
The <term>agreement</term> <tag>f</tag> in turn looks as follows.
<xmp id=ex9><![ CDATA [
<f id=agr1r3sg name=agreement>
   <x fs t=r1r3sg>
]]</xmp>
<p>A possible encoding of the structure for <cited.word>was</cited.word>
would then be the following.
<xmp id=ex10><![ CDATA [
<fs id=vbr1r3sgpainx1>
   <x f t=psvb>
   <x f t=agr1r3sg>
   <x f t=tepa>
   <x f t=mdin>
   <x f t=vf01>
   <x f t=aux1>
</fs>
]]</xmp>
<p>Next, we consider how an encoding for <cited.word>have</cited.word>
as a present-tense inflected form can be constructed. We assume that
the agreement structure represents a choice between any person and
plural number or any number and either first or second person.
The first of these agreement structures has the following form.
<xmp id=ex11><![ CDATA [
<fs id=pe0pl>
   <x f t=pe00>
   <x f t=nupl>
</fs>
]]</xmp>
The second structure has the following form.
<xmp id=ex12><![ CDATA [
<fs id=r1r2nu0>
   <or x t=per1per2>
      <x f t=per1>
      <x f t=per2>
   </or>
   <x f t=nu00>
</fs>
]]</xmp>
<p>The agreement structure, then is an <tag>or</tag> as follows.
<xmp id=ex13><![ CDATA [
<or x id=pe0plr1r2nu0>
   <x fs t=pe0pl>
   <x fs t=r1r2nu0>
</or>
]]</xmp>
<p>It is pointed to by an <term>agreement</term> <tag>f</tag> as
follows.
<xmp id=ex14><![ CDATA [
<f id=agpe0plr1r2nu0 name=agreement>
   <x or t=pe0plr1r2nu0>
</or>
]]</xmp>
<p>The entire structure is as follows.
<xmp id=ex15><![ CDATA [
<fs id=vbpe0plr1r2nu0prinx1>
   <x f t=psvb>
   <x f t=agpe0plr1r2nu0>
   <x f t=tepr>
   <x f t=mdin>
   <x f t=vf01>
   <x f t=aux1>
</or>
]]</xmp>
<p>Finally, we consider the encoding of <cited.word>have</cited.word> as
ambiguous between an indicative, imperative, subjunctive and infinitive
form. As an indicative form, it has the structure just given. As an
imperative form, it can be assumed to show second person, any number
agreement. As a subjunctive form, it can be assumed to show agreement
with any person and number. As an infinitive form, agreement is not
applicable. We give here just the encoding of the outer <tag>or</tag>.
The details of the encoding can actually be inferred from the structure
of the identifiers. The character <q>.</q> is used to separate the
codes understood to be joined by <tag>and</tag>, and the identifier for
an <tag>and</tag> ends in that character.
<xmp id=ex16><![ CDATA [
<fs id= vb.pe0p1r1r2nu0prin.r2nu0prim.pe0nu0prsj.ag8te8md8nf.x1>
   <x f t=psvb>
   <or and id=pe0plr1r2nu0prin.r2nu0prim.pe0nu0prsj.ag8te8md8nf.>
      <and x id=vbpe0p1r1r2nu0prin.>
         <x f t=agpe0plr1r2nu0>
         <x f t=tepr>
         <x f t=mdin>
         <x f t=vf01>
      </and>
      <and x id=r2nu0prim.>
         <x f t=agr2nu0>
         <x f t=tepr>
         <x f t=mdim>
         <x f t=vf01>
      </and>
      <and x id=pe0nu0prsj.>
         <x f t=agpe0nu0>
         <x f t=tepr>
         <x f t=mdsj>
         <x f t=vf01>
      </and>
      <and x id=ag8te8md8nf.>
         <x f t=ag98>
         <x f t=te98>
         <x f t=md98>
         <x f t=vfnf>
      </and>
   </or>
   <x f t=aux1>
</fs>
]]</xmp>
<p>To avoid the use of <tag>and</tag> in cases like this, one could
require the use of an <tag>f</tag> named, say, <term>inflection</term>
(code <term>if</term>), whose value is an <tag>x</tag> which points to a
<tag>fs</tag> which encloses pointers to the various <tag>f</tag>s which
are represented by inflectional morphology, such as
<term>agreement</term>, <term>tense</term>, <term>mood</term>,
<term>verb-form</term>, <term>number</term>, <term>person</term>, etc.
Schematically, the result would look as follows.
<xmp id=ex17><![ CDATA [
<fs id= vbpe0plr1r2nu0prinr2nu0primpe0nu0prsjag8te8md8nfx1>
   <x f t=psvb>
   <x f t=ifpe0plr1r2nu0prinr2nu0primpe0nu0prsjag8te8md8nf> ------------+
   <x f t=aux1> |
</fs> |
                                                                        |
<f id=ifpe0plr1r2nu0prinr2nu0primpe0nu0prsjag9te9md9nf |
      name=inflection> <---------------+
   <x or t=pe0plr1r2nu0prinr2nu0primpe0nu0prsjag8te8md8nf> -----+
                                                                |
<or x id=pe0plr1r2nu0prinr2nu0primpe0nuprsjag8te8md8nf> <------+
   <x fs t=pe0p1r1r2nu0prin> ---+
   <x fs t=r2nu0prim> ----------x---+
   <x fs t=pe0nu0prsj> ---------x---x---+
   <x fs t=ag8te8md8nf> --------x---x---x---+
</or> | | | |
                                | | | |
<fs id=pe0plr1r2nu0prin> <-----+ | | |
   <x f t=agpe0plr1r2nu0> | | |
   <x f t=tepr> | | |
   <x f t=mdin> | | |
   <x f t=vf01> | | |
</fs> | | |
                                    | | |
<fs id=r2nu0prim> <----------------+ | |
   <x f t=agr2nu0> | |
   <x f t=tepr> | |
   <x f t=mdim> | |
   <x f t=vf01> | |
</fs> | |
                                        | |
<fs id=pe0nu0prsj> <-------------------+ |
   <x f t=agpe0nu0> |
   <x f t=tepr> |
   <x f t=mdsj> |
   <x f t=vf01> |
</fs> |
                                            |
<fs id=ag8te8md8nf> <----------------------+
   <x f t=ag98>
   <x f t=te98>
   <x f t=md98>
   <x f t=vfnf>
</fs>
]]</xmp>
<p>Systematic use of the <term>inflection</term> <tag>f</tag> would
significantly change the other encoding proposals made here, however.
<div1>
<head>Libraries of <tag>fs</tag>s and <tag>f</tag>s
<p>The <tag>fs</tag>s and the <tag>or</tag>s that group pointers to
<tag>fs</tag>s, can be collected together in one place either as an
external feature-structure library, or internally collected within an
<tag>fs.lib</tag>. The <tag>f</tag>s and the <tag>or</tag>s
that group pointers to <tag>f</tag>s, can be collected together in a
similar way; the internal collection occurring within an
<tag>f.lib</tag>.
<div1>
<head>Sample text markup
<p>Here is a markup of the first sentence of <citn>Mary Robinson,
Thoughts on the Condition of Women</citn> corresponding to what appears
in <citn>TEI AI1 W9, Sample document instance showing lexical
markup with implied word lemmatization</citn>. In the following
illustration, the lemmatization is made explicit by means of
<tag>s</tag>s. The <tag>hilited</tag>s and <tag>lb</tag>s have been
omitted.
<xmp id=ex16><![ CDATA [
<s id=w1>Custom<x fs t=nnsgm1c1></s>
<s id=w2>, <x fs t=puun></s>
<s id=w3>from <x fs t=pp></s>
<s id=w4>the <x fs t=ar></s>
<s id=w5>earlie&st; <x fs t=avg3></s>
<s id=w6>periods; <x fs t=nnplm1c0></s>
<s id=w7>of <x fs t=pp></s>
<s id=w8>antiquity<x fs t=nnsgm1c0></s>
<s id=w9>, <x fs t=puun></s>
<s id=w10>has <x fs t=vbr3sgprinx1></s>
<s id=w11>endeavored <x fs t=vbpapcx0></s>
<s id=w12>to <x fs t=sb></s>
<s id=w13>place <x fs t=vbnfx0></s>
<s id=w14>the <x fs t=ar></s>
<s id=w15>female <x fs t=ajde8></s>
<s id=w16>mind <x fs t=nnsgm1c0></s>
<s id=w17>in <x fs t=pp></s>
<s id=w18>the <x fs t=ar></s>
<s id=w19>subordinate <x fs t=ajde8></s>
<s id=w20>rank <x fs t=nnsgm1c0></s>
<s id=w21>of <x fs t=pp></s>
<s id=w22>intellectual <x fs t=ajde8></s>
<s id=w23>sociability<x fs t=nnsgm1c0></s>
<s id=w24>. <x fs t=puun></s>
]]</xmp>
<p>The <tag>fs.lib</tag> and <tag>f.lib</tag> remain to be provided.
</body>
<back>
<appendix>
<head>List of noncompound feature names and values by code
<list.gl>
<head.term>feature name or value <head.gloss>code
<gl.term><tag>any</tag> <gl.gloss>00
<gl.term><tag>default</tag> <gl.gloss>01
<gl.term><tag>unknown</tag> <gl.gloss>97
<gl.term><tag>not.applicable</tag> <gl.gloss>98
<gl.term><tag>no.claim</tag> <gl.gloss>99
<gl.term>accusative <gl.gloss>ac
<gl.term>agreement <gl.gloss>ag
<gl.term>adjective <gl.gloss>aj
<gl.term>article <gl.gloss>ar
<gl.term>auxiliary <gl.gloss>au
<gl.term>adverb <gl.gloss>av
<gl.term>initial-capital minus <gl.gloss>c0
<gl.term>initial-capital plus <gl.gloss>c1
<gl.term>case <gl.gloss>ca
<gl.term>coordinator <gl.gloss>cd
<gl.term>close <gl.gloss>cl
<gl.term>common <gl.gloss>co
<gl.term>degree <gl.gloss>de
<gl.term>dative <gl.gloss>dt
<gl.term>feminine <gl.gloss>fe
<gl.term>finite <gl.gloss>fi
<gl.term>positive <gl.gloss>g1
<gl.term>comparative <gl.gloss>g2
<gl.term>superlative <gl.gloss>g1
<gl.term>gender <gl.gloss>ge
<gl.term>gerund <gl.gloss>gr
<gl.term>genitive <gl.gloss>gt
<gl.term>interjection <gl.gloss>ij
<gl.term>initial-capital <gl.gloss>il
<gl.term>imperative <gl.gloss>im
<gl.term>indicative <gl.gloss>in
<gl.term>common minus <gl.gloss>m0
<gl.term>common plus <gl.gloss>m1
<gl.term>masculine <gl.gloss>ma
<gl.term>mood <gl.gloss>md
<gl.term>matched <gl.gloss>mt
<gl.term>neuter <gl.gloss>ne
<gl.term>infinitive <gl.gloss>nf
<gl.term>nominative <gl.gloss>nm
<gl.term>noun <gl.gloss>nn
<gl.term>number <gl.gloss>nu
<gl.term>open <gl.gloss>op
<gl.term>orientation <gl.gloss>or
<gl.term>past <gl.gloss>pa
<gl.term>participle <gl.gloss>pc
<gl.term>person <gl.gloss>pe
<gl.term>plural <gl.gloss>pl
<gl.term>pronoun <gl.gloss>pn
<gl.term>possessive <gl.gloss>po
<gl.term>preposition <gl.gloss>pp
<gl.term>present <gl.gloss>pr
<gl.term>category (part-of-speech) <gl.gloss>ps
<gl.term>particle <gl.gloss>pt
<gl.term>punctuation <gl.gloss>pu
<gl.term>first <gl.gloss>r1
<gl.term>second <gl.gloss>r2
<gl.term>third <gl.gloss>r1
<gl.term>possessive minus <gl.gloss>s0
<gl.term>possesive plus <gl.gloss>s1
<gl.term>subordinator <gl.gloss>sb
<gl.term>singular <gl.gloss>sg
<gl.term>subjunctive <gl.gloss>sj
<gl.term>tense <gl.gloss>te
<gl.term>unary <gl.gloss>un
<gl.term>verb <gl.gloss>vb
<gl.term>verb-form <gl.gloss>vf
<gl.term>auxiliary minus <gl.gloss>x0
<gl.term>auxiliary plus <gl.gloss>x1
</list.gl>
</text>
</tei.1>

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002
December 2001
November 2001
October 2001
September 2001
August 2001
July 2001
June 2001
May 2001
April 2001
March 2001
February 2001
January 2001
December 2000
November 2000
October 2000
September 2000
August 2000
July 2000
June 2000
May 2000
April 2000
March 2000
February 2000
January 2000
December 1999
November 1999
October 1999
September 1999
August 1999
July 1999
June 1999
May 1999
April 1999
March 1999
February 1999
January 1999
December 1998
November 1998
October 1998
September 1998
August 1998
July 1998
June 1998
May 1998
April 1998
March 1998
February 1998
January 1998
December 1997
November 1997
October 1997
September 1997
August 1997
July 1997
June 1997
May 1997
April 1997
March 1997
February 1997
January 1997
December 1996
November 1996
October 1996
September 1996
August 1996
July 1996
June 1996
May 1996
April 1996
March 1996
February 1996
January 1996
December 1995
November 1995
October 1995
September 1995
August 1995
July 1995
June 1995
May 1995
April 1995
March 1995
February 1995
January 1995
December 1994
November 1994
October 1994
September 1994
August 1994
July 1994
June 1994
May 1994
April 1994
March 1994
February 1994
January 1994
December 1993
November 1993
October 1993
September 1993
August 1993
July 1993
June 1993
May 1993
April 1993
March 1993
February 1993
January 1993
December 1992
November 1992
October 1992
September 1992
August 1992
July 1992
June 1992
May 1992
April 1992
March 1992
February 1992
January 1992
December 1991
November 1991
October 1991
September 1991
August 1991
July 1991
June 1991
May 1991
April 1991
March 1991
February 1991
January 1991
December 1990
November 1990
October 1990
September 1990
August 1990
July 1990
June 1990
April 1990
March 1990
February 1990
January 1990

ATOM RSS1 RSS2



LISTSERV.BROWN.EDU

CataList Email List Search Powered by the LISTSERV Email List Manager