Sense

Validate against: http://json-schema.org/schema#

Description

A sense is one of the possible meanings of a lexeme. For example, the lexeme run has many different senses, such as as "run in a race" and "run water in a sink". It is up to the linguist to decide whether two particular uses of a lexeme count as the same sense or different senses.

Type: object

Required Properties

  • gloss

Additional properties: true

Dependencies

  • If the property variantType is present, the following properties must also be present:

    • variantOf

Properties

  • Argument Structure: "argumentStructure"

    Description

    An abstract representation of the argument structure for this sense

    Type: string

  • Lexical Category (Part of Speech, Morphosyntactic Class, etc.): "category"

    Description

    The lexical category, part of speech, or morphosyntactic class for this Lexeme, optionally in multiple languages. If the current lexeme is an affix or other grammatical morpheme morpheme, this field should be used to describe the category that the morpheme attaches to. For example, the English verb suffix ‑s would have this this property set to verb, and the English derivational suffix ‑ize would have this property set to noun.

    Must be an instance of the MultiLangString schema.

  • Definition: "definition"

    Description

    The definition for this particular sense, optionally in multiple languages

    Must be an instance of the MultiLangString schema.

  • Derived Category: "derives"

    Description

    If this lexeme is a derivational morpheme, this field indicates the type of lexical category, part of speech, or morphosyntactic class that is derived when this morpheme is applied. For example, the English derivational suffix ‑er would have this property set to noun, since this suffix derives nouns from verbs. May be in multiple languages.

    Must be an instance of the MultiLangString schema.

  • Examples: "examples"

    Description

    A collection of examples illustrating this sense in use. Each example is an Utterance from a Text. The Utterance number should be indicated in the index field of the Database Reference object. If using a full Utterance object rather than a Database Reference object, the key field should be included. For precision's sake, it is recommended that examples be given for individual senses rather than the entire lexeme when possible.

    Type: array

    Unique items: true

    Items

    Example Utterance (Database Reference)

    Description

    A database reference to an Utterance object

    Must be an instance of the DatabaseReference schema.

  • Gloss: "gloss"

    Description

    A Leipzig-style gloss for this sense. A gloss must be provided in at least one language.

    Must be an instance of the MultiLangString schema.

  • Lexical Relations: "lexicalRelations"

    Description

    A list of the lexical relations that this sense has to other senses of different lexemes. Each item is a Database Reference, and must also have a property called relation, indicating the type of lexical relation. For precision's sake, lexical relations should be specified for individual senses rather than the entire lexeme whenever possible.

    Type: array

    Unique items: true

    Items

    Validates Against (allOf)

    This schema must validate against all of the following schemas:

    • Lexeme (Database Reference)

      Description

      A database reference representing a lexical relation between two senses. Note: The database reference must also have a relation property specified, indicating the type of lexical relation.

      Must be an instance of the schema.

    • Required Properties

      • relation

      Properties

      • Relation Type

        Description

        The type of lexical relation that holds between the current sense and the referenced sense. Can also be used for general cross-references (a compare relation) or historical relationships (a derivedFrom or originOf relation). Examples: antonym, synonym, cognate, derivedFrom, originOf, compare, partOf, hypernymOf, hyponymOf.

        Must be an instance of the schema.

  • Link: "link"

    Description

    A URL where a presentational format for this sense may be viewed

    Type: string

    Format: uri

  • Media: "media"

    Description

    Media items associated with this sense, such as pictures of the item this word refers to, or videos of the action being performed. When a media item pertains to a specific sense, it should be placed in that sense's media field rather than the lexeme's.

    Type: array

    Unique items: true

    Items

    Media Item (Database Reference)

    Description

    A database reference to a media item associated with this sense

    Must be an instance of the DatabaseReference schema.

  • Notes: "notes"

    Description

    A collection of notes about this sense. Each Note object must have its noteType property specified. Notes with a note type of private are not intended for publication in dictionaries, while other types of notes are. For precision's sake, it is recommended that notes be attached to specific senses instead of the lexeme whenever possible.

    Type: array

    Unique items: true

    Items

    Validates Against (allOf)

    This schema must validate against all of the following schemas:

    • Note

      Description

      A note about this sense

      Must be an instance of the schema.

    • Required Properties

      • noteType

      Properties

      • Note Type

        Description

        The type of note about this sense

        Type: string

        Allowed Values (enum)

        • private
        • general
        • anthropology
        • discourse
        • encyclopedic
        • grammar
        • phonology
        • semantics
        • sociocultural
  • Bibliographic References: "references"

    Description

    A collection of bibliographic references relating to this sense. For example, a particular sense may have been discussed in detail in a published article.

    Type: array

    Unique items: true

    Items

    Reference

    Description

    A bibliographic Reference about this sense

    Must be an instance of the BibliographicReference schema.

  • Scientific Name: "scientificName"

    Description

    The scientific name for this item

    Type: string

  • Sources: "sources"

    Description

    A list of attested sources for this sense, such as a citation to a published text where it appears, the key of an Utterance in the database, or the initials of the speaker who provided it. For precision's sake, sources should be listed for specific senses of a lexeme rather than the lexeme whenever possible.

    Type: array

    Unique items: true

    Items

    Source

    Description

    An attested source for this sense. This will often be the initials of a speaker, but could also be the abbreviation of the story the sense was found it, or a citation to a published text in which the sense appears.

    Type: string

    Min length: 1

  • Tags: "tags"

    Description

    A set of tags for this sense

    Must be an instance of the Tags schema.

  • Usages: "usages"

    Description

    A list of the appropriate usages for this sense. Examples include formal, medicinal, informal, etc.

    Type: array

    Unique items: true

    Items

    Usage

    Description

    An appropriate usage for this sense, optionally in multiple languages

    Must be an instance of the MultiLangString schema.

  • Variant Of: "variantOf"

    Description

    If this sense is a variant of another sense, a reference to the other sense should go here. For example, sometimes two speakers may use the same word with a slightly different set of senses. In American English, for instance, Coke is a specific brand of soda for most speakers, but a generic term for soda for other speakers. The generic sense would therefore be listed as a dialectal variant of the specific sense.

    Must be an instance of the DatabaseReference schema.

  • Variants: "variants"

    Description

    A list of variations of this this sense. This field should be used for dialectal and idiolectal variants, register-based variants, variations in meaning, spelling variants, etc. Each variant should have its variantType property specified.

    Type: array

    Unique items: true

    Items

    Validates Against (allOf)

    This schema must validate against all of the following schemas:

    • Variant (Database Reference)

      Description

      A database reference to a variant of this sense. Note: The Database Reference object must have a variantType property, indicating the type of variant.

      Must be an instance of the schema.

    • Required Properties

      • variantType

      Properties

      • Variant Type

        Description

        This field is be used to specify the type of variant. Possible values might be a person’s name (representing an idiolectal variant), or simply idiolectal, or dialectal (or the name of the dialect), etc. May be in multiple languages.

        Must be an instance of the schema.

  • Variant Type: "variantType"

    Description

    If this sense is a variant of another sense, this field can be used to specify the type of variant. Possible values might be a person’s name (representing an idiolectal variant), or simply idiolectal, or dialectal (or the name of the dialect), etc. May be in multiple languages.

    Must be an instance of the MultiLangString schema.