<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE owl [ 
	<!ENTITY rdf "http://www.w3.org/1999/02/22-rdf-syntax-ns#">
	<!ENTITY rdfs "http://www.w3.org/2000/01/rdf-schema#">
	<!ENTITY xsd "http://www.w3.org/2001/XMLSchema#">
	<!ENTITY owl "http://www.w3.org/2002/07/owl#">
	<!ENTITY xsi "http://www.w3.org/2001/XMLSchema-instance">
]>
<rdf:RDF  xmlns:rdf="&rdf;" xmlns:rdfs="&rdfs;" xmlns:owl="&owl;" xmlns="http://www.emeld.org/gold.owl#" xmlns:xsi="&xsi;">
	<owl:Ontology rdf:about="">
		<rdfs:comment>This document contains a *working draft* the General Ontology for Linguistic Description (GOLD) in OWL format, an ontology that was developed by several individuals at the University of Arizona as a part of the EMELD (Electronic Metastructure Endangered Language Data) project. Contributors of ontological content include: D. Terence Langendoen, Scott Farrar, William D. Lewis, Peter Norquest. The following people gave much advice in the development of GOLD: Adam Pease (Teknowledge), Ian Niles (Teknowledge) Also, we gained much insight from a taxonomy of linguistic categories provided by the Summer Institute of Linguistics (SIL). Just as a convention, this ontology capitalizes the first letter of names of classes and individuals (e.g., 'BoundUnit') but uses lower case for names of relations, called properties in OWL (e.g., 'realizes'). This version is the first to be validated using the owl validator found at http://owl.bbn.com/validator/. Changes since the last version include: included more categories based on EMELD-MI and FIELD team input.</rdfs:comment>
		<rdfs:label>GOLD</rdfs:label>
		<owl:versionInfo>2004-01-22, edited by Scott Farrar</owl:versionInfo>
	</owl:Ontology>
	<!-->
	<owl:Class rdf:ID="">
		<rdfs:label xml:lang="en"></rdfs:label>
		<rdfs:comment></rdfs:comment>
		<rdfs:subClassOf rdf:resource="#"/>
	</owl:Class>
	</-->
	<!-->
	***************************************************************
	*Begin concepts from SUMO
	***************************************************************
	</-->
	<owl:Class rdf:ID="Entity">
		<rdfs:label xml:lang="en">Entity</rdfs:label>
		<rdfs:comment>The universal class of individuals. This is the root node of the ontology.</rdfs:comment>
		<rdfs:subClassOf rdf:resource="&owl;Thing"/>
	</owl:Class>
	<owl:Class rdf:ID="Physical">
		<rdfs:label xml:lang="en">Physical</rdfs:label>
		<rdfs:comment>An entity that has a location in space-time.  Note that locations are themselves understood to have a location in space-time.</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#Entity"/>
	</owl:Class>
	<owl:Class rdf:ID="Object">
		<rdfs:label xml:lang="en">Object</rdfs:label>
		<rdfs:comment>Corresponds roughly to the class of ordinary objects.  Examples include normal physical objects, geographical regions, and locations of Processes, the complement of Objects in the Physical class.  In a 4D ontology, an Object is something whose spatiotemporal extent is thought of as dividing into spatial parts roughly parallel to the time-axis.</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#Physical"/>
	</owl:Class>
	<owl:Class rdf:ID="SelfConnectedObject">
		<rdfs:label xml:lang="en">SelfConnectedObject</rdfs:label>
		<rdfs:comment>A SelfConnectedObject is any Object that does not consist of two or more disconnected parts.</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#Object"/>
	</owl:Class>
	<owl:Class rdf:ID="ContentBearingObject">
		<rdfs:label xml:lang="en">ContentBearingObject</rdfs:label>
		<rdfs:comment>Any SelfConnectedObject that expresses information.</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#SelfConnectedObject"/>
	</owl:Class>
	<!-->
	Process
	
	
	</-->
	<owl:Class rdf:ID="Process">
		<rdfs:label xml:lang="en">Process</rdfs:label>
		<rdfs:comment>Intuitively, the class of things that happen and have temporal parts or stages.  Examples include extended events like a football match or a race, actions like Searching and Reading, and biological processes. The formal definition is: anything that lasts for a time but is not an Object.  Note that a Process may have participants 'inside' it which are Objects, such as the players in a football match.  In a 4D ontology, a Process is something whose spatiotemporal extent is thought of as dividing into temporal stages roughly perpendicular to the time-axis.</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#Physical"/>
	</owl:Class>
	<owl:Class rdf:ID="Abstract">
		<rdfs:label xml:lang="en">Abstract</rdfs:label>
		<rdfs:comment>Properties or qualities as distinguished from any particular embodiment of the properties/qualities in a physical medium.  Instances of Abstract can be said to exist in the same sense as mathematical objects such as sets and relations, but they cannot exist at a particular place and time without some physical encoding or embodiment.</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#Entity"/>
	</owl:Class>
	<owl:Class rdf:ID="SetOrClass">
		<rdfs:label xml:lang="en">SetOrClass</rdfs:label>
		<rdfs:comment>The SetOrClass of Sets and Classes, i.e. any instance 
of Abstract that has elements or instances.</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#Abstract"/>
	</owl:Class>
	<owl:Class rdf:ID="Class">
		<rdfs:label xml:lang="en">Class</rdfs:label>
		<rdfs:comment>Classes differ from Sets in two important respects.  First, Classes are not assumed to be extensional.  That is, distinct Classes might well have exactly the same instances.  Second, Classes typically have an associated `condition' that determines the instances of the Class.  So, for example, the condition `human' determines the Class of Humans.  Note that some Classes might satisfy their own condition (e.g., the Class of Abstract things is Abstract) and hence be instances of themselves.</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#SetOrClass"/>
	</owl:Class>
	<owl:Class rdf:ID="Set">
		<rdfs:label xml:lang="en">Set</rdfs:label>
		<rdfs:comment>SetOrClass that satisfies extensionality as well as other constraints specified by some choice of set theory.  Sets differ from Classes in two important respects.  First, Sets are extensional - two Sets with the same elements are identical.  Second, a Set can be an arbitrary stock of objects.  That is, there is no requirement that Sets have an associated condition that determines their membership.</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#SetOrClass"/>
	</owl:Class>
	<owl:Class rdf:ID="Attribute">
		<rdfs:label xml:lang="en">Attribute</rdfs:label>
		<rdfs:comment>Qualities which we cannot or choose not to reify into subclasses of Object.</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#Abstract"/>
	</owl:Class>
	<owl:Class rdf:ID="InternalAttribute">
		<rdfs:label xml:lang="en">InternalAttribute</rdfs:label>
		<rdfs:comment>Any Attribute of an Entity that is an internal property of the Entity, e.g. its shape, its color, its fragility, etc.</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#Attribute"/>
	</owl:Class>
	<owl:Class rdf:ID="Relation">
		<rdfs:label xml:lang="en">Relation</rdfs:label>
		<rdfs:subClassOf rdf:resource="#Abstract"/>
		<rdfs:comment>The Class of relations.  There are three kinds of Relation: Predicate, Function, and List.  Predicates and 
Functions both denote sets of ordered n-tuples.  The difference between 
these two Classes is that Predicates cover formula-forming operators, while 
Functions cover term-forming operators.  A List, on the other hand, is a 
particular ordered n-tuple.</rdfs:comment>
	</owl:Class>
	<owl:Class rdf:ID="List">
		<rdfs:label xml:lang="en">List</rdfs:label>
		<rdfs:subClassOf rdf:resource="#Relation"/>
		<rdfs:comment>Every List is a particular ordered n-tuple of 
items.  Generally speaking, Lists are created by means of the ListFn 
Function, which takes any number of items as arguments and returns a 
List with the items in the same order.  Anything, including other 
Lists, may be an item in a List.  Note too that Lists are 
extensional - two lists that have the same items in the same order are 
identical.  Note too that a List may contain no items.  In that case, 
the List is the NullList.</rdfs:comment>
	</owl:Class>
	<!-->
	***************************************************************
	*Begin GOLD specific concepts
	***************************************************************
	</-->
	<!-->
	***************************************************************
	*Begin written linguistic expressions
	***************************************************************
	</-->
	<owl:Class rdf:ID="WrittenExpression">
		<rdfs:label xml:lang="en">WrittenExpression</rdfs:label>
		<rdfs:comment>A very general category subsuming any entity which is the product writing process. WrittenExpressions are necessarily symbolic.</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#ContentBearingObject"/>
		<rdfs:subClassOf>
			<owl:Restriction>
				<owl:onProperty rdf:resource="#hasForm"/>
				<owl:cardinality rdf:datatype="&xsd;nonNegativeInteger">1</owl:cardinality>
			</owl:Restriction>
		</rdfs:subClassOf>
	</owl:Class>
	<owl:Class rdf:ID="Character">
		<rdfs:label xml:lang="en">Character</rdfs:label>
		<rdfs:comment>Character is the minimal orthographic unit.</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#WrittenExpression"/>
	</owl:Class>
	<owl:Class rdf:ID="SymbolicString">
		<rdfs:label xml:lang="en">SymbolicString</rdfs:label>
		<rdfs:comment>SymbolicString is a sequence of one or more Characters.</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#WrittenExpression"/>
	</owl:Class>
	<owl:Class rdf:ID="OrthographicExpression">
		<rdfs:label xml:lang="en">OrthographicExpression</rdfs:label>
		<rdfs:comment>An OrthographicExpression is an orthographic unit composed of the standard characters of an orthographic system. An OrthographicExpression is governed by the orthographic combinatorial rules of a particular language. OrthographicExpressions are not transcriptions of any external entity, but independent linguistic expressions which refer directly to the LinguisticUnits of the language. They are expressions of some human language, possibly no longer spoken.</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#SymbolicString"/>
	</owl:Class>
	<owl:Class rdf:ID="OrthPart">
		<rdfs:label xml:lang="en">OrthPart</rdfs:label>
		<rdfs:comment>OrthPart is the subclass of written expressions whose members are not orthographically independent, that is, they cannot stand alone as words but compose to form words. Note that an OrthPart is not the same as a single character. Although, some OrthParts are characters.</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#OrthographicExpression"/>
	</owl:Class>
	<owl:Class rdf:ID="SimpleOrthPart">
		<rdfs:label xml:lang="en">SimpleOrthPart</rdfs:label>
		<rdfs:comment>SimpleOrthPart is the subclass of OrthPart whose members cannt be decomposed further into other instances of SimpleOrthPart.</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#OrthPart"/>
	</owl:Class>
	<owl:Class rdf:ID="OrthRoot">
		<rdfs:label xml:lang="en">OrthRoot</rdfs:label>
		<rdfs:comment>Some expression is an OrthRoot if it realizes a LinguisticUnit which is either a Bound or FreeRoot.</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#OrthPart"/>
	</owl:Class>
	<owl:Class rdf:ID="OrthAffix">
		<rdfs:label xml:lang="en">OrthAffix</rdfs:label>
		<rdfs:comment>An OrthAffix is a OrthPart that is joined before, after, around, or within an OrthRoot or OrthStem (Crystal 1980: 17; Hartmann and Stork 1972: 6; Mish et al. 1990: 62).</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#OrthPart"/>
	</owl:Class>
	<owl:Class rdf:ID="OrthPrefix">
		<rdfs:label xml:lang="en">OrthPrefix</rdfs:label>
		<rdfs:comment>An OrthPrefix is an OrthAffix that is joined before a OrthRoot or OrthStem (Crystal 1980: 281; Hartmann and Stork 1972: 182; Mish et al. 1990: 927).</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#OrthAffix"/>
	</owl:Class>
	<owl:Class rdf:ID="OrthInfix">
		<rdfs:label xml:lang="en">OrthInfix</rdfs:label>
		<rdfs:comment>An OrthInfix is an OrthAffix that is inserted within a OrthRoot (Hartmann and Stork 1972: 111).</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#OrthAffix"/>
	</owl:Class>
	<owl:Class rdf:ID="OrthSuffix">
		<rdfs:label xml:lang="en">OrthSuffix</rdfs:label>
		<rdfs:comment>A OrthSuffix is an OrthAffix that is attached to the end of a OrthRoot or OrthStem (Crystal 1980: 340; Hartmann and Stork 1972: 226; Mish et al. 1990: 1179).</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#OrthAffix"/>
	</owl:Class>
	<owl:Class rdf:ID="OrthCircumfix">
		<rdfs:label xml:lang="en">OrthCircumfix</rdfs:label>
		<rdfs:comment>An OrthCircumfix is an OrthAffix that is attached around a OrthRoot or OrthStem </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#OrthAffix"/>
	</owl:Class>
	<owl:Class rdf:ID="OrthStem">
		<rdfs:label xml:lang="en">OrthStem</rdfs:label>
		<rdfs:comment>An OrthStem realizes either a Boundor FreeStem.</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#OrthPart"/>
	</owl:Class>
	<owl:Class rdf:ID="OrthWord">
		<rdfs:label xml:lang="en">OrthWord</rdfs:label>
		<rdfs:comment>An OrthWord is the fundamental unit of an orthography, usually set off by white space.</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#OrthographicExpression"/>
	</owl:Class>
	<owl:Class rdf:ID="SimpleOrthWord">
		<rdfs:label xml:lang="en">SimpleOrthWord</rdfs:label>
		<rdfs:comment>A SimpleOrthWord has no internal parts which are also WrittenExpressions.</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#OrthWord"/>
	</owl:Class>
	<owl:Class rdf:ID="ComplexOrthWord">
		<rdfs:label xml:lang="en">ComplexOrthWord</rdfs:label>
		<rdfs:comment>A ComplexOrthWord is made up of two or more OrthographicExpressions.</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#OrthWord"/>
	</owl:Class>
	<owl:Class rdf:ID="OrthCompound">
		<rdfs:label xml:lang="en">OrthCompound</rdfs:label>
		<rdfs:comment>An OrthCompound is an expression made up of two or more OrthRoots.</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#ComplexOrthWord"/>
	</owl:Class>
	<owl:Class rdf:ID="OrthPhrase">
		<rdfs:label xml:lang="en">OrthPhrase</rdfs:label>
		<rdfs:comment>An OrthPhrase realizes a PhraseUnit.</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#OrthographicExpression"/>
	</owl:Class>
	<owl:Class rdf:ID="Transcription">
		<rdfs:label xml:lang="en">Transcription</rdfs:label>
		<rdfs:comment>A Transcription is something that represents some other entity observed by a transcriber. Therefore, it is an interpretation of an original source. For example, this is usually the primary data in interlinear glossed text. The key difference between a transcription and an orthographic expression is that a transcription involves two entities, a transcriber and a source (speaking event, audio file, video file, some other orthographic expression). </rdfs:comment>
		<rdfs:subClassOf rdf:resource="#SymbolicString"/>
	</owl:Class>
	<owl:Class rdf:ID="PhoneticTranscription">
		<rdfs:label xml:lang="en">PhoneticTranscription</rdfs:label>
		<rdfs:comment>A PhoneticTranscription is composed of characters that correspond to phones of a language.</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#Transcription"/>
	</owl:Class>
	<owl:Class rdf:ID="PhonemicTranscription">
		<rdfs:label xml:lang="en">PhonemicTranscription</rdfs:label>
		<rdfs:comment>A PhonemicTranscription is composed of characters that correspond to phonemes of a language.</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#Transcription"/>
	</owl:Class>
	<owl:Class rdf:ID="UnderlyingFormTranscription">
		<rdfs:label xml:lang="en">UnderlyingFormTranscription</rdfs:label>
		<rdfs:comment>An UnderlyingFormTranscription is composed of SymbolicStrings which correspond to the underlying form of the LinguisticUnits of the language.</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#Transcription"/>
	</owl:Class>
	<owl:Class rdf:ID="OrthographicTranscription">
		<rdfs:label xml:lang="en">OrthographicTranscription</rdfs:label>
		<rdfs:comment>An OrthographicTranscription is composed in the native orthogrphy, as when a an English speaking transcriber transcribes an English conversation.</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#Transcription"/>
	</owl:Class>
	<owl:Class rdf:ID="Transliteration">
		<rdfs:label xml:lang="en">Transliteration</rdfs:label>
		<rdfs:comment>A Transliteration is a representation of some native orthography by some other system.</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#Transcription"/>
	</owl:Class>
	<owl:Class rdf:ID="Term">
		<rdfs:label xml:lang="en">Term</rdfs:label>
		<rdfs:comment>This class includes includes any expression that is not conventially a part of a written language, but is used to name various features, values, and other linguistic constructs. Terms are used in interlinear text, often on the second line, to annotate or 'gloss' transcriptions.</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#SymbolicString"/>
		<rdfs:subClassOf>
			<owl:Restriction>
				<owl:onProperty rdf:resource="#names"/>
				<owl:minCardinality rdf:datatype="&xsd;nonNegativeInteger">1</owl:minCardinality>
			</owl:Restriction>
		</rdfs:subClassOf>
	</owl:Class>
	<!-->
	***************************************************************
	*Begin morphosyntactic units
	***************************************************************
	</-->
	<owl:Class rdf:ID="LinguisticUnit">
		<rdfs:label xml:lang="en">LinguisticUnit</rdfs:label>
		<rdfs:comment>The class of entities is meant to be a container for mental linguistic units of all kinds, including discourse, morphosyntactic, phonological and semantic.</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#Abstract"/>
	</owl:Class>
	<owl:Class rdf:ID="MorphoSyntacticUnit">
		<rdfs:label xml:lang="en">MorphoSyntacticUnit</rdfs:label>
		<rdfs:comment>The class of entities which may be construed as the elements of a language. Such units are meant to serve as ontological containers for mental objects or representations. In some theories, these may correspond to the notion of a morphemes and constructions. In a feature system, these elements carry MorphoSyntacticFeatures.</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#LinguisticUnit"/>
	</owl:Class>
	<owl:Class rdf:ID="SublexicalUnit">
		<rdfs:label xml:lang="en">SublexicalUnit</rdfs:label>
		<rdfs:comment>SublexicalUnit is the class of morphosyntactic unit which may not be expressed alone and, hence, are bound to other morphosyntactic units.</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#MorphoSyntacticUnit"/>
	</owl:Class>
	<owl:Class rdf:ID="InflectionalUnit">
		<rdfs:label xml:lang="en">InflectionalUnit</rdfs:label>
		<rdfs:comment>InflectionalUnit is the class of sublexical unit whose members designate such grammatical categories as tense, aspect, mood etc. The various forms of an InflectionalUnit plus the stem forms a grammatical paradigm and express a grammatical contrast that is obligatory for its stem's part of speech in some given grammatical context. An InflectionalUnit does not alter the partOfSpeech feature of the Root or Stem it attaches to. It is typically located farther from its Root than a derivational unit and  produces a predictable, nonidiosyncratic change of meaning (Crystal 1980:184; Hartmann and Stork 1972:112; Mish et al. 1990:620; Bybee 1985:2, 99).</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#SublexicalUnit"/>
	</owl:Class>
	<owl:Class rdf:ID="DerivationalUnit">
		<rdfs:label xml:lang="en">DerivationalUnit</rdfs:label>
		<rdfs:comment>DerivationalUnit is the class of sublexical units whose members function to derive a new lexical unit from an existing one, by systematically changing the meaning and possibly altering the partOfSpeech feature of the Root or Stem it attaches to (Hartmann and Stork 1972:62; Crystal 1985:89; Mish et al. 1990:342; Bybee 1985:81-82, 99).</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#SublexicalUnit"/>
	</owl:Class>
	<owl:Class rdf:ID="Clitic">
		<rdfs:label xml:lang="en">Clitic</rdfs:label>
		<rdfs:comment>Clitic is the class of units which members exhibit syntactic characteristics of a lexical unit, but show evidence of being morphologically bound to another lexical unit, the host, by being unstressed or subject to word-level phonological rules (Crystal 1980:64; Hartmann and Stork 1972:38; Anderson 1985:158; Klavans 1982: xi-xiv, 74-76,83,93-95,100-101; Zwicky 1977:5).</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#SublexicalUnit"/>
	</owl:Class>
	<owl:Class rdf:ID="Enclitic">
		<rdfs:label xml:lang="en">Enclitic</rdfs:label>
		<rdfs:comment> An enclitic is a clitic that is phonologically joined at the end of a preceding lexical unit to form a single phonological unit (Crystal 1980:64; Pei and Gaynor 1954:65; Mish et al. 1990:409).</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#Clitic"/>
	</owl:Class>
	<owl:Class rdf:ID="Proclitic">
		<rdfs:label xml:lang="en">Proclitic</rdfs:label>
		<rdfs:comment>A proclitic is a clitic that precedes the lexical unit to which it is phonologically joined (Crystal 1980:64; Hartmann and Stork 1972:185; Pei and Gaynor 1954:176; Mish et al. 1990:938).</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#Clitic"/>
	</owl:Class>
	<owl:Class rdf:ID="BoundRoot">
		<rdfs:label xml:lang="en">BoundRoot</rdfs:label>
		<rdfs:comment>BoundRoot is the class of bound units whose members are common to a set of derived or  inflected units, if any, when all  bound units are removed. They are not further analyzable into meaningful elements, being morphologically simple. Also, they designate the principle portion of meaning of the unit to which it belongs (Crystal 1985:268; Hartmann and Stork 1972:199; Pei and Gaynor 1954:187-188; Mish et al. 1990:1023; Matthews 1991:64).</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#SublexicalUnit"/>
	</owl:Class>
	<owl:Class rdf:ID="BoundStem">
		<rdfs:label xml:lang="en">BoundStem</rdfs:label>
		<rdfs:comment>BoundStem is the class of units whose members are decomposable into a root or roots and a derivational unit, and are only expressed by bound forms in the language (Crystal 1985:287; Mish et al. 1990:1154).</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#SublexicalUnit"/>
	</owl:Class>
	<owl:Class rdf:ID="LexicalUnit">
		<rdfs:label xml:lang="en">LexicalUnit</rdfs:label>
		<rdfs:label xml:lang="en"/>
		<rdfs:comment>LexicalUnit is the class of morphosyntactic units which are expressed as individual units, or words, in a language. They are constituents at the Phrase level and above. They are sometimes identifiable according to such criteria as: (1) they are the minimal possible units in a reply; (2) their phonological expressions have features such as a regular stress pattern, and phonological changes conditioned by or blocked at Word boundaries; (3) they are the largest units resistant to insertion of new constituents within their boundaries; or (4) they are the smallest constituents that can be moved within a Sentence without making the Sentence ungrammatical (Hartmann and Stork 1972: 256; Crystal 1980: 168, 383, 384; Cruse 1986: 3536; Mish et al. 1990: 1358; Pike and Pike 1982: 462).
</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#MorphoSyntacticUnit"/>
	</owl:Class>
	<owl:Class rdf:ID="FreeRoot">
		<rdfs:label xml:lang="en">FreeRoot</rdfs:label>
		<rdfs:comment>FreeRoot is the class of free units whose members are common to a set of derived or  inflected units, if any, when all  bound units are removed. They are not further analyzable into meaningful elements, being morphologically simple. Also, they designate the principle portion of meaning of the unit to which it belongs (Crystal 1985:268; Hartmann and Stork 1972:199; Pei and Gaynor 1954:187-188; Mish et al. 1990:1023; Matthews 1991:64).</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#LexicalUnit"/>
	</owl:Class>
	<owl:Class rdf:ID="ComplexLexicalUnit">
		<rdfs:label xml:lang="en">ComplexLexicalUnit</rdfs:label>
		<rdfs:comment>ComplexLexicalUnit</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#LexicalUnit"/>
	</owl:Class>
	<owl:Class rdf:ID="FreeStem">
		<rdfs:label xml:lang="en">FreeStem</rdfs:label>
		<rdfs:comment>FreeStem is the class of units whose members are decomposable into a root or roots and a derivational unit. They are expressed by the free forms of the language (Crystal 1985:287; Mish et al. 1990:1154).</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#ComplexLexicalUnit"/>
	</owl:Class>
	<owl:Class rdf:ID="Compound">
		<rdfs:label xml:lang="en">Compound</rdfs:label>
		<rdfs:comment>Compound</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#ComplexLexicalUnit"/>
	</owl:Class>
	<!-->
	***************************************************************
	*Begin syntactic units (under construction)
	***************************************************************
	</-->
	<owl:Class rdf:ID="PhraseUnit">
		<rdfs:label xml:lang="en">PhraseUnit</rdfs:label>
		<rdfs:comment>PhraseUnit</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#MorphoSyntacticUnit"/>
	</owl:Class>
	<owl:Class rdf:ID="Clause">
		<rdfs:label xml:lang="en">Clause</rdfs:label>
		<rdfs:comment>A clause is a minimal unit including a predicate, all arguments of the predicate, and all modifiers of the predicate and the arguments.</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#PhraseUnit"/>
	</owl:Class>
	<owl:Class rdf:ID="MainClause">
		<rdfs:label xml:lang="en">MainClause</rdfs:label>
		<rdfs:comment>A main clause is an independent clause that can stand on its own as a sentence.  If a sentence contains any embedded clauses, the main clause is understood as the matrix plus the embedded clauses. In the sentence 'John thinks that Mary is sick', 'John thinks that Mary is sick' is the main clause (Crystal 2001:  231).</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#Clause"/>
	</owl:Class>
	<owl:Class rdf:ID="SubordinateClause">
		<rdfs:label xml:lang="en">SubordinateClause</rdfs:label>
		<rdfs:comment>A subordinate clause is a dependent clause that cannot stand on its own as a sentence.  A matrix clause combined with a subordinate clause form a clause. In the sentence 'John thinks that Mary is sick', 'Mary is sick' is the subordinate clause.</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#Clause"/>
	</owl:Class>
	
	<!-->**************************************************************
			*Begin Feature System
			**************************************************************
	</-->
	<owl:Class rdf:ID="FeatureSystem">
		<rdfs:label xml:lang="en">FeatureSystem</rdfs:label>
		<rdfs:comment>FeatureSystem is the class of grammatical systems which uses features and values to represent grammatical information. It can be assumed that only one feature system exists per language data project. A FeatureSystem consists of a set of FeatureValueAssociations, which is a set of features and their allowable values, and a set of FeatureConstraints (Maxwell, Simons, and Hayashi 2001).</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#List"/>
	</owl:Class>
	<!--FeatureSystem rdf:ID="defaultFeatureSystem">
		this will be read by FIELD
</FeatureSystem-->
	<owl:Class rdf:ID="FeatureValueAssociation">
		<rdfs:label xml:lang="en">FeatureValueAssociation</rdfs:label>
		<rdfs:comment>FeatureValueAssociation is the class of all lists, duples, which contain as the first member a Feature and as the second a set of FeatureValues.</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#List"/>
	</owl:Class>
	<owl:Class rdf:ID="FeatureConstraint">
		<rdfs:label xml:lang="en">FeatureConstraint</rdfs:label>
		<rdfs:comment>FeatureConstraint is the class of all lists, duples, which contain as the first member a partOfSpeechValue and, as its second, a set of Features. This essentially gives part of speech a priviledged status in a FeatureSystem. That is, the part of speech determines which Features may be associated with a particular linguistic unit.</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#List"/>
	</owl:Class>
	<owl:Class rdf:ID="FeatureSpecification">
		<rdfs:label xml:lang="en">FeatureSpecification</rdfs:label>
		<rdfs:comment>A FeatureSpecification is an ordered list, a duple, whose first element must be an instance of Feature and whose second element is either an instance of FeatureValue or FeatureStructure (Maxwell, Simons, and Hayashi 2001).</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#List"/>
	</owl:Class>
	<owl:Class rdf:ID="ClosedSpecification">
		<rdfs:label xml:lang="en">ClosedSpecification</rdfs:label>
		<rdfs:comment>ClosedSpecification is a kind of FeatureSpecification whose first element must be an instance of Feature and whose second element must be an instance of FeatureValue (Maxwell, Simons, and Hayashi 2001).</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#FeatureSpecification"/>
	</owl:Class>
	<owl:Class rdf:ID="ComplexSpecification">
		<rdfs:label xml:lang="en">ComplexSpecification</rdfs:label>
		<rdfs:comment>ComplexSpecification is a kind of FeatureSpecification whose first element must be an instance of Feature and whose second element must be an instance of FeatureStructure. This class gives a feature system its recursive properites (Maxwell, Simons, and Hayashi 2001).</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#FeatureSpecification"/>
	</owl:Class>
	<owl:Class rdf:ID="FeatureStructure">
		<rdfs:label xml:lang="en">FeatureStructure</rdfs:label>
		<rdfs:comment>A FeatureStructure is a set of zero or more FeatureSpecifications. A FeatureStructure is a kind of information structure, a container or data structure, expressly to group qualities or features of some object. In a grammatical feature system, a FeatureStructure holds the grammatical information associated with some linguistic unit. In a typed feature system, a FeatureStructure has an associated type, usually a PartOfSpeechValue. (Shieber 1986; Maxwell, Simons, and Hayashi 2001).</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#Set"/>
	</owl:Class>
	<!-->begin feature</-->
	<owl:Class rdf:ID="Feature">
		<rdfs:label xml:lang="en">Feature</rdfs:label>
		<rdfs:comment>Feature, also called a quality or a feature name, is the class of attributes that may be associated with entities. Features have as their values instances of FeatureValue. That is, specific features have specific values associated with them, e.g., the feature 'tense' has 'past', 'present', ..., 'future' as values. In the broader domain, the class of Feature can be thought of as the set of qualities associated with some object in general, e.g., color, size, shape, etc. (Shieber 1986: 12; Gärdenfors 2000; Masolo et al. 2002).</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#InternalAttribute"/>
	</owl:Class>
	<owl:Class rdf:ID="ClosedFeature">
		<rdfs:label xml:lang="en">ClosedFeature</rdfs:label>
		<rdfs:comment>ClosedFeature is the set of features with a simple value, e.g., the feature 'tense' which may have the feature 'past' (Maxwell, Simons and Hayashi 2001).</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#Feature"/>
	</owl:Class>
	<owl:Class rdf:ID="ComplexFeature">
		<rdfs:label xml:lang="en">ComplexFeature</rdfs:label>
		<rdfs:comment>ComplexFeature is the set of features which have complex values, that is, which have a FeatureSpecification as its value (Maxwell, Simons and Hayashi 2001).</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#Feature"/>
	</owl:Class>
	<owl:Class rdf:ID="ClosedMorphoSyntacticFeature">
		<rdfs:label xml:lang="en">ClosedMorphoSyntacticFeature</rdfs:label>
		<rdfs:comment>ClosedMorphoSyntacticFeature identifies the particular grammatical category to which a simple FeatureValue is assigned. It is the first member of a FeatureSpecification. Any grammatical category, such as 'tense' or 'aspect', can be represented as a ClosedMorphoSyntacticFeature in a given language. A set of Features forms an integral part of a language's FeatureSystem.  (Maxwell, Simons and Hayashi 2001).</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#ClosedFeature"/>
	</owl:Class>
	<owl:Class rdf:ID="ComplexMorphoSyntacticFeature">
		<rdfs:label xml:lang="en">ComplexMorphoSyntacticFeature</rdfs:label>
		<rdfs:comment>ComplexMorphoSyntacticFeature identifies the particular grammatical category to which a FeatureSpecification is assigned. This class is used to assign multiple values to a single feature, e.g., 'agreement' (Maxwell, Simons and Hayashi 2001).</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#ClosedFeature"/>
	</owl:Class>
	<!-->begin feature instances</-->
	<ClosedMorphoSyntacticFeature rdf:ID="tense">
		<rdfs:label xml:lang="en">tense</rdfs:label>
		<rdfs:comment>Tense is the grammatical encoding of an event's location in time. It is typically marked on the verb and deictically refers to the time of the event or state denoted by the verb in relation to some other temporal reference point (Comrie 1985: 9; Crystal 1987: 384).</rdfs:comment>
	</ClosedMorphoSyntacticFeature>
	<ClosedMorphoSyntacticFeature rdf:ID="aspect">
		<rdfs:label xml:lang="en">aspect</rdfs:label>
		<rdfs:comment>Aspect is the grammatical encoding of various characteristics of the event referred to in an utterance. Aspect does not form a semantically contiguous class (Comrie 1976; Bybee 1985; Sasse 2002).</rdfs:comment>
	</ClosedMorphoSyntacticFeature>
	<ClosedMorphoSyntacticFeature rdf:ID="modality">
		<rdfs:label xml:lang="en">modality</rdfs:label>
		<rdfs:comment>Modality is the grammatical encoding of the speaker's attitudes and opinions about the expressed proposition. Modality is concerned with the encoding of the truth status of the expressed proposition as well as the propositional attitudes such as fears, wants and desires. Evidentiality is also closely related and is often part of the formal modality system of a language. A distinction is often made between modal and mood systems in the grammar. However, here they are conflated as 'modality' (Bybee, Perkins, and Pagliuca 1994: 176; Palmer 2001: 1).</rdfs:comment>
	</ClosedMorphoSyntacticFeature>
	<ClosedMorphoSyntacticFeature rdf:ID="number">
		<rdfs:label xml:lang="en">number</rdfs:label>
		<rdfs:comment>Number is the grammatical encoding of cardinality, often found on nouns, pronouns, and verbs. Number expresses count distinctions, such as 'one' or 'more than one'. The count distinctions typically, but not always, correspond to the actual count of the referents of the marked noun or pronoun (Crystal 1980: 245; Hartmann and Stork 1972: 155; Mish et al. 1990: 811).</rdfs:comment>
	</ClosedMorphoSyntacticFeature>
	<ClosedMorphoSyntacticFeature rdf:ID="person">
		<rdfs:label xml:lang="en">person</rdfs:label>
		<rdfs:comment>Person is the grammatical encoding of the number and nature of the participants in a situation. Usually a three-way contrast is found: first, second, and third person. Other formal distinctions in languages include: inclusive/exlusive, honorific/intimate, and male/female (Crystal 1997: 285).</rdfs:comment>
	</ClosedMorphoSyntacticFeature>
	<ClosedMorphoSyntacticFeature rdf:ID="case">
		<rdfs:label xml:lang="en">case</rdfs:label>
		<rdfs:comment>Case is a grammatical encoding of the relationship (syntactic or semantic) a noun bears to some other element in the sentence, such as a verb, other noun, pronoun, or adposition(Pei and Gaynor 1954: 35; Crystal 1980: 5354; Anderson 1985: 179180; Andrews 1985: 7172; Mish et al. 1990: 211; Kuno 1973: 45; Blake 2001).</rdfs:comment>
	</ClosedMorphoSyntacticFeature>
	<ClosedMorphoSyntacticFeature rdf:ID="partOfSpeech">
		<rdfs:label xml:lang="en">partOfSpeech</rdfs:label>
		<rdfs:comment>partOfSpeech also known as 'grammatical category' or 'lexical class', is the grammatical encoding of a lexical unit's syntactic class. While a particular theory may not utilize the notion part of speech, it is useful as part of a FeatureSystem. The set of part of speech values for a particular language can be described based on how words behave in the syntax (Payne 1997: 33; Maxwell, Simons, and Hayashi 2001).</rdfs:comment>
	</ClosedMorphoSyntacticFeature>
	<ComplexMorphoSyntacticFeature rdf:ID="agreement">
		<rdfs:label xml:lang="en">agreement</rdfs:label>
		<rdfs:comment>Agreement marks a morphosyntactic relation between two constituents based on one or more grammatical categories.</rdfs:comment>
	</ComplexMorphoSyntacticFeature>
	<!-->begin feature values </-->
	<owl:Class rdf:ID="FeatureValue">
		<rdfs:label xml:lang="en">FeatureValue</rdfs:label>
		<rdfs:comment>FeatureValue is the class of values that may be associated with instances of Feature. That is, specific features have specific feature values associated with them, e.g., the feature 'tense' has 'past', 'present', ..., 'future' as values. In the broader domain, the class of FeatureValue can be thought of as the set of qualia associated with some feature in general, a point in cognitive space. E.g., red is a quale in color space (Shieber 1986: 12; Maxwell, Simons, and Hayashi 2001; Gärdenfors 2000; Masolo et al. 2002).</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#Abstract"/>
	</owl:Class>
	<owl:Class rdf:ID="MorphoSyntacticFeatureValue">
		<rdfs:label xml:lang="en">MorphoSyntacticFeatureValue</rdfs:label>
		<rdfs:comment>MorphoSyntacticFeatureValue is the class of values that may be associated with instances of MorphoSyntacticFeature. In a FeatureSystem, these dictate the formal properties of the grammar and may or may not be true semantically. A set of FeatureValues forms an integral part of a language's FeatureSystem (Pollard and Sag 1994; Maxwell, Simons, and Hayashi 2001).</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#FeatureValue"/>
	</owl:Class>
	<!-->**************************************************************
			*Begin Tense
			**************************************************************
	</-->
	<owl:Class rdf:ID="TenseValue">
		<rdfs:label xml:lang="en">TenseValue</rdfs:label>
		<rdfs:comment>TenseValue is the class of values that may be associated with the feature instance 'tense'. TenseValue is the class of all tense types found in language.</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#MorphoSyntacticFeatureValue"/>
	</owl:Class>
	<owl:Class rdf:ID="AbsoluteTense">
		<rdfs:label xml:lang="en">AbsoluteTense</rdfs:label>
		<rdfs:comment>AbsoluteTenseValue is the set of all values associated with the grammatical encoding of an event's location in time where the moment of utterance is the deictic center (Comrie 1985: 36).</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#TenseValue"/>
	</owl:Class>
	<owl:Class rdf:ID="AbsolutePastTense">
		<rdfs:label xml:lang="en">AbsolutePastTense</rdfs:label>
		<rdfs:comment>AbsolutePastTense locates the situation in question prior to the present moment (Comrie 1985: 41).</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#AbsoluteTense"/>
	</owl:Class>
	<AbsolutePastTense rdf:ID="SimplePastTense">
		<rdfs:label xml:lang="en">SimplePastTense</rdfs:label>
		<rdfs:comment>SimplePastTense is a very generic AbsolutePastTense which locates the situation in question prior to the present moment, with no specification on the distance in time (Comrie 1985).</rdfs:comment>
	</AbsolutePastTense>
	<AbsolutePastTense rdf:ID="RecentPastTense">
		<rdfs:label xml:lang="en">RecentPastTense</rdfs:label>
		<rdfs:comment>RecentPastTense locates the situation in question prior to the present moment, but by culturally and situationally defined criteria, usually within the span ranging from yesterday to a week or a few months previous (Comrie 1985:87; Dahl 1985:121-122).</rdfs:comment>
	</AbsolutePastTense>
	<AbsolutePastTense rdf:ID="RemotePastTense">
		<rdfs:label xml:lang="en">RemotePastTense</rdfs:label>
		<rdfs:comment>RemotePastTense locates the situation in question prior to the present moment, usually more than a few days ago (Dahl 1985:121; Comrie 1985:88).</rdfs:comment>
	</AbsolutePastTense>
	<AbsolutePastTense rdf:ID="HesternalPastTense">
		<rdfs:label xml:lang="en">HesternalPastTense</rdfs:label>
		<rdfs:comment>HesternalPastTense locates the situation in question somewhere in the span beginning with the period defined culturally as 'yesterday' and extends back through some period that is considered nonremote (Comrie 1985:87-88; Dahl 1985:126).</rdfs:comment>
	</AbsolutePastTense>
	<AbsolutePastTense rdf:ID="HodiernalPastTense">
		<rdfs:label xml:lang="en">HodiernalPastTense</rdfs:label>
		<rdfs:comment>HodiernalPastTense locates the situation in question before the moment of utterance within the span culturally defined as 'today' (Comrie 1985:87; Dahl 1985:125-126)</rdfs:comment>
	</AbsolutePastTense>
	<AbsolutePastTense rdf:ID="ImmediatePastTense">
		<rdfs:label xml:lang="en">ImmediatePastTense</rdfs:label>
		<rdfs:comment>ImmediatePastTense locates the situation in question at a time considered very recent in relation to the moment of utterance (Comrie 1985: 87).</rdfs:comment>
	</AbsolutePastTense>
	<AbsolutePastTense rdf:ID="NonRecentPastTense">
		<rdfs:label xml:lang="en">NonRecentPastTense</rdfs:label>
		<rdfs:comment>NonRecentPastTense locates the situation in question before the range of a contrasting recent past tense. This category must be defined relative to a RecentPastTense.</rdfs:comment>
	</AbsolutePastTense>
	<AbsolutePastTense rdf:ID="NonRemotePastTense">
		<rdfs:label xml:lang="en">NonRemotePastTense</rdfs:label>
		<rdfs:comment>NonRemotePastTense locates the situation in question not more than a few days ago, in contrast to a RemotePastTense. This category must be defined relative to a RemotePastTense.</rdfs:comment>
	</AbsolutePastTense>
	<AbsolutePastTense rdf:ID="PreHesternalPastTense">
		<rdfs:label xml:lang="en">PreHesternalPastTense</rdfs:label>
		<rdfs:comment>PreHesternalPastTense locates the situation in question before that of an opposing hesternal past tense. This category must be defined relative to a HesternalPastTense (Bybee, Perkins, Pagliuca 1994: 98).</rdfs:comment>
	</AbsolutePastTense>
	<AbsolutePastTense rdf:ID="PreHodiernalPastTense">
		<rdfs:label xml:lang="en">PreHodiernalPastTense</rdfs:label>
		<rdfs:comment>PreHodiernalPastTense locates the situation in question before that of a contrasting HodiernalPastTense. This category must be defined relative to a HodiernalPastTense (Bybee, Perkins, Pagliuca 1994: 98).</rdfs:comment>
	</AbsolutePastTense>
	<AbsoluteTense rdf:ID="AbsolutePresentTense">
		<rdfs:label xml:lang="en">AbsolutePresentTense</rdfs:label>
		<rdfs:comment>AbsolutePresentTense locates the situation in question at the present moment, though the situation rarely coincides exactly with the present moment (Comrie 1985: 37). </rdfs:comment>
	</AbsoluteTense>
	<AbsoluteTense rdf:ID="StillTense">
		<rdfs:label xml:lang="en">StillTense</rdfs:label>
		<rdfs:comment> StillTense is similar to AbsolutePresentTense but carries the presupposition that an event or state held before the moment of utterance. In positive declarative clauses, still tense asserts that the event or state holds at the moment of utterance (Comrie 1985: 54).</rdfs:comment>
	</AbsoluteTense>
	<owl:Class rdf:ID="AbsoluteFutureTense">
		<rdfs:label xml:lang="en">AbsoluteFutureTense</rdfs:label>
		<rdfs:comment>AbsoluteFutureTense locates the event in question subsequent to the present moment; it is a prediction of some state of affairs (Comrie 1985: 43-44).</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#AbsoluteTense"/>
	</owl:Class>
	<AbsoluteFutureTense rdf:ID="CloseFutureTense">
		<rdfs:label xml:lang="en">CloseFutureTense</rdfs:label>
		<rdfs:comment>CloseFutureTense, also called 'immediate future', locates the situation in question shortly after the moment of utterance (Dahl 1985:121; Comrie 1985:94; Bybee, Perkins, and Pagliuca 1994: 244-245).</rdfs:comment>
	</AbsoluteFutureTense>
	<AbsoluteFutureTense rdf:ID="HodiernalFutureTense">
		<rdfs:label xml:lang="en">HodiernalFutureTense</rdfs:label>
		<rdfs:comment>HodiernalFutureTense locates the situation in question after the moment of utterance within the span culturally defined as 'today' (Comrie 1985: 86; Bybee, Perkins, and Pagliuca 1994: 247).</rdfs:comment>
	</AbsoluteFutureTense>
	<AbsoluteFutureTense rdf:ID="PostHodiernalFutureTense">
		<rdfs:label xml:lang="en">PostHodiernalFutureTense</rdfs:label>
		<rdfs:comment>PostHodiernalFutureTense locates the situation in question after the span that is culturally defined as 'today' (Bybee, Perkins, and Pagliuca 1994: 247).</rdfs:comment>
	</AbsoluteFutureTense>
	<AbsoluteFutureTense rdf:ID="RemoteFutureTense">
		<rdfs:label xml:lang="en">RemoteFutureTense</rdfs:label>
		<rdfs:comment>RemoteFutureTense locates the situation in question at a time that is considered relatively distant. It is characteristically after the span of time culturally defined as 'tomorrow' (Dahl 1985:121; Comrie 1985:94).</rdfs:comment>
	</AbsoluteFutureTense>
	<AbsoluteTense rdf:ID="NonFutureTense">
		<rdfs:label xml:lang="en">NonFutureTense</rdfs:label>
		<rdfs:comment>NonFutureTense locates the situation in question at or before the moment of utterance, and contrasts with a FutureTense (Comrie 1985: 49).</rdfs:comment>
	</AbsoluteTense>
	<AbsoluteTense rdf:ID="NonPastTense">
		<rdfs:label xml:lang="en">NonPastTense</rdfs:label>
		<rdfs:comment>NonPastTense locates the situation in question at or after the moment of utterance, and contrasts with a past tense (Comrie 1985:48-49).</rdfs:comment>
	</AbsoluteTense>
	<owl:Class rdf:ID="RelativeTense">
		<rdfs:label xml:lang="en">RelativeTense</rdfs:label>
		<rdfs:comment>RelativeTense locates the situation in question in relation to a contextually determined temporal reference point, regardless of the latter's temporal relation to the moment of utterance (Comrie 1985: 56).</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#TenseValue"/>
	</owl:Class>
	<RelativeTense rdf:ID="RelativePastTense">
		<rdfs:label xml:lang="en">RelativePastTense</rdfs:label>
		<rdfs:comment>RelativePastTense locates the situation in question before that of a contextually determined temporal reference point (Comrie 1985: 104).</rdfs:comment>
	</RelativeTense>
	<RelativeTense rdf:ID="RelativePresentTense">
		<rdfs:label xml:lang="en">RelativePresentTense</rdfs:label>
		<rdfs:comment>RelativePresentTense locates the situation in question simultaneously with some contextually determined temporal reference point.</rdfs:comment>
	</RelativeTense>
	<RelativeTense rdf:ID="RelativeFutureTense">
		<rdfs:label xml:lang="en">RelativeFutureTense</rdfs:label>
		<rdfs:comment>RelativeFutureTense locates the situation in question after a contextually determined temporal reference point, regardless of the latter's relation to the moment of utterance.</rdfs:comment>
	</RelativeTense>
	<RelativeTense rdf:ID="RelativeNonFutureTense">
		<rdfs:label xml:lang="en">RelativeNonFutureTense</rdfs:label>
		<rdfs:comment>RelativeNonFutureTense locates the situation in question simultaneous to, or before, a contextually determined temporal reference point, regardless of the latter's relation to the moment of utterance.</rdfs:comment>
	</RelativeTense>
	<RelativeTense rdf:ID="RelativeNonPastTense">
		<rdfs:label xml:lang="en">RelativeNonPastTense</rdfs:label>
		<rdfs:comment> RelativeNonPastTense locates the situation in question simultaneous to, or after, a contextually determined temporal reference point, regardless of the latter's relation to the moment of utterance.</rdfs:comment>
	</RelativeTense>
	<owl:Class rdf:ID="AbsoluteRelativeTense">
		<rdfs:label xml:lang="en">AbsoluteRelativeTense</rdfs:label>
		<rdfs:comment>AbsoluteRelativeTense locates the event in question in relation to a temporal reference point that, in turn, is referred to in relation to the moment of utterance; the reference point and the moment of utterance are not identical (Comrie 1985: 64-65).</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#TenseValue"/>
	</owl:Class>
	<AbsoluteRelativeTense rdf:ID="FuturePerfectTense">
		<rdfs:label xml:lang="en">FuturePerfectTense</rdfs:label>
		<rdfs:comment>FuturePerfectTense locates the situation in question before a contextually determined temporal reference point that must be located in the future relative to the moment of utterance (Comrie 1985:69-71).</rdfs:comment>
	</AbsoluteRelativeTense>
	<AbsoluteRelativeTense rdf:ID="FutureInFutureTense">
		<rdfs:label xml:lang="en">FutureInFutureTense</rdfs:label>
		<rdfs:comment>FutureInFutureTense locates the situation in question in the future, relative to a temporal reference point that itself is located in the future relative to the moment of utterance.</rdfs:comment>
	</AbsoluteRelativeTense>
	<AbsoluteRelativeTense rdf:ID="FutureInPastTense">
		<rdfs:label xml:lang="en">FutureInPastTense</rdfs:label>
		<rdfs:comment>FutureInPastTense locates the situation in question in the future, relative to a contextually determined temporal reference point that itself must be located in the past relative to the moment of utterance.</rdfs:comment>
	</AbsoluteRelativeTense>
	<!-->**************************************************************
			*Begin Aspect
			**************************************************************
	</-->
	<owl:Class rdf:ID="AspectValue">
		<rdfs:label xml:lang="en">AspectValue</rdfs:label>
		<rdfs:comment>AspectValue is the class of values that may be associated with the feature instance 'aspect'. AspectValue is the class of all apsect types found in language. Aspect is the grammatical encoding of various characteristics of the event referred to in an utterance. Aspect does not form a semantically contiguous class (Comrie 1976; Bybee 1985; Sasse 2002).</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#MorphoSyntacticFeatureValue"/>
	</owl:Class>
	<owl:Class rdf:ID="PhaseAspect">
		<rdfs:label xml:lang="en">PhaseAspect</rdfs:label>
		<rdfs:comment xml:lang="en">PhaseAspect encodes some portion of the event, the initial, final or core part (Bickel 1997: 116; Sasse 2002).</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#AspectValue"/>
	</owl:Class>
	<PhaseAspect rdf:ID="InceptiveAspect">
		<rdfs:label xml:lang="en">InceptiveAspect</rdfs:label>
		<rdfs:comment xml:lang="en">InceptiveAspect, also called the ingressive, encodes the beginning portion of some event (Bybee 1985: 147, 149; Payne 1997: 240).</rdfs:comment>
	</PhaseAspect>
	<PhaseAspect rdf:ID="CompletiveAspect">
		<rdfs:label xml:lang="en">CompletiveAspect</rdfs:label>
		<rdfs:comment xml:lang="en">CompletiveAspect, also called the egressive, encodes the end portion of some event. In order to be a completive, the case in question should be clearly differentiated in the grammar from an ordinary perfective which also implies that the event is completed (Bybee, Perkins, and Pagliuca 1994: 54; Payne 1997: 240; Dahl 1999: 33).</rdfs:comment>
	</PhaseAspect>
	<owl:Class rdf:ID="ViewPointAspect">
		<rdfs:label xml:lang="en">ViewPointAspect</rdfs:label>
		<rdfs:comment xml:lang="en">ViewPointAspect is a deictic category that encodes the particilar way an event is represented, either as from within the event itself or from outside the event (Comrie 1976: 16-40; Givón 2001: 289).</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#AspectValue"/>
	</owl:Class>
	<ViewPointAspect rdf:ID="PerfectiveAspect">
		<rdfs:label xml:lang="en">PerfectiveAspect</rdfs:label>
		<rdfs:comment xml:lang="en">PerfectiveAspect, sometimes called the aorists, encodes the totality of some event, that is, the event viewed from outside, in its entirety as a whole. Because perfectives encode the entire event, the event is necessarily complete. A perfective may be used to encode a several events when they are to be viewed as a whole (Comrie 1976: 12, 18; Payne 1997: 239; Dahl 1999: 33)</rdfs:comment>
	</ViewPointAspect>
	<!-->Note:  PerfectiveAspect might be viewed as a subclass of both PhaseAspect and ViewPointAspect, or perhaps it should be its own class. Need to decide about this.
	</-->
	<ViewPointAspect rdf:ID="ImperfectiveAspect">
		<rdfs:label xml:lang="en">ImperfectiveAspect</rdfs:label>
		<rdfs:comment xml:lang="en">ImperfectiveAspect encodes the internal temporal structure of an event from within. It indicates that the event is a process without emphasizing its end points, although there may be the entailment that the event has a starting/end point (Comrie 1976: 24; Dahl 1999: 33).</rdfs:comment>
	</ViewPointAspect>
	<owl:Class rdf:ID="QuantitativeAspect">
		<rdfs:label xml:lang="en">QuantitativeAspect</rdfs:label>
		<rdfs:comment xml:lang="en">QuantitativeAspect refers to the cardinality of the event which is represented by the predicate (de Groot 1995; Dahl 1999: 31; Sasse 2002: 227).</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#AspectValue"/>
	</owl:Class>
	<QuantitativeAspect rdf:ID="HabitualAspect">
		<rdfs:label xml:lang="en">HabitualAspect</rdfs:label>
		<rdfs:comment xml:lang="en">HabitualAspect, also called the durative, encodes the situation where an event takes place over an extended period of time. This is, it refers to not just one event but many events of the same type. The occurrence of the events may be protracted indefinitely in time. If the event is a state, then the state is said to hold for some time. If the event is an achievement or an accomplishment, then it may occur again and again. The time interval which is relevant to the habitual is relatively longer than in the case of the iterative (Comrie 1976: 28; Bybee 1985: 142; Payne 1997: 241; Dahl 1999: 32).</rdfs:comment>
	</QuantitativeAspect>
	<QuantitativeAspect rdf:ID="IterativeAspect">
		<rdfs:label xml:lang="en">IterativeAspect</rdfs:label>
		<rdfs:comment xml:lang="en">IterativeAspect, also called repetitives, encodes a number of events of the same type that are repeated on a particular occasion. The time interval which is relevant to the iterative is relatively shorter than in the case of the habitual (Bybee 1985: 150; Bybee, Perkins and Pagliuca 1994: 127).</rdfs:comment>
	</QuantitativeAspect>
	<owl:Class rdf:ID="DynamicityAspect">
		<rdfs:label xml:lang="en">DynamicityAspect</rdfs:label>
		<rdfs:comment xml:lang="en">DynamicityAspect refers to the degree to which an event is expressed as an on going process, i.e., as progressive or not (Bybee, Perkins and Pagliuca 1994: 127-139).</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#AspectValue"/>
	</owl:Class>
	<DynamicityAspect rdf:ID="ProgressiveAspect">
		<rdfs:label xml:lang="en">ProgressiveAspect</rdfs:label>
		<rdfs:comment xml:lang="en">ProgressiveAspect, also called the continuative or the durative, encodes a single event as an ongoing process. Thus, states cannot generally be encoded with the progressive (Comrie 1976: 32-35; Bybee, Perkins and Pagliuca 1994: 127-139; Payne 1997: 240).</rdfs:comment>
	</DynamicityAspect>
	<DynamicityAspect rdf:ID="NonProgressiveAspect">
		<rdfs:label xml:lang="en">NonProgressiveAspect</rdfs:label>
		<rdfs:comment xml:lang="en">NonProgressiveAspect is essentially the opposite of ProgressiveAspect; it encodes a single event as a state or non-process. It is a controversial category, though there may be languages in which it contrasts witht he ProgressiveAspect (Comrie 1976: 32-35; Bybee, Perkins and Pagliuca 1994: 137-139).</rdfs:comment>
	</DynamicityAspect>
	<owl:Class rdf:ID="RelevanceAspect">
		<rdfs:label xml:lang="en">RelevanceAspect</rdfs:label>
		<rdfs:comment xml:lang="en">RelevanceAspect encodes the degree to which some event is relevant in relation to some reference time (Givón 2001: 296).</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#AspectValue"/>
	</owl:Class>
	<RelevanceAspect rdf:ID="PerfectAspect">
		<rdfs:label xml:lang="en">PerfectAspect</rdfs:label>
		<rdfs:comment xml:lang="en">PerfectAspect indicates that the event is relevant in relation to some reference time. Thus, it encodes both a temporal and a discourse relation between two time points. It can contrast with the perfective (Comrie 1976: 52-65; Givón 2001: 296).</rdfs:comment>
	</RelevanceAspect>
	<!-->
	I've commented this out because neither Bybee 1985 nor Bybee, Perkins and Pagliuca 1994 found the continuous as distinguished from the progressive. We may find in the future that it is indeed useful.
	
	<owl:Class rdf:ID="ContinuousAspect">
		<rdfs:label xml:lang="en">ContinuousAspect</rdfs:label>
		<rdfs:comment xml:lang="en">ContinuousAspect encodes an event (including states) as ongoing at reference time. The continuous contrasts with the progressive in that states can be continuous. (Comrie 1976: 25; Bybee 1985: 142; Bybee, Perkins, and Pagliuca 1994: 127).</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#"/>	
	</owl:Class>
</-->
	<!-->**************************************************************
			*Begin Modality
			**************************************************************
	</-->
	<owl:Class rdf:ID="ModalityValue">
		<rdfs:label xml:lang="en">ModalityValue</rdfs:label>
		<rdfs:comment>ModalityValue is the class of values that may be associated with the feature instance 'modality'. ModalityValue is the class of all modality types found in language. Modality is the encoding of the speaker's attitudes and opinions about the expressed proposition. Modality is concerned with the encoding of the truth status of the expressed proposition as well as the propositional attitudes such as fears, wants and desires. Evidentiality is also closely related and is often part of the formal mood system of a language. A formal distinction is often made between modal and mood systems in the grammar. However, here they are conflated as Modality (Bybee, Perkins, and Pagliuca 1994: 176; Palmer 2001: 1).</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#MorphoSyntacticFeatureValue"/>
	</owl:Class>
	<!-->
	Special note: Modality values are not organized. Scott will organize Modality values later based on Modality notes. A few values are not defined either.
</-->
	<ModalityValue rdf:ID="Realis">
		<rdfs:label xml:lang="en">Realis</rdfs:label>
		<rdfs:comment xml:lang="en">Realis</rdfs:comment>
	</ModalityValue>
	<ModalityValue rdf:ID="Irrealis">
		<rdfs:label xml:lang="en">Irrealis</rdfs:label>
		<rdfs:comment xml:lang="en">Irrealis</rdfs:comment>
	</ModalityValue>
	<ModalityValue rdf:ID="Indicative">
		<rdfs:label xml:lang="en">Indicative</rdfs:label>
		<rdfs:comment xml:lang="en">Indicative</rdfs:comment>
	</ModalityValue>
	<ModalityValue rdf:ID="Subjunctive">
		<rdfs:label xml:lang="en">Subjunctive</rdfs:label>
		<rdfs:comment xml:lang="en">Subjunctive</rdfs:comment>
	</ModalityValue>
	<ModalityValue rdf:ID="DirectEvidential">
		<rdfs:label xml:lang="en">DirectEvidential</rdfs:label>
		<rdfs:comment xml:lang="en">DirectEvidential, also called sensory, encodes the fact that the speaker came to believe the content of the expression by having direct sensory experience of some situation; this does not include hearing about it from someone else (Palmer 2001: 35-36).</rdfs:comment>
	</ModalityValue>
	<ModalityValue rdf:ID="VisualEvidential">
		<rdfs:label xml:lang="en">VisualEvidential</rdfs:label>
		<rdfs:comment xml:lang="en">VisualEvidential encodes the fact that the speaker came to believe the content of the expression through direct visual experience; they saw it (Palmer 2001: 57).</rdfs:comment>
	</ModalityValue>
	<ModalityValue rdf:ID="NonVisualEvidential">
		<rdfs:label xml:lang="en">NonVisualEvidential</rdfs:label>
		<rdfs:comment xml:lang="en">NonVisualEvidential encodes the fact that the speaker came to believe the content of the expression directly in a way other than through visual experience; they heard it, smelled it, tasted it, ect. (Palmer 2001: 36, 57).</rdfs:comment>
	</ModalityValue>
	<ModalityValue rdf:ID="AuditoryEvidential">
		<rdfs:label xml:lang="en">AuditoryEvidential</rdfs:label>
		<rdfs:comment xml:lang="en">AuditoryEvidential encodes the fact that the speaker came to believe the content of the expression through direct auditory experience; they heard it. This does not include spoken reported accounts, but only direct sensory evdience, such as the situation of 'hearing a tree fall' (Palmer 2001: 38).</rdfs:comment>
	</ModalityValue>
	<!-- I've included these logical possibilities, but they are not attested as separate categories>
	<ModalityValue rdf:ID="OlfactoryEvidential">
		<rdfs:label xml:lang="en">OlfactoryEvidential</rdfs:label>
		<rdfs:comment xml:lang="en">OlfactoryEvidential encodes the fact that the speaker came to believe the content of the expression through direct olfactory experience; they smelled it ().</rdfs:comment>	
	</ModalityValue>

	<ModalityValue rdf:ID="TactileEvidential">
		<rdfs:label xml:lang="en">TactileEvidential</rdfs:label>
		<rdfs:comment xml:lang="en">TactileEvidential encodes the fact that the speaker came to believe the content of the expression through direct tactile experience; they felt it ().</rdfs:comment>	
		</ModalityValue>

	<ModalityValue rdf:ID="GustatoryEvidential">
		<rdfs:label xml:lang="en">GustatoryEvidential</rdfs:label>
		<rdfs:comment xml:lang="en">GustatoryEvidential encodes the fact that the speaker came to believe the content of the expression through direct gustatory experience; they tasted it ().</rdfs:comment>	
		</ModalityValue>
</-->
	<ModalityValue rdf:ID="IndirectEvidential">
		<rdfs:label xml:lang="en">IndirectEvidential</rdfs:label>
		<rdfs:comment xml:lang="en">IndirectEvidential, also called reported, encodes the fact that the speaker came to believe the content of the expression from a source other than by experiencing the situation directly (Palmer 2001: 40).</rdfs:comment>
	</ModalityValue>
	<ModalityValue rdf:ID="SecondHandEvidential">
		<rdfs:label xml:lang="en">SecondHandEvidential</rdfs:label>
		<rdfs:comment xml:lang="en">SecondHandEvidential, also called the quotative, encodes the fact that the speaker came to believe the content of the expression from communicating with someone else (Palmer 2001: 40).</rdfs:comment>
	</ModalityValue>
	<ModalityValue rdf:ID="ThirdHandEvidential">
		<rdfs:label xml:lang="en">ThirdHandEvidential</rdfs:label>
		<rdfs:comment xml:lang="en">ThirdHandEvidential, also called the hearsay, encodes the fact that the speaker came to believe the content of the expression from a source generally considered less reliable than with a SecondHandEvidential (Palmer 2001: 40).</rdfs:comment>
	</ModalityValue>
	<ModalityValue rdf:ID="FolkloreEvidential">
		<rdfs:label xml:lang="en">FolkloreEvidential</rdfs:label>
		<rdfs:comment xml:lang="en">FolkloreEvidential encodes the fact that the speaker came to believe the content of the expression through legend, folklore or some other established tradition (Palmer 2001: 40).</rdfs:comment>
	</ModalityValue>
	<ModalityValue rdf:ID="InferenceEvidential">
		<rdfs:label xml:lang="en">InferenceEvidential</rdfs:label>
		<rdfs:comment xml:lang="en">InferenceEvidential encodes the fact that the speaker came to believe the content of the expression through some kind of internal inference procedure, e.g., deduction, abduction, induction (Palmer 2001: 6-8).</rdfs:comment>
	</ModalityValue>
	<ModalityValue rdf:ID="Assumptive">
		<rdfs:label xml:lang="en">Assumptive</rdfs:label>
		<rdfs:comment xml:lang="en">Assumptive encodes the fact that the speaker came to believe the content of the expression through (possibly) unsound inference procedure. That is, it is at least reasonalbe (Palmer 2001: 6-8).</rdfs:comment>
	</ModalityValue>
	<ModalityValue rdf:ID="Deductive">
		<rdfs:label xml:lang="en">Deductive</rdfs:label>
		<rdfs:comment xml:lang="en">Deductive encodes the fact that the speaker came to believe the content of the expression through sound inference procedure. That is, it is the only possible conclusion (Palmer 2001: 6-8).</rdfs:comment>
	</ModalityValue>
	<ModalityValue rdf:ID="Volitive">
		<rdfs:label xml:lang="en">Volitive</rdfs:label>
		<rdfs:comment xml:lang="en">Volitive encodes that the speaker is willing to perform some action (Palmer 2001: 76).</rdfs:comment>
	</ModalityValue>
	<ModalityValue rdf:ID="Commisive">
		<rdfs:label xml:lang="en">Commisive</rdfs:label>
		<rdfs:comment xml:lang="en">Commisive encodes that the speaker promises or threatens to perform some action (Palmer 2001: 10, 72).</rdfs:comment>
	</ModalityValue>
	<ModalityValue rdf:ID="Optative">
		<rdfs:label xml:lang="en">Optative</rdfs:label>
		<rdfs:comment xml:lang="en">Optative encodes that the speaker wishes or hopes that the expressed proposition be the case (Bybee, Perkins, and Pagliuca 1994: 179; Palmer 2001: 204).</rdfs:comment>
	</ModalityValue>
	<ModalityValue rdf:ID="Timitive">
		<rdfs:label xml:lang="en">Timitive</rdfs:label>
		<rdfs:comment xml:lang="en">Timitive encodes that the speaker fears somethings expressed in the proposition (Palmer 2001: 13, 22).</rdfs:comment>
	</ModalityValue>
	<ModalityValue rdf:ID="Obligative">
		<rdfs:label xml:lang="en">Obligative</rdfs:label>
		<rdfs:comment xml:lang="en">Obligative is a very common modal category and encodes that the subject is required to perform the action expressed by the predicate (Bybee, Perkins, and Pagliuca 1994: 177; Palmer 2001: 71).</rdfs:comment>
	</ModalityValue>
	<ModalityValue rdf:ID="Permissive">
		<rdfs:label xml:lang="en">Permissive</rdfs:label>
		<rdfs:comment xml:lang="en">Permissive encodes that the subject has permission to perform the action expressed by the predicate (Palmer 2001: 10, 71).</rdfs:comment>
	</ModalityValue>
	<!--
	Is  WeakOblig. /'should' a kind of semi-modal or a kind of deontic Obligative?
-->
	<ModalityValue rdf:ID="WeakObligative">
		<rdfs:label xml:lang="en">WeakObligative</rdfs:label>
		<rdfs:comment xml:lang="en">WeakObligative encodes that the subject 'should' perform the action expressed by the predicate (Bybee, Perkins, and Pagliuca 1994: 186-187).</rdfs:comment>
	</ModalityValue>
	<ModalityValue rdf:ID="Categorical">
		<rdfs:label xml:lang="en">Categorical</rdfs:label>
		<rdfs:comment xml:lang="en">Categorical encodes that fact that the speaker knows the expressed proposition to be true (Palmer 2001: 37, 68-69).</rdfs:comment>
	</ModalityValue>
	<ModalityValue rdf:ID="Speculative">
		<rdfs:label xml:lang="en">Speculative</rdfs:label>
		<rdfs:comment xml:lang="en">Speculative encodes the fact that the speaker considers, or 'entertains', the content of the expression. That is, it is in the realm of possibility, though the speaker does not necessarilty believe it (Palmer 2001: 6-8, 25).</rdfs:comment>
	</ModalityValue>
	<ModalityValue rdf:ID="GeneralAbilitive">
		<rdfs:label xml:lang="en">GeneralAbilitive</rdfs:label>
		<rdfs:comment xml:lang="en">GeneralAbilitive is a very frequently occurring modality which encodes that the agent is able to perform some action. The conditions are external to the agent (Bybee, Perkins, and Pagliuca 1994: 177; Palmer 2001: 76)</rdfs:comment>
	</ModalityValue>
	<ModalityValue rdf:ID="MentalAbilitive">
		<rdfs:label xml:lang="en">MentalAbilitive</rdfs:label>
		<rdfs:comment xml:lang="en">MentalAbilitive encodes an internal condition of ability, whereby the agent has the mental capacity to perform some action (Bybee, Perkins, and Pagliuca 1994: 192; Palmer 2001: 77)</rdfs:comment>
	</ModalityValue>
	<ModalityValue rdf:ID="PhysicalAbilitive">
		<rdfs:label xml:lang="en">PhysicalAbilitive</rdfs:label>
		<rdfs:comment xml:lang="en">PhysicalAbilitive encodes an internal condition of ability, whereby the agent has the physical capacity to perform some action (Bybee, Perkins, and Pagliuca 1994: 192; Palmer 2001: 77).</rdfs:comment>
	</ModalityValue>
	<ModalityValue rdf:ID="Dubitative">
		<rdfs:label xml:lang="en">Dubitative</rdfs:label>
		<rdfs:comment>Dubitative encodes a speakers doubt or uncertainty about a proposition (Palmer 2001).</rdfs:comment>
	</ModalityValue>

	
	<!-->
			**************************************************************
			*Begin Number
			**************************************************************
	</-->
	<owl:Class rdf:ID="NumberValue">
		<rdfs:label xml:lang="en">NumberValue</rdfs:label>
		<rdfs:comment>NumberValue is the class of values that may be associated with the feature instance 'number'. NumberValue is the class of all grammatical number types found in language. Number is a grammatical category often found on nouns, pronouns, and verb agreement that expresses count distinctions--such as 'one' or 'more than one'. The count distinctions typically, but not always, correspond to the actual count of the referents of the marked noun or Pronoun (Crystal 1980: 245; Hartmann and Stork 1972: 155; Mish et al. 1990: 811).</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#MorphoSyntacticFeatureValue"/>
	</owl:Class>
	<NumberValue rdf:ID="singular">
		<rdfs:label xml:lang="en">singular</rdfs:label>
		<rdfs:comment>Singular number is number that refers to one member of a designated class (Crystal 1980: 245; Hartmann and Stork 1972: 210).</rdfs:comment>
	</NumberValue>
	<NumberValue rdf:ID="plural">
		<rdfs:label xml:lang="en">plural</rdfs:label>
		<rdfs:comment>Plural number is number that expresses reference to a quantity greater than that expressed by the largest specific number category in a language, such as 'more than one' in English, and 'more than two' in some other languages (Crystal 1980: 245; Hartmann and Stork 1972: 178; Crystal 1987: 428; Mish et al. 1990: 906).</rdfs:comment>
	</NumberValue>
	<NumberValue rdf:ID="dual">
		<rdfs:label xml:lang="en">dual</rdfs:label>
		<rdfs:comment>Dual number is number which refers to two members of a designated class (Crystal 1997: 265).</rdfs:comment>
	</NumberValue>
	<NumberValue rdf:ID="paucal">
		<rdfs:label xml:lang="en">paucal</rdfs:label>
		<rdfs:comment>Paucal number is number which refers to a few members of a designated class (Crystal 1997: 265).</rdfs:comment>
	</NumberValue>
	<NumberValue rdf:ID="trial">
		<rdfs:label xml:lang="en">trial</rdfs:label>
		<rdfs:comment>A trial number is a number that refers to three members of the designated class (Pei and Gaynor 1954: 220; Gove, et al. 1966: 2439).</rdfs:comment>
	</NumberValue>
	<!-->**************************************************************
			*Begin Person
			************************************************************	
			</-->
	<owl:Class rdf:ID="PersonValue">
		<rdfs:label xml:lang="en">PersonValue</rdfs:label>
		<rdfs:comment>PersonValue is the class of values that may be associated with the feature instance 'person'. PersonValue is the class of all grammatical person types found in language. Person indicates the number and nature of the participants in a situation. Usually a three-way contrast is found: first, second, and third person. Other formal distinctions in languages include: inclusive/exlusive, honorific/intimate, and male/female (Crystal 1997: 285).</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#MorphoSyntacticFeatureValue"/>
	</owl:Class>
	<PersonValue rdf:ID="firstPerson">
		<rdfs:label xml:lang="en">FirstPerson</rdfs:label>
		<rdfs:comment>Reference to speaker(s), usually including themselves (Crystal 1997: 285).</rdfs:comment>
	</PersonValue>
	<PersonValue rdf:ID="firstPersonExclusive">
		<rdfs:label xml:lang="en">FirstPersonExclusive</rdfs:label>
		<rdfs:comment>Distinction of the participants referred to, for example, speaker and others, but not hearer. Contrast with the FirstPersonInclusive (Crystal 1997: 285).</rdfs:comment>
	</PersonValue>
	<PersonValue rdf:ID="firstPersonInclusive">
		<rdfs:label xml:lang="en">FirstPersonInclusive </rdfs:label>
		<rdfs:comment>Distinction of the particpants referred to, for example, speaker, hearer and others. Contrast with FirstPersonExclusive (Crystal 1997: 285).</rdfs:comment>
	</PersonValue>
	<PersonValue rdf:ID="secondPerson">
		<rdfs:label xml:lang="en">SecondPerson</rdfs:label>
		<rdfs:comment>Normally used for person the speaker is addressing (Crystal 1997: 285).</rdfs:comment>
	</PersonValue>
	<PersonValue rdf:ID="thirdPerson">
		<rdfs:label xml:lang="en">ThirdPerson</rdfs:label>
		<rdfs:comment>The manner in which other people, things, animals, etc. are referred to (Crystal 1997: 285).</rdfs:comment>
	</PersonValue>
	<!-->**************************************************************
			*Begin Case
			**************************************************************
	</-->
	<owl:Class rdf:ID="CaseValue">
		<rdfs:label xml:lang="en">CaseValue</rdfs:label>
		<rdfs:comment>CaseValue is the class of values that may be associated with the feature instance 'case'. CaseValue is the class of all case types found in language. Case is a system of marking dependent nouns for the type of relationship (syntactic or semantic) they bear to some other element in the sentence, such as a verb, noun, pronoun, or adposition(Pei and Gaynor 1954: 35; Crystal 1980: 5354; Anderson 1985: 179180; Andrews 1985: 7172; Mish et al. 1990: 211; Kuno 1973: 45; Blake 2001).</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#MorphoSyntacticFeatureValue"/>
	</owl:Class>
	<owl:Class rdf:ID="GrammaticalCase">
		<rdfs:label xml:lang="en">GrammaticalCase</rdfs:label>
		<rdfs:comment>Subsumes the Cases that are assigned by the verb. These Cases often correspond to the SemanticRoles in the Sentence.</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#CaseValue"/>
	</owl:Class>
	<GrammaticalCase rdf:ID="NominativeCase">
		<rdfs:label xml:lang="en">NominativeCase</rdfs:label>
		<rdfs:comment>NominativeCase identifies clause subjects in nominative-accusative languages. It is usually the unmarked case. Nouns used in isolation often have this case (Crystal 1980: 242; Pei and Gaynor 1954: 147; Mish et al. 1990: 801; Hartmann and Stork 1972: 224).</rdfs:comment>
	</GrammaticalCase>
	<GrammaticalCase rdf:ID="ErgativeCase">
		<rdfs:label xml:lang="en">ErgativeCase</rdfs:label>
		<rdfs:comment>ErgativeCase in ergative-absolutive languages generally identifies the subject of transitive verbs in the translation equivalents of nominative-accusative Languages such as English (Crystal 1980: 134; Hartmann and Stork 1972: 78; Pei and Gaynor 1954: 67; Andrews and Avery 1985: 138).</rdfs:comment>
	</GrammaticalCase>
	<GrammaticalCase rdf:ID="GenitiveCase">
		<rdfs:label xml:lang="en">GenitiveCase</rdfs:label>
		<rdfs:comment>GenitiveCase is used to mark the noun whose referent is the possessor of the referent of another noun (Crystal 1980: 161; Hartmann and Stork 1972: 9495,180; Pei and Gaynor 1954: 82,172; Anderson 1985: 185; Mish et al. 1990: 511; Fleming 1988: 10).</rdfs:comment>
	</GrammaticalCase>
	<GrammaticalCase rdf:ID="AbsolutiveCase">
		<rdfs:label xml:lang="en">AbsolutiveCase</rdfs:label>
		<rdfs:comment>AbsolutiveCase in ergative-absolutive languages mark referents that would generally be the subjects of intransitive verbs or the objects of transitive verbs in the translational equivalents of nominative-accusative languages (Anderson 1985: 181; Crystal 1985: 1; Andrews and Avery 1985: 138).</rdfs:comment>
	</GrammaticalCase>
	<GrammaticalCase rdf:ID="AccusativeCase">
		<rdfs:label xml:lang="en">AccusativeCase</rdfs:label>
		<rdfs:comment>AccusativeCase in nominative-accusative languages marks certain syntactic functions, usually direct objects (Hartmann and Stork 1972: 3,156; Crystal 1980: 11,246; Andrews and Avery 1985: 75; Anderson; 1985: 181; Mish et al. 1990: 50).</rdfs:comment>
	</GrammaticalCase>
	<GrammaticalCase rdf:ID="DativeCase">
		<rdfs:label xml:lang="en">DativeCase</rdfs:label>
		<rdfs:comment>DativeCase marks 1) Indirect objects (for languages in which they are held to exist) or 2) nouns having the role of recipient (as of things given), beneficiary of an action, or possessor of an item (Crystal 1980: 102; Gove, et al. 1966: 577).</rdfs:comment>
	</GrammaticalCase>
	<GrammaticalCase rdf:ID="InstrumentalCase">
		<rdfs:label xml:lang="en">InstrumentalCase</rdfs:label>
		<rdfs:comment>InstrumentalCase indicates that the referent of the noun it marks is the means of the accomplishment of the action expressed by the clause (Crystal 1980: 187; Hartmann and Stork 1972: 114; Mish et al. 1990: 627).</rdfs:comment>
	</GrammaticalCase>
	<owl:Class rdf:ID="NonGrammaticalCase">
		<rdfs:label xml:lang="en">NonGrammaticalCase</rdfs:label>
		<rdfs:comment>Subsumes the Cases that are assigned by the verb. These Cases often correspond to the SemanticRoles in the Sentence.</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#CaseValue"/>
	</owl:Class>
	<!-->

**********begin NonSpatialCase

</-->
	<owl:Class rdf:ID="NonSpatialCase">
		<rdfs:label xml:lang="en">NonspatialCase </rdfs:label>
		<rdfs:comment>This subsumes cases which are non-grammatical and non-spatial.</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#NonGrammaticalCase"/>
	</owl:Class>
	<NonSpatialCase rdf:ID="CausalCase">
		<rdfs:label xml:lang="en">CausalCase</rdfs:label>
		<rdfs:comment>Used to mark the noun whose referent is the cause of some event, found in Archi (Kibrik 1998: 468).</rdfs:comment>
	</NonSpatialCase>
	<NonSpatialCase rdf:ID="BenefactiveCase">
		<rdfs:label xml:lang="en">BenefactiveCase</rdfs:label>
		<rdfs:comment>BenefactiveCase expresses that the referent of the noun it marks receives the benefit of the situation expressed by the clause (Crystal 1980: 43; Gove, et al. 1966: 203).</rdfs:comment>
	</NonSpatialCase>
	<NonSpatialCase rdf:ID="MalefactiveCase">
		<rdfs:label xml:lang="en">MalefactiveCase</rdfs:label>
		<rdfs:comment>Opposite of BenefactiveCase; used when the marked noun is negatively affected in the clause.</rdfs:comment>
	</NonSpatialCase>
	<NonSpatialCase rdf:ID="VocativeCase">
		<rdfs:label xml:lang="en">VocativeCase</rdfs:label>
		<rdfs:comment>VocativeCase marks a noun whose referent is being addressed (Crystal 1980: 377; Hartmann and Stork 1972: 251; Pei and Gaynor 1954: 228).</rdfs:comment>
	</NonSpatialCase>
	<NonSpatialCase rdf:ID="AversiveCase">
		<rdfs:label xml:lang="en">AversiveCase</rdfs:label>
		<rdfs:comment>Marks the noun whose referent is the object of avoidance; also called the evitative (Blake 1998: 154).</rdfs:comment>
	</NonSpatialCase>
	<NonSpatialCase rdf:ID="AbessiveCase">
		<rdfs:label xml:lang="en">AbessiveCase</rdfs:label>
		<rdfs:comment>AbessiveCase expresses the lack or absence of the referent of the noun it marks. It has the meaning of the English preposition 'without' (Pei and Gaynor 1954: 3,35; Gove, et al. 1966: 3).</rdfs:comment>
	</NonSpatialCase>
	<NonSpatialCase rdf:ID="ProprietiveCase">
		<rdfs:label xml:lang="en">ProprietiveCase</rdfs:label>
		<rdfs:comment>This case expresses the presence of the referent of the noun it marks.  It has the meaning of the English verb 'have' (Blake 1994: 156). </rdfs:comment>
	</NonSpatialCase>
	<NonSpatialCase rdf:ID="ComitativeCase">
		<rdfs:label xml:lang="en">ComitativeCase</rdfs:label>
		<rdfs:comment>ComitativeCase expresses accompaniment. It carries the meaning 'with' or 'accompanied by' (Anderson, Stephen 1985: 186; Pei and Gaynor 1954: 42;Dixon, R. 1972: 12; Gove, et al. 1966: 455).</rdfs:comment>
	</NonSpatialCase>
	<NonSpatialCase rdf:ID="EquativeCase">
		<rdfs:label xml:lang="en">EquativeCase</rdfs:label>
		<rdfs:comment>EquativeCase expresses 'likeness of' or 'identity to' the referent of the noun it marks. It mean: 'as', 'like', and 'in the capacity of'; in some instances, it may have the meaning 'occurs in the manner typical of the referent' (Kibrik 1998: 469).</rdfs:comment>
	</NonSpatialCase>
	<NonSpatialCase rdf:ID="PartitiveCase">
		<rdfs:label xml:lang="en">PartitiveCase</rdfs:label>
		<rdfs:comment>PartitiveCase expresses the partial nature of the referent of the noun it marks, as opposed to expressing the whole unit or class of which the referent is a part. This case may be found in items such as the following: existential clauses, nouns that are accompanied by numerals or units of measure, or predications of material from which something is made. It often has a meaning similar to the English word 'some' (Pei and Gaynor 1954: 161; Richards, Platt, and Weber 1985: 208; Quirk, et al. 1985: 249; Gove, et al. 1966: 1648; Sebeok 1946: 1214).</rdfs:comment>
	</NonSpatialCase>
	<NonSpatialCase rdf:ID="PermutativeCase">
		<rdfs:label xml:lang="en">PermutativeCase</rdfs:label>
		<rdfs:comment>PermutativeCase expresses that the referent of the noun it marks takes part in some event instead of the referent of some other noun; it means roughly ' instead of'; found in Archi (Kibrik 1998: 469).</rdfs:comment>
	</NonSpatialCase>
	<NonSpatialCase rdf:ID="ComparativeCase">
		<rdfs:label xml:lang="en">ComparativeCase</rdfs:label>
		<rdfs:comment>ComparitiveCase expresses that the referent of the noun it marks has some property to a lesser extent than that of the referent of some other noun; found in Archi (Kibrik 1998: 469) and in some Dravidian languages (Blake 1998: 155).</rdfs:comment>
	</NonSpatialCase>
	<NonSpatialCase rdf:ID="PossessorCase">
		<rdfs:label xml:lang="en">PossessorCase</rdfs:label>
		<rdfs:comment>PossessorCase is used to mark the noun whose referent is the possessor of the referent of another noun (Blake 1998: 149).</rdfs:comment>
	</NonSpatialCase>
	<NonSpatialCase rdf:ID="PossessedCase">
		<rdfs:label xml:lang="en">PossessedCase</rdfs:label>
		<rdfs:comment>PossessedCase is used to mark the noun whose referent is possessed by the referent of another noun.</rdfs:comment>
	</NonSpatialCase>
	<NonSpatialCase rdf:ID="AdversativeCase">
		<rdfs:label xml:lang="en">AdversativeCase</rdfs:label>
		<rdfs:comment>AdversativeCase expresses an antithetical circumstance. Adversative meaning can be expressed in several grammatical ways, such as through a conjunction (but), adverbial (however, nevertheless, yet, in spite of that, on the other hand), or preposition (despite, except, apart from, notwithstanding) (Crystal 1997: 11).</rdfs:comment>
	</NonSpatialCase>
	<!-->

************begin SpatialCase

</-->
	<owl:Class rdf:ID="SpatialCase">
		<rdfs:label xml:lang="en">SpatialCase</rdfs:label>
		<rdfs:comment>This subsumes cases that involve literal spatial arrangement, static or dynamic.</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#NonGrammaticalCase"/>
	</owl:Class>
	<owl:Class rdf:ID="PositionalCase">
		<rdfs:label xml:lang="en">PositionalCase</rdfs:label>
		<rdfs:comment>Represents a static spatial relation between two Objects.</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#SpatialCase"/>
	</owl:Class>
	<PositionalCase rdf:ID="EssiveCase">
		<rdfs:label xml:lang="en">EssiveCase</rdfs:label>
		<rdfs:comment>EssiveCase expresses that  the referent of the noun it marks is the location at which another referent exists (Lyons 1968: 299,301; Gove, et al. 1966: 778; Crystal 1985: 112; Blake 1994: 154-5).</rdfs:comment>
	</PositionalCase>
	<PositionalCase rdf:ID="SuperessiveCase">
		<rdfs:label xml:lang="en">SuperessiveCase</rdfs:label>
		<rdfs:comment>SuperessiveCase expresses that  the referent of the noun it marks is the location on which another referent exists. It has the meaning of 'on' or 'upon'. (Pei and Gaynor 1954: 207, Gove, et al. 1966: 2293).</rdfs:comment>
	</PositionalCase>
	<PositionalCase rdf:ID="SubessiveCase">
		<rdfs:label xml:lang="en">SubessiveCase</rdfs:label>
		<rdfs:comment>SubessiveCase expresses that  the referent of the noun it marks is the location under which another referent exists. It has the meaning of 'under' or 'beneath'.</rdfs:comment>
	</PositionalCase>
	<PositionalCase rdf:ID="InessiveCase">
		<rdfs:label xml:lang="en">InessiveCase</rdfs:label>
		<rdfs:comment>InessiveCase expresses that  the referent of the noun it marks is the location within which another referent exists. It has the meaning of 'within' or 'inside' (Lyons 1968: 299; Gove, et al. 1966: 1156; Crystal 1985: 156). X in Y.</rdfs:comment>
	</PositionalCase>
	<PositionalCase rdf:ID="InteressiveCase">
		<rdfs:label xml:lang="en">InteressiveCase</rdfs:label>
		<rdfs:comment>InteressiveCase expresses that  the referent of the noun it marks is the location between which another referent exists. It has the meaning of 'between'.</rdfs:comment>
	</PositionalCase>
	<PositionalCase rdf:ID="AdessiveCase">
		<rdfs:label xml:lang="en">AdessiveCase</rdfs:label>
		<rdfs:comment>AdessiveCase expresses that  the referent of the noun it marks is the location near/at which another referent exists. It has the meaning of 'at' or 'near' (Crystal 1997: 8).</rdfs:comment>
	</PositionalCase>
	<owl:Class rdf:ID="DirectionalCase">
		<rdfs:label xml:lang="en">DirectionalCase</rdfs:label>
		<rdfs:comment>Represents a dynamic spatial relation (involving movement) between two Objects</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#SpatialCase"/>
	</owl:Class>
	<DirectionalCase rdf:ID="LativeCase">
		<rdfs:label xml:lang="en">LativeCase</rdfs:label>
		<rdfs:comment>LativeCase expresses 'motion up to the location of,' or 'as far as' the referent of the noun it marks (Pei and Gaynor 1954: 121; Gove, et al. 1966: 1277).</rdfs:comment>
	</DirectionalCase>
	<DirectionalCase rdf:ID="SuperlativeCase">
		<rdfs:label xml:lang="en">SuperlativeCase</rdfs:label>
		<rdfs:comment>SuperlativeCase expresses that  the referent of the noun it marks is the location onto which another referent is moving. It has the meaning of 'onto'.</rdfs:comment>
	</DirectionalCase>
	<DirectionalCase rdf:ID="SublativeCase">
		<rdfs:label xml:lang="en">SublativeCase</rdfs:label>
		<rdfs:comment>SublativeCase expresses that  the referent of the noun it marks is the location under which another referent is moving toward. It has the meaning 'towards the underneath of'.</rdfs:comment>
	</DirectionalCase>
	<DirectionalCase rdf:ID="IllativeCase">
		<rdfs:label xml:lang="en">IllativeCase</rdfs:label>
		<rdfs:comment>IllativeCase expresses that  the referent of the noun it marks is the location into which another referent is moving. It has the meaning 'into' (Lyons 1968: 299; Gove, et al. 1966: 1126; Crystal 1985: 152).</rdfs:comment>
	</DirectionalCase>
	<DirectionalCase rdf:ID="ElativeCase">
		<rdfs:label xml:lang="en">ElativeCase</rdfs:label>
		<rdfs:comment>ElativeCase expresses that  the referent of the noun it marks is the location out of which another referent is moving. It has the meaning 'out of' (Lyons 1968: 299; Pei and Gaynor 1954: 64; Crystal 1985: 106; Gove, et al. 1966: 730).</rdfs:comment>
	</DirectionalCase>
	<DirectionalCase rdf:ID="InterlativeCase">
		<rdfs:label xml:lang="en">InterlativeCase</rdfs:label>
		<rdfs:comment>InterlativeCase expresses that  the referent of the noun it marks is the location between which another referent is moving. It has the meaning 'to the middle of'.</rdfs:comment>
	</DirectionalCase>
	<DirectionalCase rdf:ID="ContlativeCase">
		<rdfs:label xml:lang="en">ContlativeCase</rdfs:label>
		<rdfs:comment>ContlativeCase expresses that  the referent of the noun it marks is the location in the vicinity of which another referent is moving. It has the meaning 'in the vicinity of'.</rdfs:comment>
	</DirectionalCase>
	<DirectionalCase rdf:ID="AblativeCase">
		<rdfs:label xml:lang="en">AblativeCase</rdfs:label>
		<rdfs:comment>AblativeCase expresses that  the referent of the noun it marks is the location from which another referent is moving. It has the meaning 'from'.</rdfs:comment>
	</DirectionalCase>
	<DirectionalCase rdf:ID="SuperablativeCase">
		<rdfs:label xml:lang="en">SuperablativeCase</rdfs:label>
		<rdfs:comment>SuperlativeCase expresses that  the referent of the noun it marks is the location from over which another referent is moving. It has the meaning 'from over'.</rdfs:comment>
	</DirectionalCase>
	<DirectionalCase rdf:ID="SubablativeCase">
		<rdfs:label xml:lang="en">SubablativeCase</rdfs:label>
		<rdfs:comment>SubablativeCase expresses that  the referent of the noun it marks is the location from under which another referent is moving. It has the meaning 'from under'.</rdfs:comment>
	</DirectionalCase>
	<DirectionalCase rdf:ID="InablativeCase">
		<rdfs:label xml:lang="en">InablativeCase</rdfs:label>
		<rdfs:comment>InablativeCase expresses that  the referent of the noun it marks is the location from within which another referent is moving. It has the meaning 'from within'.</rdfs:comment>
	</DirectionalCase>
	<DirectionalCase rdf:ID="InterablativeCase">
		<rdfs:label xml:lang="en">InterablativeCase</rdfs:label>
		<rdfs:comment>InterablativeCase expresses that  the referent of the noun it marks is the location from between which another referent is moving. It has the meaning 'from inbetween'.</rdfs:comment>
	</DirectionalCase>
	<DirectionalCase rdf:ID="ContablativeCase">
		<rdfs:label xml:lang="en">ContablativeCase</rdfs:label>
		<rdfs:comment>ContablativeCase expresses that  the referent of the noun it marks is the location from near which another referent is moving. It has the meaning 'from near'.</rdfs:comment>
	</DirectionalCase>
	<DirectionalCase rdf:ID="AllativeCase">
		<rdfs:label xml:lang="en">AllativeCase</rdfs:label>
		<rdfs:comment>AllativeCase expresses motion to or toward the referent of the noun it marks (Pei and Gaynor 1954: 6,9,216; Lyons 1968: 299; Crystal 1985: 1213; Gove, et al. 1966: 55,2359).</rdfs:comment>
	</DirectionalCase>
	<DirectionalCase rdf:ID="SuperallativeCase">
		<rdfs:label xml:lang="en">SuperallativeCase</rdfs:label>
		<rdfs:comment>SuperallativeCase expresses that  something is moving toward the region that is above the referent of the noun it marks. It has the meaning 'towards the region that is over'.</rdfs:comment>
	</DirectionalCase>
	<DirectionalCase rdf:ID="SuballativeCase">
		<rdfs:label xml:lang="en">SuballativeCase</rdfs:label>
		<rdfs:comment>SuballativeCase expresses that  something is moving toward the region that is under the referent of the noun it marks. It has the meaning 'towards the region that is under'.</rdfs:comment>
	</DirectionalCase>
	<DirectionalCase rdf:ID="InallativeCase">
		<rdfs:label xml:lang="en">InallativeCase</rdfs:label>
		<rdfs:comment>InallativeCase expresses that  something is moving toward the region that is inside the referent of the noun it marks. It has the meaning  'towards in(side)'.</rdfs:comment>
	</DirectionalCase>
	<DirectionalCase rdf:ID="InterallativeCase">
		<rdfs:label xml:lang="en">InterallativeCase</rdfs:label>
		<rdfs:comment>InterallativeCase expresses that  something is moving toward the region that is in the middle of the referent of the noun it marks. It has the meaning  'towards the middle of'.</rdfs:comment>
	</DirectionalCase>
	<DirectionalCase rdf:ID="ContallativeCase">
		<rdfs:label xml:lang="en">ContallativeCase</rdfs:label>
		<rdfs:comment>ContallativeCase expresses that  something is moving toward the vicinity of the referent of the noun it marks. It has the meaning  'towards the vicinity of'.</rdfs:comment>
	</DirectionalCase>
	<DirectionalCase rdf:ID="TranslativeCase">
		<rdfs:label xml:lang="en">TranslativeCase</rdfs:label>
		<rdfs:comment>TranslativeCase expresses that the referent of the noun, or the quality of the adjective, that it marks is the result of a process of change (Lyons 1968: 299301, Gove, et al. 1966: 813,2429, Sebeok 1946: 17, Hakulinen 1961: 70). X along, across Y.</rdfs:comment>
	</DirectionalCase>
	<DirectionalCase rdf:ID="SupertranslativeCase">
		<rdfs:label xml:lang="en">SupertranslativeCase</rdfs:label>
		<rdfs:comment>SupertranslativeCase expresses the notion of something moving along a trajectory above the referent of the noun it marks. It has the meaning 'along the region over'.</rdfs:comment>
	</DirectionalCase>
	<DirectionalCase rdf:ID="SubtranslativeCase">
		<rdfs:label xml:lang="en">SubtranslativeCase</rdfs:label>
		<rdfs:comment>SubtranslativeCase expresses the notion of something moving along a trajectory underneath the referent of the noun it marks. It has the meaning 'along the region underneath'.</rdfs:comment>
	</DirectionalCase>
	<DirectionalCase rdf:ID="IntranslativeCase">
		<rdfs:label xml:lang="en">IntranslativeCase</rdfs:label>
		<rdfs:comment>IntranslativeCase expresses the notion of something moving through the referent of the noun it marks. It has the meaning 'along through'.</rdfs:comment>
	</DirectionalCase>
	<DirectionalCase rdf:ID="IntertranslativeCase">
		<rdfs:label xml:lang="en">IntertranslativeCase</rdfs:label>
		<rdfs:comment>IntertranslativeCase expresses the notion of something moving along a trajectory between the referent of the noun it marks. It has the meaning 'along the in between.</rdfs:comment>
	</DirectionalCase>
	<DirectionalCase rdf:ID="TerminativeCase">
		<rdfs:label xml:lang="en">TerminativeCase</rdfs:label>
		<rdfs:comment>TerminativeCase expresses the notion of something into but not further than (ie, not through) the referent of the noun it marks. It has the meaning 'into but not through'.</rdfs:comment>
	</DirectionalCase>
	<DirectionalCase rdf:ID="SuperterminativeCase">
		<rdfs:label xml:lang="en">SuperterminativeCase</rdfs:label>
		<rdfs:comment>SuperterminativeCase expresses the notion of something moving into the region over the referent of the noun it marks, but not through that region. It has the meaning 'into the region over'.</rdfs:comment>
	</DirectionalCase>
	<DirectionalCase rdf:ID="SubterminativeCase">
		<rdfs:label xml:lang="en">SubterminativeCase</rdfs:label>
		<rdfs:comment>SubterminativeCase expresses the notion of something moving into the region under the referent of the noun it marks, but not through that region. It has the meaning 'into the region under'.</rdfs:comment>
	</DirectionalCase>
	<DirectionalCase rdf:ID="InterminativeCase">
		<rdfs:label xml:lang="en">InterminativeCase</rdfs:label>
		<rdfs:comment>'into in(side of)'.</rdfs:comment>
	</DirectionalCase>
	<DirectionalCase rdf:ID="InterterminativeCase">
		<rdfs:label xml:lang="en">InterterminativeCase</rdfs:label>
		<rdfs:comment>InterterminativeCase expresses the notion of something moving into the middle of the referent of the noun it marks, but not through it. It has the meaning 'into the middle of'.</rdfs:comment>
	</DirectionalCase>
	<DirectionalCase rdf:ID="ConterminativeCase">
		<rdfs:label xml:lang="en">ConterminativeCase</rdfs:label>
		<rdfs:comment>ConterminativeCase expresses the notion of something moving into the vicinity of the referent of the noun it marks, but not through that region. It has the meaning 'moving into the vicinity of'.</rdfs:comment>
	</DirectionalCase>
	<DirectionalCase rdf:ID="PerlativeCase">
		<rdfs:label xml:lang="en">PerlativeCase</rdfs:label>
		<rdfs:comment>PerlativeCase expresses that something moved 'through','across', or 'along' the referent of the noun that is marked (Blake 1998: 38, 203).</rdfs:comment>
	</DirectionalCase>
	<DirectionalCase rdf:ID="DelativeCase">
		<rdfs:label xml:lang="en">DelativeCase</rdfs:label>
		<rdfs:comment>DelativeCase expresses motion downward from the referent of the noun it marks (Pei and Gaynor 1954: 53; Gove, et al. 1966: 595).</rdfs:comment>
	</DirectionalCase>

<!-->
	**************************************************************
	*Begin Gender
	**************************************************************
	</-->
	<owl:Class rdf:ID="GenderValue">
		<rdfs:label xml:lang="en">GenderValue</rdfs:label>
		<rdfs:comment>GenderValue is the class of values that may be associated with the feature instance 'gender'. GenderValue is the class of all gender types found in language.</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#MorphoSyntacticFeatureValue"/>
	</owl:Class>
	<owl:Class rdf:ID="Animate">
		<rdfs:label xml:lang="en">Animate</rdfs:label>
		<rdfs:comment>One of the two grammatical genders, or classes of nouns, the other being inanimate. Membership in the animate grammatical class is largely based on meanings, in that living things, including humans, animals, spirits, trees, and most plants are included in the animate class of nouns (Valentine 2001:  114).</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#GenderValue"/>
	</owl:Class>
	<GenderValue rdf:ID="inanimate">
		<rdfs:label xml:lang="en">inanimate</rdfs:label>
		<rdfs:comment>One of the two grammatical genders, or noun classes, of Nishnaabemwin, the other being animate. Membership in the inanimate grammatical class is largely based on meaning, in that non-living things, such as objects of manufacture and natural 'non-living' things are included in it (Valentine 2001:  114).</rdfs:comment>
	</GenderValue>
	<Animate rdf:ID="masculine">
		<rdfs:label xml:lang="en">masculine</rdfs:label>
		<rdfs:comment>A grammatical class of nouns whose members tend to be perceived of as male.</rdfs:comment>
	</Animate>
	<Animate rdf:ID="feminine">
		<rdfs:label xml:lang="en">feminine</rdfs:label>
		<rdfs:comment>A grammatical class of nouns whose members tend to be perceived of as female.</rdfs:comment>
	</Animate>


	<!-->**************************************************************
	*Begin Size
	**************************************************************
	</-->
	<owl:Class rdf:ID="SizeValue">
		<rdfs:label xml:lang="en">SizeValue</rdfs:label>
		<rdfs:comment>SizeValue is the class of values that may be associated with the feature instance 'size'. SizeValue is the class of all size types found in language.</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#MorphoSyntacticFeatureValue"/>
	</owl:Class>
	<SizeValue rdf:ID="diminutive">
		<rdfs:label xml:lang="en">diminutive</rdfs:label>
		<rdfs:comment>Generally, a special form of a noun that signals that the object being referred to is small relative to the usual size of such an object.  In some cases it may be used as a term of endearment (Crystal 1980:  116).</rdfs:comment>
	</SizeValue>
	<SizeValue rdf:ID="augmentative">
		<rdfs:label xml:lang="en">augmentative</rdfs:label>
		<rdfs:comment>Generally, a special form of a noun that signals that the object being referred to is large relative to the usual size of such an object (Crystal 1980:  34).</rdfs:comment>
	</SizeValue>
	<!-->**************************************************************
	*Begin Evaluative
	**************************************************************
	</-->
	<owl:Class rdf:ID="EvaluativeValue">
		<rdfs:label xml:lang="en">EvaluativeValue</rdfs:label>
		<rdfs:comment>EvaluativeValue is the class of values that may be associated with the feature instance 'evaluative'. EvaluativeValue is the class of all evaluative types found in language.</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#MorphoSyntacticFeatureValue"/>
	</owl:Class>
	<EvaluativeValue rdf:ID="pejorative">
		<rdfs:label xml:lang="en">pejorative</rdfs:label>
		<rdfs:comment>A special form of a noun that indicates the speaker regards the person or object being referred to with distaste, contempt, or displeasure (Valentine 2001:  190-193).</rdfs:comment>
	</EvaluativeValue>
	<EvaluativeValue rdf:ID="preferred">
		<rdfs:label xml:lang="en">preferred</rdfs:label>
		<rdfs:comment>A special form of a noun that indicates the speaker regards the person or object being referred to with favor or admiration.</rdfs:comment>
	</EvaluativeValue>
	<!-->**************************************************************
	*Begin Polarity
	**************************************************************
	</-->
	<owl:Class rdf:ID="PolarityValue">
		<rdfs:label xml:lang="en">PolarityValue</rdfs:label>
		<rdfs:comment>PolarityValue is the class of values that may be associated with the feature instance 'polarity'. PolarityValue is the class of all polarity types found in language.</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#MorphoSyntacticFeatureValue"/>
	</owl:Class>
	<PolarityValue rdf:ID="positive">
		<rdfs:label xml:lang="en">positive</rdfs:label>
		<rdfs:comment>In general, positive polarity refers to an assertion that contains no marker of negation (Crystal 1980:  299).</rdfs:comment>
	</PolarityValue>
	<PolarityValue rdf:ID="negative">
		<rdfs:label xml:lang="en">negative</rdfs:label>
		<rdfs:comment>A construction that expresses the contradiction of some or all of a proposition (Crystal 1980:  257).</rdfs:comment>
	</PolarityValue>


	<!-->**************************************************************
			*Begin PartOfSpeech
			**************************************************************
	</-->
	<owl:Class rdf:ID="PartOfSpeechValue">
		<rdfs:label xml:lang="en">PartOfSpeechValue</rdfs:label>
		<rdfs:comment>PartOfSpeechValue is the value associated with partOfSpeech feature. PartOfSpeechValue is the class of all lexical types found in language. While a particular theory may not utilize the notion part of speech, it is useful as part of a FeatureSystem. The set of part of speech values for a particular language can be described based on how words behave in the syntax (Payne 1997: 33; Maxwell, Simons, and Hayashi 2001).</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#MorphoSyntacticFeatureValue"/>
	</owl:Class>
	<PartOfSpeechValue rdf:ID="adjective">
		<rdfs:label xml:lang="en">adjective</rdfs:label>
		<rdfs:comment>An adjective is a part of speech whose members modify nouns. An adjective specifies the attributes of a noun referent. Note: this is one case among many. Adjectives are a class of modifiers (Crystal 1997:8; Mish et al. 1990:56; Payne 1997:63).</rdfs:comment>
	</PartOfSpeechValue>

	<PartOfSpeechValue rdf:ID="Adjectivalization">
		<rdfs:label xml:lang="en">Adjectivalization</rdfs:label>
		<rdfs:comment>An adjectivalization is a partOfSpeech whose members differ grammatically from adjectives but which functions as them (Crystal 1997:260; Mish et al. 1990:801).</rdfs:comment>
	</PartOfSpeechValue>

	
	<PartOfSpeechValue  rdf:ID="participle">
		<rdfs:label xml:lang="en">participle</rdfs:label>
		<rdfs:comment>A grammatical term referring to a word derived from a verb and used as an adjective (Crystal 1980:  279).</rdfs:comment>
	</PartOfSpeechValue >

	<PartOfSpeechValue  rdf:ID="prenoun">
		<rdfs:label xml:lang="en">prenoun</rdfs:label>
		<rdfs:comment>An element which may be compounded to the front of a noun to signal information such as size, color, etc. (Valentine 2001:  152-154).</rdfs:comment>
	</PartOfSpeechValue >
	<PartOfSpeechValue  rdf:ID="preverb">
		<rdfs:label xml:lang="en">preverb</rdfs:label>
		<rdfs:comment>An element which may be compounded to the front of a verb, to signal information such as tense, direction, etc. (Valentine 2001:  154-158).</rdfs:comment>
		<rdf:type rdf:resource="#Proclitic"/>
	</PartOfSpeechValue >

	
	
	<owl:Class rdf:ID="Adposition">
		<rdfs:label xml:lang="en">Adposition</rdfs:label>
		<rdfs:comment>  An adposition is a part of speech whose members are of a closed set and occur before or after a complement composed of a noun phrase, noun, pronoun, or clause that functions as a noun phrase and forms a single structure with the complement to express its grammatical and semantic relation to another unit within a clause (Comrie 1989:91; Crystal 1997: 305; Mish et al. 1990:929; Payne 1997:86).</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#PartOfSpeechValue"/>
	</owl:Class>
	<Adposition rdf:ID="postposition">
		<rdfs:label xml:lang="en">postposition</rdfs:label>
		<rdfs:comment>A postposition is an adposition that occurs after its complement (Crystal 1997:300; Payne 1997:86).</rdfs:comment>
	</Adposition>
	<Adposition rdf:ID="preposition">
		<rdfs:label xml:lang="en">preposition</rdfs:label>
		<rdfs:comment>  A preposition is an adposition that occurs before its complement (Crystal 1997:305; Mish et al. 1990:929; Payne 1997:86).</rdfs:comment>
	</Adposition>
	<PartOfSpeechValue rdf:ID="adverb">
		<rdfs:label xml:lang="en">Adverb</rdfs:label>
		<rdfs:label xml:lang="en"/>
		<rdfs:comment>An adverb, narrowly defined, is a part of speech whose members modify verbs for such categories as time, manner, place, or direction. An adverb, broadly defined, is is a part of speech whose members modify any constituent class of words other than nouns, such as  verbs, adjectives, adverbs, phrases, clauses, or sentences. Under this definition, the possible type of modification depends on the class of the constituent being modified (Crystal 1997:11; Mish et al. 1990:59; Payne 1997:69).</rdfs:comment>
	</PartOfSpeechValue>
	<owl:Class rdf:ID="Connective">
		<rdfs:label xml:lang="en">Connective</rdfs:label>
		<rdfs:comment>Also known as a conjunction, a Connective is a class of parts of speech whose members syntactically link words or larger  constituents, and expresses a semantic relationship between them. A conjunction is positionally fixed relative to one or more of the elements related by it, thus distinguishing it from constituents such as English conjunctive adverbs (Crystal 1997:81; Mish et al. 1990:277-278).</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#PartOfSpeechValue"/>
	</owl:Class>
	<owl:Class rdf:ID="CoordinatingConnective">
		<rdfs:label xml:lang="en">CoordinatingConnective</rdfs:label>
		<rdfs:comment>A coordinating connective is a connective that links constituents without syntactically subordinating one to the other (Crystal 1997:93; Mish et al. 1990:288).</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#Connective"/>
	</owl:Class>
	<CoordinatingConnective rdf:ID="correlativeConnective">
		<rdfs:label xml:lang="en">correlativeConnective</rdfs:label>
		<rdfs:comment>A correlative connective is either of a pair of  coordinating conjunctions (connectives) used in ordered fashion. Typically, one is used immediately before each member of a pair of constituents (Crystal 1997:96; Mish et al. 1990:293).</rdfs:comment>
	</CoordinatingConnective>
	<owl:Class rdf:ID="SubordinatingConnective">
		<rdfs:label xml:lang="en">SubordinatingConnective</rdfs:label>
		<rdfs:comment>A subordinating connective is a connective that links constructions by making one of them a constituent of another. The subordinating conjunction typically marks the incorporated constituent (Crystal 1997:370; Mish et al. 1990:1175).</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#Connective"/>
	</owl:Class>
	<SubordinatingConnective rdf:ID="adverbializer">
		<rdfs:label xml:lang="en">adverbializer</rdfs:label>
		<rdfs:comment>An adverbializer is a subordinating connective that links a subordinate clause  to a main clause, and indicates that the subordinate clause has an 'adverbial' or interpropositional relation  to the main clause, indicating purpose, condition, time, and location.</rdfs:comment>
	</SubordinatingConnective>
	<SubordinatingConnective rdf:ID="complementizer">
		<rdfs:label xml:lang="en">complementizer</rdfs:label>
		<rdfs:comment>A complementizer is a connective which marks a complement clause (Crystal 1997:75).</rdfs:comment>
	</SubordinatingConnective>
	<SubordinatingConnective rdf:ID="relativizer">
		<rdfs:label xml:lang="en">relativizer</rdfs:label>
		<rdfs:comment>A relativizer is a subordinating connective that links a relative clause to its head  noun. It is distinguishable from a relative pronoun in that it does not have a nominal function within the relative clause (Payne1997:332)</rdfs:comment>
	</SubordinatingConnective>
	<owl:Class rdf:ID="Determiner">
		<rdfs:label xml:lang="en">Determiner</rdfs:label>
		<rdfs:comment>A Determiner is a partOfSpeech whose members belong to a class of noun modifiers and express the reference, including quantity, of a noun (Crystal 1997:112; Mish et al. 1990:346).</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#PartOfSpeechValue"/>
	</owl:Class>
	<owl:Class rdf:ID="Article">
		<rdfs:label xml:lang="en">article</rdfs:label>
		<rdfs:comment>An article is a member of a small class of determiners that identify a noun's definite or indefinite reference, and new or given status (Crystal 1997:26; Mish et al. 1990:105).</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#Determiner"/>
	</owl:Class>
	<Article rdf:ID="definiteArticle">
		<rdfs:label xml:lang="en">definiteArticle</rdfs:label>
		<rdfs:comment>An article is a part of speech whose members refer to a specific, identifiable entity (or class of entities) (Crystal 1997:107).</rdfs:comment>
	</Article>
	<Article rdf:ID="indefiniteArticle">
		<rdfs:label xml:lang="en">indefiniteArticle</rdfs:label>
		<rdfs:comment>An article is a part of speech whose members are used to refer to an entity (or class of entities) which is not capable of specific identification (Crystal 1997:193).</rdfs:comment>
	</Article>
	<Determiner rdf:ID="demonstrative">
		<rdfs:label xml:lang="en">demonstrative</rdfs:label>
		<rdfs:comment>A demonstrative is a determiner that is used deictically to indicate a referent's spatial, temporal, or discourse location. A demonstrative functions as a modifier of a noun, or a pronoun (Crystal 1997:312; Mish et al. 1990:338).</rdfs:comment>
	</Determiner>
	<owl:Class rdf:ID="Quantifier">
		<rdfs:label xml:lang="en">Quantifier</rdfs:label>
		<rdfs:comment>A quantifier is a determiner that expresses a referent's definite or indefinite  number or amount. A quantifier functions as a modifier of a noun, or a pronoun (Crystal 1997:317; Mish et al. 1990:963).</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#Determiner"/>
	</owl:Class>
	<owl:Class rdf:ID="Numeral">
		<rdfs:label xml:lang="en">Numeral</rdfs:label>
		<rdfs:comment>A numeral is a partOfSpeech whose members function most typically as adjectives or pronouns and express a number, or relation to the number, such as one of the following: quantity, sequence, frequency, fraction (Hartmann and Stork 1972:155; Pei and Gaynor 1954:149).</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#Quantifier"/>
	</owl:Class>
	<Numeral rdf:ID="cardinalNumeral">
		<rdfs:label xml:lang="en">cardinalNumeral</rdfs:label>
		<rdfs:comment>A cardinal numeral is a numeral of the class whose members are considered basic in form, are used in counting, and are used in expressing how many objects are referred to (Crystal 1997:52; Mish et al. 1990:207).</rdfs:comment>
	</Numeral>
	<Numeral rdf:ID="distributiveNumeral">
		<rdfs:label xml:lang="en">distributiveNumeral</rdfs:label>
		<rdfs:comment>A distributive numeral is a numeral which expresses a group of the number specified.</rdfs:comment>
	</Numeral>
	<Numeral rdf:ID="multiplicativeNumeral">
		<rdfs:label xml:lang="en">multiplicativeNumeral</rdfs:label>
		<rdfs:comment>A multiplicative numeral is a numeral that expresses how many fold or how many times (Pei and Gaynor 1954:149; Hartmann and Stork 1972:147).</rdfs:comment>
	</Numeral>
	<Numeral rdf:ID="ordinalNumeral">
		<rdfs:label xml:lang="en">ordinalNumeral</rdfs:label>
		<rdfs:comment>An ordinal numeral is a numeral belonging to a class whose members designate positions in a sequence (Crystal 1997:272; Mish et al. 1990:831).</rdfs:comment>
	</Numeral>
	<Numeral rdf:ID="partitiveNumeral">
		<rdfs:label xml:lang="en">partitiveNumeral</rdfs:label>
		<rdfs:comment>A partitive numeral is a numeral that expresses a fraction (Pei and Gaynor 1954:149; Hartmann and Stork 1972:165).</rdfs:comment>
	</Numeral>
	<PartOfSpeechValue rdf:ID="interjection">
		<rdfs:label xml:lang="en">interjection</rdfs:label>
		<rdfs:comment>An interjection is a part of speech, typically brief in form, such as one syllable or word, whose members are used most often as exclamations or parts of an exclamation. An interjection, typically expressing an emotional reaction, often with respect to an accompanying sentence, is not syntactically related to other accompanying expressions, and may include a combination of sounds not otherwise found in the language (Crystal 1997:200).</rdfs:comment>
	</PartOfSpeechValue>
	<owl:Class rdf:ID="Noun">
		<rdfs:label xml:lang="en">noun</rdfs:label>
		<rdfs:comment>A noun is a broad classification of parts of speech which include substantives and nominals (Crystal 1997:371; Mish et al. 1990:1176).</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#PartOfSpeechValue"/>
	</owl:Class>
	<Noun rdf:ID="substantive">
		<rdfs:label xml:lang="en">substantive</rdfs:label>
		<rdfs:comment>A substantive is a member of the syntactic class in which the names of physical, concrete, relatively unchanging experiences are most typically found whose members may act as subjects and  objects, and most of whose members have inherently determined grammatical  gender (in languages which inflect for gender) (Crystal 1997:264; Mish et al. 1990:808; Givón 1984:51-52; Payne 1997:33).</rdfs:comment>
	</Noun>
	<owl:Class rdf:ID="Nominal">
		<rdfs:label xml:lang="en">Nominal</rdfs:label>
		<rdfs:comment>A nominal is a partOfSpeech whose members differ grammatically from a substantive but which functions as one (Crystal 1997:260; Mish et al. 1990:801).</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#Noun"/>
	</owl:Class>
	<Nominal rdf:ID="gerund">
		<rdfs:label xml:lang="en">gerund</rdfs:label>
		<rdfs:comment>A part of speech derived from a verb and used as a noun, usually restricted to non-finite forms of the verb (Crystal 1997: 279).</rdfs:comment>
	</Nominal>
	<owl:Class rdf:ID="Particle">
		<rdfs:label xml:lang="en">Particle</rdfs:label>
		<rdfs:comment>A particle is a partOfSpeech whose members do not belong to one of the main classes of words, is invariable, and typically has grammatical or pragmatic meaning.</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#PartOfSpeechValue"/>
	</owl:Class>
	<Particle rdf:ID="verbalParticle">
		<rdfs:label xml:lang="en">verbalParticle</rdfs:label>
		<rdfs:comment>A verbal particle is a member of a closed class of particles which co-occur with some verbs to form phrasal verbs. In some languages, verbal particles are identical to certain adpositions.</rdfs:comment>
	</Particle>
	<Particle rdf:ID="questionParticle">
		<rdfs:label xml:lang="en">questionParticle</rdfs:label>
		<rdfs:comment>A particle is a part of speech whose members signal a yes/no question (Payne 1997:296).</rdfs:comment>
	</Particle>
	<owl:Class rdf:ID="NominalParticle">
		<rdfs:label xml:lang="en">NominalParticle</rdfs:label>
		<rdfs:comment>A nominal particle is a member of a closed class of particles that co-occur with nouns.</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#Particle"/>
	</owl:Class>
	<NominalParticle rdf:ID="classifier">
		<rdfs:label xml:lang="en">classifier</rdfs:label>
		<rdfs:comment>A classifier is a partOfSpeech whose members express the classification of a noun (Crystal 1997:61; Mish et al. 1990:246; Payne 1997:107).</rdfs:comment>
	</NominalParticle>
	<owl:Class rdf:ID="ProForm">
		<rdfs:label xml:lang="en">ProForm</rdfs:label>
		<rdfs:comment>A ProForm is a partOfSpeech whose members usually substitute for other constituents, including phrases, clauses, or sentences, and whose meaning is recoverable from the linguistic or extralinguistic context (Schachter 1985:24-25; Crystal 1997:310).</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#PartOfSpeechValue"/>
	</owl:Class>
	<ProForm rdf:ID="expletive">
		<rdfs:label xml:lang="en">expletive</rdfs:label>
		<rdfs:comment>An expletive (also known as a dummy word) is a part of speech whose members have no meaning, but complete a sentence to make it grammatical (Crystal 1997:127; Mish et al. 1990:437).	</rdfs:comment>
	</ProForm>
	<ProForm rdf:ID="existentialMarker">
		<rdfs:label xml:lang="en">existentialMarker</rdfs:label>
		<rdfs:comment>An existential marker is a partOfSpeech whose members are found in distinct clause types and which mark a referent's existence (Crystal 1997:142).</rdfs:comment>
	</ProForm>
	<ProForm rdf:ID="interrogativeProForm">
		<rdfs:label xml:lang="en">interrogativeProForm</rdfs:label>
		<rdfs:comment>An interrogative proForm is a proForm that is used in questions to stand for the item questioned.</rdfs:comment>
	</ProForm>
	<ProForm rdf:ID="proAdjective">
		<rdfs:label xml:lang="en">proAdjective</rdfs:label>
		<rdfs:comment>A proAdjective is a proForm that substitutes for an adjective or adjective phrase.</rdfs:comment>
	</ProForm>
	<ProForm rdf:ID="proAdverb">
		<rdfs:label xml:lang="en">proAdverb</rdfs:label>
		<rdfs:comment>A proAdverb is a proForm that substitutes for an adverb or other expression having an adverbial function.</rdfs:comment>
	</ProForm>
	<owl:Class rdf:ID="Pronoun">
		<rdfs:label xml:lang="en">Pronoun</rdfs:label>
		<rdfs:comment>A Pronoun is a proForm which functions like a noun and substitutes for a noun or  noun phrase (Crystal 1997:312; Mish et al. 1990:942).</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#ProForm"/>
	</owl:Class>
	<Pronoun rdf:ID="indefinitePronoun">
		<rdfs:label xml:lang="en">indefinitePronoun</rdfs:label>
		<rdfs:comment>An indefinite pronoun is a pronoun that belongs to a class whose members indicate  indefinite reference (Crystal 1997: 312; Mish et al. 1990:612).</rdfs:comment>
	</Pronoun>
	<owl:Class rdf:ID="PersonalPronoun">
		<rdfs:label xml:lang="en">PersonalPronoun</rdfs:label>
		<rdfs:comment>A personal pronoun is a pronoun that expresses a distinction of person deixis (Mish et al. 1990:878).</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#Pronoun"/>
	</owl:Class>
	<PersonalPronoun rdf:ID="emphaticPronoun">
		<rdfs:label xml:lang="en">emphaticPronoun</rdfs:label>
		<rdfs:comment>An emphatic pronoun is a personal pronoun that is used to emphasize its  referent.</rdfs:comment>
	</PersonalPronoun>
	<PersonalPronoun rdf:ID="possessivePronoun">
		<rdfs:label xml:lang="en">possessivePronoun</rdfs:label>
		<rdfs:comment>A possessive pronoun is a pronoun that expresses ownership and relationships like ownership, such as kinship, and other forms of association (Crystal 1997:312; Mish et al. 1990:918).</rdfs:comment>
	</PersonalPronoun>
	<PersonalPronoun rdf:ID="reflexivePronoun">
		<rdfs:label xml:lang="en">reflexivePronoun</rdfs:label>
		<rdfs:comment>A reflexive pronoun is a pronoun that has coreference with the subject (Mish et al. 1990:990).</rdfs:comment>
	</PersonalPronoun>
	<Pronoun rdf:ID="reciprocalPronoun">
		<rdfs:label xml:lang="en">reciprocalPronoun</rdfs:label>
		<rdfs:comment>A reciprocal pronoun is a pronoun that expresses a mutual feeling or action among the referents of a plural subject (Crystal 1997:323; Mish et al. 1990:982).</rdfs:comment>
	</Pronoun>
	<Pronoun rdf:ID="relativePronoun">
		<rdfs:label xml:lang="en">relativePronoun</rdfs:label>
		<rdfs:comment>A relative pronoun is a pronoun that marks a relative clause, functions grammatically within the relative clause, and is coreferential to the word modified by the relative clause (Crystal 1997:329).</rdfs:comment>
	</Pronoun>
	<owl:Class rdf:ID="Verb">
		<rdfs:label xml:lang="en">Verb</rdfs:label>
		<rdfs:comment>A Verb is a part of speech whose members typically signal events and actions; constitute, singly or in a phrase, a minimal  predicate in a  clause; govern the number and types of other constituents which may occur in the clause; and, in inflectional languages, may be inflected for tense, aspect, voice, modality, or agreement with other constituents in person, number, or grammatical gender  (Crystal 1997:409; Mish et al. 1990:1309; Givón 1984:52; Payne 1997:47).</rdfs:comment>
		<rdfs:subClassOf rdf:resource="#PartOfSpeechValue"/>
	</owl:Class>
	<Verb rdf:ID="ditransitiveVerb">
		<rdfs:label xml:lang="en">ditransitiveVerb</rdfs:label>
		<rdfs:comment>A ditransitive verb is a verb that takes two objects (Crystal 1997:397).</rdfs:comment>
	</Verb>
	<Verb rdf:ID="intransitiveVerb">
		<rdfs:label xml:lang="en">intransitiveVerb</rdfs:label>
		<rdfs:comment>An intransitive verb is a verb that cannot take a direct object, and describes a property, state, or situation involving only one participant (Crystal 1997:397; Payne 1997:171).</rdfs:comment>
	</Verb>
	<Verb rdf:ID="transitiveVerb">
		<rdfs:label xml:lang="en">transitiveVerb</rdfs:label>
		<rdfs:comment>A transitive verb is a verb that takes a direct object, and describes a relation between two participants (Crystal 1997:397; Mish et al. 1990:1254; Payne 1997:171).</rdfs:comment>
	</Verb>
	<!-->
*******************************************************************************
*	Begin Properties
*******************************************************************************
</-->
	<!-->

<owl:ObjectProperty rdf:ID="">
		<rdfs:label xml:lang="en"></rdfs:label>
		<rdfs:comment></rdfs:comment>
		<rdfs:subPropertyOf rdf:resource="#"/>
</owl:ObjectProperty>
</-->
	<!-->
*******************************************************************************
*	General Semiotic Properties
*******************************************************************************
</-->
	<!-->
	*Try and work in these SUMO predicates

	<owl:ObjectProperty rdf:ID="refers">
		<rdfs:label xml:lang="en"></rdfs:label>
		<rdfs:comment></rdfs:comment>
	</owl:ObjectProperty>

	<owl:ObjectProperty rdf:ID="represents">
		<rdfs:label xml:lang="en"></rdfs:label>
		<rdfs:comment></rdfs:comment>
		<rdfs:subPropertyOf rdf:resource="#refers"/>
	</owl:ObjectProperty>
</-->
	<owl:ObjectProperty rdf:ID="realization">
		<rdfs:label xml:lang="en">realization</rdfs:label>
		<rdfs:comment>This relation associates some LinguisticUnit with its corresponding OrthographicExpression.</rdfs:comment>
		<rdfs:domain rdf:resource="#LinguisticUnit"/>
		<rdfs:range rdf:resource="#WrittenExpression"/>
	</owl:ObjectProperty>
	<owl:ObjectProperty rdf:ID="hasSense">
		<rdfs:label xml:lang="en">hasSense</rdfs:label>
		<rdfs:comment>This relation associates some LinguisticUnit with a SemanticUnit. </rdfs:comment>
		<rdfs:domain rdf:resource="#LinguisticUnit"/>
		<!--rdfs:range rdf:resource="#SemanticUnit"/-->
	</owl:ObjectProperty>
	<owl:ObjectProperty rdf:ID="names">
		<rdfs:label xml:lang="en">names</rdfs:label>
		<rdfs:comment>This relation associates some written expression with any entity in the ontology. It labels or expresses that entity.</rdfs:comment>
		<rdfs:domain rdf:resource="#WrittenExpression"/>
		<rdfs:range rdf:resource="#Entity"/>
	</owl:ObjectProperty>
	<!-->
*******************************************************************************
*	WrittenExpression Properties
*******************************************************************************
</-->
	<owl:DatatypeProperty rdf:ID="hasForm">
		<rdfs:label xml:lang="en">hasForm</rdfs:label>
		<rdfs:comment>This relation is included as a work-around, because string literals cannot be used as classes themselves, i.e., as subjects in an rdf graph. It expresses the substantial part of all written expressions. </rdfs:comment>
		<rdfs:domain rdf:resource="#WrittenExpression"/>
		<rdfs:range rdf:resource="&xsd;string"/>
	</owl:DatatypeProperty>
	<owl:ObjectProperty rdf:ID="annotation">
		<rdfs:label xml:lang="en">annotation</rdfs:label>
		<rdfs:comment>The relation between linguistic data and some other expression which provides some kind linguistic information other than what is explicitly given by the data. </rdfs:comment>
	</owl:ObjectProperty>
	<owl:ObjectProperty rdf:ID="translation">
		<rdfs:label xml:lang="en">translates</rdfs:label>
		<rdfs:comment>The relation between an orthographic expression in one language and some orthographic expression in another such that both expressions have the same or roughly the same meaning.</rdfs:comment>
		<rdfs:subPropertyOf rdf:resource="#annotation"/>
	</owl:ObjectProperty>
	<owl:ObjectProperty rdf:ID="literalTranslation">
		<rdfs:label xml:lang="en">literalTranslation</rdfs:label>
		<rdfs:comment>The relation between an orthographic expression in one language and some orthographic expression in another such that the translation is done on a word by word basis without regard for the meaning of idioms [revise this definition].</rdfs:comment>
		<rdfs:subPropertyOf rdf:resource="#translation"/>
	</owl:ObjectProperty>
	<owl:ObjectProperty rdf:ID="freeTranslation">
		<rdfs:label xml:lang="en">freeTranslation</rdfs:label>
		<rdfs:comment>The relation between an orthographic expression in one language and some orthographic expression in another such that both expressions have exactly the same meaning. The words in the translation may not correspond to the those in the source expression.</rdfs:comment>
		<rdfs:subPropertyOf rdf:resource="#translation"/>
	</owl:ObjectProperty>
</rdf:RDF>
