Matches in LOV for { ?s <http://www.w3.org/2000/01/rdf-schema#comment> ?o. }
- Thursday comment "Thursday as a day of the week.".
- Tuesday comment "Tuesday as a day of the week.".
- TypeAndQuantityNode comment "This class collates all the information about a gr:ProductOrService included in a bundle. If a gr:Offering contains just one item, you can directly link from the gr:Offering to the gr:ProductOrService using gr:includes. If the offering contains multiple items, use an instance of this class for each component to indicate the quantity, unit of measurement, and type of product, and link from the gr:Offering via gr:includesObject.\n\nExample: An offering may include of 100g of Butter and 1 kg of potatoes, or 1 cell phone and 2 headsets.".
- UnitPriceSpecification comment "A unit price specification is a conceptual entity that specifies the price asked for a given gr:Offering by the respective gr:Business Entity. An offering may be linked to multiple unit price specifications that specify alternative prices for non-overlapping sets of conditions (e.g. quantities or sales regions) or with differing validity periods. \n\nA unit price specification is characterized by (1) the lower and upper limits and the unit of measurement of the eligible quantity, (2) by a monetary amount per unit of the product or service, and (3) whether this prices includes local sales taxes, namely VAT.\n\t\nExample: The price, including VAT, for 1 kg of a given material is 5 Euros per kg for 0 - 5 kg and 4 Euros for quantities above 5 kg.\n\nThe eligible quantity interval for a given price is specified using the object property gr:hasEligibleQuantity, which points to an instance of gr:QuantitativeValue. The currency is specified using the gr:hasCurrency property, which points to an ISO 4217 currency code. The unit of measurement for the eligible quantity is specified using the gr:hasUnitOfMeasurement datatype property, which points to an UN/CEFACT Common Code (3 characters).\n\t\nIn most cases, the appropriate unit of measurement is the UN/CEFACT Common Code \"C62\" for \"Unit or piece\", since a gr:Offering is defined by the quantity and unit of measurement of all items included (e.g. \"1 kg of bananas plus a 2 kg of apples\"). As long at the offering consists of only one item, it is also possible to use an unit of measurement of choice for specifying the price per unit. For bundles, however, only \"C62\" for \"Unit or piece\" is a valid unit of measurement.\n\nYou can assume that the price is given per unit or piece if there is no gr:hasUnitOfMeasurement property attached to the price.\n\t\nWhether VAT and sales taxes are included in this price is specified using the property gr:valueAddedTaxIncluded (xsd:boolean).\n\t\nThe price per unit of measurement is specified as a float value of the gr:hasCurrencyValue property. The currency is specified via the gr:hasCurrency datatype property. Whether the price includes VAT or not is indicated by the gr:valueAddedTaxIncluded datatype property.\n\nThe property priceType can be used to indicate that the price is a retail price recommendation only (i.e. a list price). \n\nIf the price can only be given as a range, use gr:hasMaxCurrencyValue and gr:hasMinCurrencyValue for the upper and lower bounds.\n\nImportant: When querying for the price, always use gr:hasMaxCurrencyValue and gr:hasMinCurrencyValue.\n\nNote 1: Due to the complexity of pricing scenarios in various industries, it may be necessary to create extensions of this fundamental model of price specifications. Such can be done easily by importing and refining the GoodRelations ontology.\n\nNote 2: For Google, attaching a gr:validThrough statement to a gr:UnitPriceSpecification is mandatory.".
- WarrantyPromise comment "This is a conceptual entity that holds together all aspects of the n-ary relation gr:hasWarrantyPromise.\n\nA Warranty promise is an entity representing the duration and scope of services that will be provided to a customer free of charge in case of a defect or malfunction of the gr:ProductOrService. A warranty promise is characterized by its temporal duration (usually starting with the date of purchase) and its gr:WarrantyScope. The warranty scope represents the types of services provided (e.g. labor and parts, just parts) of the warranty included in an gr:Offering. The actual services may be provided by the gr:BusinessEntity making the offering, by the manufacturer of the product, or by a third party. There may be multiple warranty promises associated with a particular offering, which differ in duration and scope (e.g. pick-up service during the first 12 months, just parts and labor for 36 months).\n\nExamples: 12 months parts and labor, 36 months parts".
- WarrantyScope comment "The warranty scope represents types of services that will be provided free of charge by the vendor or manufacturer in the case of a defect (e.g. labor and parts, just parts), as part of the warranty included in an gr:Offering. The actual services may be provided by the gr:BusinessEntity making the offering, by the manufacturer of the product, or by a third party. \n\nExamples: Parts and Labor, Parts".
- Wednesday comment "Wednesday as a day of the week.".
- availableAtOrFrom comment "This states that a particular gr:Offering is available at or from the given gr:Location (e.g. shop or branch).".
- datatypeProductOrServiceProperty comment "This property is the super property for all pure datatype properties that can be used to describe a gr:ProductOrService.\n\nIn products and services ontologies, only such properties that are no quantitative properties and that have no predefined gr:QualitativeValue instances are subproperties of this property. In practice, this refers to a few integer properties for which the integer value represents qualitative aspects, for string datatypes (as long as no predefined values exist), for boolean datatype properties, and for dates and times.".
- description comment "A short textual description of the resource. \n\nThis property is semantically equivalent to rdfs:comment and just meant as a handy shortcut for marking up data.".
- equal comment "This ordering relation for qualitative values indicates that the subject is equal to the object.".
- greater comment "This ordering relation for qualitative values indicates that the subject is greater than the object.".
- greaterOrEqual comment "This ordering relation for qualitative values indicates that the subject is greater than or equal to the object.".
- hasEAN_UCC-13 comment "The EAN·UCC-13 code of the given gr:ProductOrService or gr:Offering. This code is now officially called GTIN-13 (Global Trade Identifier Number) or EAN·UCC-13. Former 12-digit UPC codes can be converted into EAN·UCC-13 code by simply adding a preceeding zero.\n\nNote 1: When using this property for searching by 12-digit UPC codes, you must add a preceeding zero digit.\nNote 2: As of January 1, 2007, the former ISBN numbers for books etc. have been integrated into the EAN·UCC-13 code. For each old ISBN-10 code, there exists a proper translation into EAN·UCC-13 by adding \"978\" or \"979\" as prefix. Since the old ISBN-10 is now deprecated, GoodRelations does not provide a property for ISBNs.".
- hasManufacturer comment "This object property links a gr:ProductOrService to the gr:BusinessEntity that produces it. Mostly used with gr:ProductOrServiceModel.".
- hasMaxCurrencyValue comment "This property specifies the UPPER BOUND of the amount of money for a price RANGE per unit, shipping charges, or payment charges. The currency and other relevant details are attached to the respective gr:PriceSpecification etc.\nFor a gr:UnitPriceSpecification, this is the UPPER BOUND for the price for one unit or bundle (as specified in the unit of measurement of the unit price specification) of the respective gr:ProductOrService. For a gr:DeliveryChargeSpecification or a gr:PaymentChargeSpecification, it is the UPPER BOUND of the price per delivery or payment.\n\nUsing gr:hasCurrencyValue sets the upper and lower bounds to the same given value, i.e., x gr:hasCurrencyValue y implies x gr:hasMinCurrencyValue y, x gr:hasMaxCurrencyValue y.".
- hasMaxValue comment "This property captures the upper limit of a gr:QuantitativeValue instance.".
- hasMaxValueFloat comment "This property captures the upper limit of a gr:QuantitativeValueFloat instance.".
- hasMaxValueInteger comment "This property captures the upper limit of a gr:QuantitativeValueInteger instance.".
- hasMinCurrencyValue comment "This property specifies the LOWER BOUND of the amount of money for a price RANGE per unit, shipping charges, or payment charges. The currency and other relevant details are attached to the respective gr:PriceSpecification etc.\nFor a gr:UnitPriceSpecification, this is the LOWER BOUND for the price for one unit or bundle (as specified in the unit of measurement of the unit price specification) of the respective gr:ProductOrService. For a gr:DeliveryChargeSpecification or a gr:PaymentChargeSpecification, it is the LOWER BOUND of the price per delivery or payment.\n\nUsing gr:hasCurrencyValue sets the upper and lower bounds to the same given value, i.e., x gr:hasCurrencyValue y implies x gr:hasMinCurrencyValue y, x gr:hasMaxCurrencyValue y.".
- hasMinValue comment "This property captures the lower limit of a gr:QuantitativeValue instance.".
- hasMinValueFloat comment "This property captures the lower limit of a gr:QuantitativeValueFloat instance.".
- hasMinValueInteger comment "This property captures the lower limit of a gr:QuantitativeValueInteger instance.".
- hasNext comment "This ordering relation for gr:DayOfWeek indicates that the subject is directly followed by the object.\n\nExample: Monday hasNext Tuesday\n\nSince days of the week are a cycle, this property is not transitive.".
- hasPrevious comment "This ordering relation for gr:DayOfWeek indicates that the subject is directly preceeded by the object.\n\nExample: Tuesday hasPrevious Monday\n\nSince days of the week are a cycle, this property is not transitive.".
- hasPriceSpecification comment "This links a gr:Offering to a gr:PriceSpecification or specifications. There can be unit price specifications, payment charge specifications, and delivery charge specifications. For each type, multiple specifications for the same gr:Offering are possible, e.g. for different quantity ranges or for different currencies, or for different combinations of gr:DeliveryMethod and target destinations.\n\nRecommended retail prices etc. can be marked by the gr:priceType property of the gr:UnitPriceSpecification.".
- isSimilarTo comment "This states that a given gr:ProductOrService is similar to another product or service. Of course, this is a subjective statement; when interpreting it, the trust in the origin of the statement should be taken into account.".
- isVariantOf comment "This states that a particular gr:ProductOrServiceModel is a variant of another product or service model. It is pretty safe to infer that the variant inherits all gr:quantitativeProductOrServiceProperty, gr:qualitativeProductOrServiceProperty, and gr:datatypeProductOrServiceProperty values that are defined for the first gr:ProductOrServiceModel.\n\nExample:\nfoo:Red_Ford_T_Model gr:isVariantOf foo:Ford_T_Model".
- lesser comment "This ordering relation for gr:QualitativeValue pairs indicates that the subject is lesser than the object.".
- lesserOrEqual comment "This ordering relation for gr:QualitativeValue pairs indicates that the subject is lesser than or equal to the object.".
- name comment "A short text describing the respective resource.\n\nThis property is semantically equivalent to dcterms:title and rdfs:label and just meant as a handy shortcut for marking up data.".
- nonEqual comment "This ordering relation for gr:QualitativeValue pairs indicates that the subject is not equal to the object.".
- offers comment "This links a gr:BusinessEntity to the offers (gr:Offering) it makes. If you want to express interest in receiving offers, use gr:seeks instead.".
- predecessorOf comment "This property indicates that the subject is a previous, often discontinued variant of the gr:ProductOrServiceModel used as the object.\n\nExample: Golf III predecessorOf Golf IV\n\nThis relation is transitive.".
- qualitativeProductOrServiceProperty comment "This is the super property of all qualitative properties for products and services. All properties in product or service ontologies for which gr:QualitativeValue instances are specified are subproperties of this property.".
- quantitativeProductOrServiceProperty comment "This is the super property of all quantitative properties for products and services. All properties in product or service ontologies that specify quantitative characteristics, for which an interval is at least theoretically an appropriate value, are subproperties of this property.".
- serialNumber comment "The serial number or any alphanumeric identifier of a particular product. Note that serial number are unique only for the same brand or the same model, so you cannot infer from two occurrences of the same serial number that the objects to which they are attached are identical.\n\nThis property can also be attached to a gr:Offering in cases where the included products are not modeled in more detail.".
- successorOf comment "This property indicates that the subject is a newer, often updated or improved variant of the gr:ProductOrServiceModel used as the object.\n\nExample: Golf III successorOf Golf II\n\nThis relation is transitive.".
- valueReference comment "The superclass of properties that link a gr:QuantitativeValue or a gr:QualitativeValue to a second gr:QuantitativeValue or a gr:QualitativeValue that provides additional information on the original value. A good modeling practice is to define specializations of this property (e.g. foo:referenceTemperature) for your particular domain.".
- v1 comment "Ontology for healthcare metadata - especially metadata found in DICOM files \n(Digital Imaging and Communications in Medicine, see http://dicom.nema.org/).\n\nAuthor: Michael Brunnbauer, Bonubase GmbH (www.bonubase.com).\nThe author's email address is brunni@netestate.de.\n\nSee http://purl.org/healthcarevocab/v1help for explanations.".
- ru-meta.owl comment "This is the dirst draft for a recommendation for metadata on Representational Units (RU) which appear in ontologies. It is so far harmonized for implementation through owl annotation properties.\nComments to: OBI discussion list, metadata wiki or to schober at ebi.ac.uk".
- skos-thes comment "These notes apply to the published mapping between the ISO 25964 data model and the SKOS schema (http://www.niso.org/schemas/iso25964/correspondencesSKOS/).\nRemarks can be exchanged using: 25964info@list.niso.org \nSubscription info and archive is on: http://www.niso.org/lists/25964info/ \nGeneral information about ISO 25964: http://www.niso.org/schemas/iso25964/\n\nThe annotation http://www.w3.org/2003/06/sw-vocab-status/ns#term_status indicates \"proposed\" properties that are not part of the mapping documentation.".
- CompoundEquivalence comment "ISO CompoundEquivalence \n\niso-thes:plusUseTerm (and its inverse iso-thes:plusUFTerm) may be derived from iso-thes:CompoundEquivalence.\n\nFor a iso-thes:CompoundEquivalence instance each derived iso thes:plusUseTerm has as:\n- subject: the iso thes:plusUF value\n- object: the iso thes:plusUse value\n\nAn ISO 25964 compliant thesaurus only has one compound equivalence relation for each split non preferred term.\n\nIn special cases where the iso-thes:SplitNonPreferredTerm has more than one decomposition, the inverse inference may not be possible. (While this situation should not arise within a single thesaurus that complies with ISO 25964, it could occur if terms and relationships have been drawn from more than one thesaurus. For this reason the property skos:inScheme (http://www.w3.org/2004/02/skos/core#inScheme) should be used with each instance of the class Compound Equivalence, to relate it to its Thesaurus.)".
- ConceptGroup comment "ISO ConceptGroup\n\nConcept groups have several applications.\n\nOne such application is illustrated by the EUROVOC and the UNESCO thesaurus. Both of these use a super structure of domain and of micro-thesaurus. Both of these structuring elements can be modeled using ConceptGroup.".
- PreferredTerm comment "ISO PreferredTerm:\n\nInstances of iso-thes:PreferredTerm are objects of skos-xl:prefLabel statements.\n\nMaking the class explicit allows RDF/OWL consistency checks for CompoundEquivalence.".
- SimpleNonPreferredTerm comment "ISO SimpleNonPreferredTerm\n\nInstances of iso:SimpleNonPreferredTerm are the object of either of skos xl:altLabel or skos xl:hiddenLabel statements.\n\n\nIdentifying cases of Equivalence:\n\nIn SKOS/-XL, Equivalence may be derived between the skos/skos xl:prefLabel statements on one hand and the skos/skos xl:altLabel or the skos/skos xl:hiddenLabel statements on the other hand where:\n- the subject of all these statements is the same instance of skos:Concept,\n- the language of all the bound labels is the same,\n- the prefLabel has the role USE, and\n- the altLabel and hiddenLabel have the role UF.".
- SplitNonPreferredTerm comment "iso SplitNonPreferredTerm\n\nThis class provides for an 'imagined' concept that may exist in a user’s mind but is not present in the thesaurus (Concept Scheme); it can, however, be represented by a combination of two or more preferred terms (skos-xl:prefLabel) in the thesaurus. (In contrast, concepts present in the thesaurus are provided for by the ThesaurusConcept class.)\nThis label is provided by the object property iso thes:plusUF\n- domain: iso-thes:CompoundEquivalence\n- range: iso-thes:SplitNonPreferredTerm.".
- Carrier comment "This class contains a controlled list of \"carriers\" that can be used to contain a schema:CreativeWork.".
- File comment "Describes a file that can be imported in a particular platform such as R or SAS and execute the model. This could also be a PMML-XML file.".
- Method comment "Describes a statistical or data mining method used for creating a model. We assume that this class uses a set of predefined concepts such as linear regression, logistic regression, markov models, support vector machine, random forest, neural networks etc.".
- Model comment "The actual predictive model that is described by the vocabulary.".
- Power comment "Describes the predictive power of a model.".
- Variable comment "Represents the variables that are included in the predictive model.".
- data comment "Connects a model to the dataset that contains the actual data that have been used for the development of the model.".
- Abstract 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. [SUMO 2010]".
- Adjectival comment "An adjectival, or 'adjective', is a part of speech whose members modify nouns. An adjectival specifies the attributes of a noun referent. Note: this is one case among many. Adjectivals are a class of modifiers. An adjectival may be inflected as comparitive or superlative [Crystal 1997: 8; Payne 1997: 63].".
- Adposition 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; Payne 1997: 86].".
- Affix comment "An affix is a morpheme with an abstract meaning which can only be used when added to a root morpheme. These are classified in four different ways, depending on their position with reference to the root: suffix, prefix, circumfix and infix. [Haspelmath 2002: 265; Crystal 1980: 17]".
- AirstreamProperty comment "Refers to the direction of the airstream in speech sound production. In the canonical literature, there are three airstream mechanisms: pulmonic, velaric, and glottalic. Glottalic airstream mechanism is sometimes used to describe the method of production of ejectives and implosives. Ladefoged and Maddieson prefer to regard implosives and ejectives as characterized by a laryngeal parameter of movement rather than an airstream property. [Ladefoged and Maddieson 1996: 372-373]".
- AnteriorProperty comment "Properties characterized by focusing on the upper passive articulator on the roof of the mouth [Ladefoged 1997: 597].".
- ApicalityProperty comment "Properties characterized by focusing on the action of the lower, active articulator, i.e. which part of the tongue is used in articulation [Ladefoged 1997: 597].".
- Article 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].".
- ArticulatoryProperty comment "The class of properties defining how sounds are produced in the mouth. [Ladefoged".
- AspectProperty comment "The term 'aspect'; designates the perspective taken on the internal temporal organization of the event, and different values of the Aspect Feature distinguish different ways of viewing the internal temporal constituency of the same event [Comrie 1976: 3ff], after [Holt 1943: 6; Bybee 2003: 157]. The 'event' is understood here as a general term covering any situation type (a state, activity, accomplishment, achievement, etc.) as expressed by the verb phrase of the construction. Unlike Tense Feature, which expresses event-external time and is deictic, Aspect Feature is event-internal and non-deictic, as it is not concerned with relating the time of the event to any other time point. [Kibort 2008e]".
- BacknessProperty comment "A feature of vowel quality that correlates the difference between frequencies of formant two and formant one (overtones corresponding to a resonating frequency of the air in the vocal tract) [Ladefoged 2000: 215, 273]".
- BinaryPredicator comment "Binary predicates define relationships between keywords. Each binary predicate is viewed as function: given the value of the first argument, it returns the set of values for the second argument that would make the predicate true. [Feldman and Hirsh 1996: 344] BinaryPredicators are the class of syntactic words that require two arguments.".
- BoundMorpheme comment "A bound morpheme (or bound form) is one which cannot occur on its own as a separate word, e.g. various affixes de-, -tion, -ize. [Crystal 2003: 56]".
- BuccalProperty comment "A subclass of place properties roughly referring to positions inside the mouth [Ladefoged 1997: 606].".
- CaseProperty comment "CaseProperty is the class of properties that concerns the grammatical encoding of a noun's relationship (syntactic or semantic) to some other element in the sentence, such as a verb, noun, pronoun, or adposition [Pei and Gaynor 1954: 35; Crystal 1980: 53-54; Anderson 1985: 179-180; Andrews 1985: 7172; Kuno 1973: 45; Blake 2001].".
- CategoryChanger comment "CategoryChanger is a cover class for all derivational units that change the syntactic category of the root to which they are attached.".
- Character comment "A symbol used in writing, distinguished from others by its meaning, not its specific shape; similar to grapheme. It relates to the domain of orthographies and writing. Specific to the implementation of computers and other information systems. [Lyons, et al. 2001]".
- Classifier comment "In grammar, a morpheme whose function is to indicate the formal or semantic class to which items belong are sometimes called classifiers, e.g. -ly is an adverb classifier, -ess is a 'femininity' classifier. The marking of lexical items as belonging to the same semantic class is an important feature in many languages (e.g. Chinese, Vietnamese, Hopi), and sometimes quite unexpected bases of classification are found, in terms of shape, size, colour, movability, animacy, status and so on. [Crystal 2003: 74]".
- Clause comment "A clause is a subdivision of a sentence containing a subject (argument) and predicate. It is possible to have a word that implies or refers to a predicate rather than one explicitly stated. [Pei".
- Clitic 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].".
- ComplexSpecification comment "A ComplexSpecification is a kind of FeatureSpecification whose value must be a FeatureStructure. This class gives a feature system its recursive properites [Maxwell, Simons and Hayashi 2000].".
- Connective 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].".
- CoordinatingConnective comment "A coordinating connective is a connective that links constituents without syntactically subordinating one to the other [Crystal 1997: 93].".
- CoronalProperty comment "Properties of sounds produced with passive articulators either lying on the coronal axis, with the blade of the tongue raised from its neutral position, or in the neutral position (for non-coronal sounds). [Crystal 1980: 94]".
- DerivationalMorpheme comment "DerivationalUnit is the class of functional units whose members function to derive a new lexical unit from an existing one, by systematically changing the meaning and possibly altering the part of speech feature of the root or stem it attaches to [Hartmann and Stork 1972: 62; Crystal 1985: 89; Bybee 1985: 81-82, 99].".
- Determiner comment "A Determiner is a part of speech whose members belong to a class of noun modifiers and express the reference, including quantity, of a noun [Crystal 1997: 112].".
- DorsalProperty comment "The class of properties associated with sounds made with the body of the tongue [Ladefoged 1997: 601]. Almost all vowels can be described using subclasses of this property.".
- EvaluativeProperty comment "A term used in semantics for a type of modality where propositions express the speaker’s attitude (e.g. surprise, regret) towards what is being said. [Crystal 2003: 168]".
- EvidentialityProperty comment "Evidentiality denotes the basis that the speaker has for claiming that the event has occurred (or is going to take place). Appear to show a greater number of distinctions in the realis mood (especially in the past tense) than the irrealis mood. [Bhat 1999: 63-64, 70]".
- FeatureAssignmentSystem comment "(The term 'assignment') was first used with respect to feature values by Corbett (1991) in his discussion of mechanisms for allotting nouns to different genders. Native speakers have the ability to ‘work out’ the gender of a noun, and models of this ability have been called ‘gender assignment systems’. So far, the concept of ‘assignment of a feature value’ has not been used outside gender. For some features, there may not be as much to say as for gender. However, using the concept of ‘assignment’ with respect to the values of all features is useful to be able to compare the features. Therefore, for this typology I have adopted the following definition: an assignment system is a set of rules that realise the value of a feature on an element. Note, however, that under this definition, a gender value is ‘assigned’ both to nouns, and to targets of agreement in gender with the noun. [Kibort 2008d: 8]".
- FeatureConstraint comment "A term used in linguistics, and especially in generative grammar, to refer to a condition which restricts the application of a rule, to ensure that the sentences generated are well formed. For example, in generative phonology, a distinction can be made between ‘simulatenous’ and ‘sequential’ constraints: the former states the restrictions on the simulataneous occurrence of features, e.g. a segment cannot be at once [+high] and [+low]; the latter states the restrictions on sequences of features, e.g. whether a language permits consonant clusters. In generative syntax there are also several constraints which have to be imposed in order to prevent the derivation of ill formed phrase-markers, e.g. constraints on the ordering of rules. The notion of constraints takes on a different direction in optimality theory, where it is the principle explanatory device. Here, constraints are ways of characterizing language universals. Each language has its own ranking of constraints (e.g. which determine morpheme position or syllable structure), and differences between these rankings result in the variations observed between languages. [Crystal 2003: 101]".
- FeatureDistributionSystem comment "In a given language, the system according to which feature values (of a particular feature) are determined contextually for elements, through agreement or government. FeatureDistributionSystem can have one or two main components: FeatureAgreementSystem, and FeatureGovernmentSystem. [Kibort 2008d]".
- FeatureSpecification comment "A FeatureSpecification is a data structure that groups together a linguistic feature with a value [Maxwell, Simons and Hayashi 2000].".
- FeatureStructure comment "A FeatureStructure is a set of one or more FeatureSpecifications. A FeatureStructure is a kind of information structure, a container or data structure, used to group together 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 PartOfSpeech. [Shieber 1986; Maxwell, Simons and Hayashi 2000].".
- FeatureSystem comment "An utterance is divided into parts, which are assigned to word classes and then subclassified in terms of their \"accidents\" or properties. [Blevins 2006: 390] The properties, also referred to as features or categories, express what is shared by different linguistic elements, as opposed to what is idiosyncratic. [Kibort 2008d: 1]".
- ForceProperty comment "ForceProperty is the class of properties that concern the grammatical encoding of the speech act associated with a proposition. Among the traditionally defined values are Declarative, Imperative and Interrogative. Force is here distinguished from Mood, but there is a close association of Mood with Force values, e.g. between IndicativeMood and DeclarativeForce.".
- FormUnit comment "Denotes the sensorily perceptible aspect of the linguistic sign. [Bussmann 1996: 169]".
- Functor comment "Functor is the class of syntactic word whose members are neither relation- nor argument-like non-relational [Anderson 1997: 20]. Typical functors include adpositions, subordinators, and complementizers.".
- GenderProperty comment "GenderProperty is the class of properties that are assigned to nouns on the basis of their inherent properties by an AssignmentSystem and required by the syntax to appear on the target in an AgreementSystem. Gender may but need not be assigned on the basis of sex [Corbett 1991].".
- GeneticTaxon comment "GeneticTaxon is the class of all taxons whose members are based on genetic relatedness.".
- GlottalStrictureProperty comment "The three phonation types are part of the five possible values of Glottal Stricture that are used by languages. Sounds can have the vocal cords tightly together, as in a glottal stop, or they can be far apart as in voiceless sounds, or they can have one of the three phonation types: breathy voice, modal voice and creaky voice. Although some phoneticians have shown how terms similar to these may be combinable from the phonetic point of view, the named terms form a set of phonologically mutually exclusive possibilities. These factors point to there being an ordered set of five possibilities: [voiceless], [breathy], [modal voice], [creaky] and [closed]. It is certainly appropriate to consider these glottal states as resulting from two physiological attributes of the vocal cords, their stiffness and their aperture. However from a linguistic point of view, the named values of the feature Glottal Stricture operate as a linearly ordered set of five mutually exclusive possibilities. [Ladefoged 1997: 607-608]".
- GlottalTimingProperty comment "A phonation type containing the features 'aspirated' and 'unaspirated. Aspiration involves matters of relativing timing between laryngeal and oral articulations, and the wider opening can be viewed as an aspect of the control of this timing. There are two ways of interpreting this greather width; it can be seen as the essential aspect of the production of voiceless aspiration, that is, aspiration is an extra-wide opening of the vocal folds [Kim 1965], or it can be seen as a by-product of the mechanism by which a delay between the offset of the oral and glottal gestures is achieved, that is, aspiration is esentially a matter of the timing between speech movements controlling laryngeal setting and oral articulation [Goldstein and Browman 1986]. [Ladefoged and Maddieson 1996: 49-66; 372]".
- Glyph comment "A Glyph is a symbol used in a writing system to represent some kind of linguistic unit, such as a single sound, a phoneme or an entire word. Glyphs are concatenated in a writing system to form orthographic parts and orthographic words. Consider the printed word 'apple'. This word contains two instances of the 'p' glyph, which is a subclass of Glyph. Instances of a Glyph share a similar shape and can be called 'shapemes'. The class Glyph is not the same as Grapheme. A Grapheme is a contrastive unit within a particular writing system. The notion of a glyph is relevant across writing systems. For instance, consider the symbol 'р' used in a printed instance of a Russian word 'русский'. Now consider the symbol 'p' used in the printed instance of an English word 'pickle'. Both symbols are instances of the same Glyph. They share the same general shape, but do not have the same phonemic value.".
- Glyph comment "A shape that is the visual representation of a character. It is a graphic object stored within a font. Glyphs are objects that are recognizably related to particular characters and which are dependent on particular design. Glyphs may or may not correspond to characters in a one-to-one manner. For example, a single character may correspond to multiple glyphs that have complementary distributions based upon context (e.g. final and non-final sigma in Greek), or several characters may correspond to a single glyph known as a ligature. [Lyons, et al. 2001]".
- GrammarUnit comment "A GrammarUnit is the structural component of the linguistic sign and includes notions such as morpheme, syntactic word, and construction. Grammar units are classified according to their mereology (part-whole and complexity), morphosyntactic function, and whether they exist in a bound or free forms.".
- HeightProperty comment "The class of features describing sounds based on the relative vertical position of the tongue. Note, Ladefoged refers to this feature as High.".