View source for Extension:WikibaseLexeme/Data Model

<languages/>
<div style="background: #FFC; padding: 1ex; border: #B00 solid 1px; ">
<translate><!--T:1--> This is a living document, describing the [[w:Conceptual schema|conceptual data model]] used by <tvar name=1>{{ll|Extension:WikibaseLexeme|WikibaseLexeme}}</tvar>.</translate>
<translate><!--T:84--> It is not a [[w:Specification_(technical_standard)|specification]] of any concrete [[w:Data binding|binding]], [[w:Implementation|implementation]], [[w:data mapping|mapping]], or [[w:serialization|serialization]].</translate>
</div>

<div style="float:{{dir|{{pagelang}}|left|right}}; clear:{{dir|{{pagelang}}|left|right}}; margin:{{dir|{{pagelang}}|1ex 1ex 1ex 0|1ex 0 1ex 1ex}}" class="toc">
* [[#Lexeme|Lexeme]]:
** [[#Lemma|Lemma]]
** [[#Language|Language]]
** [[#Lexical category|Lexical category]]
** [[Wikibase/DataModel#Statement|Statements]]
** [[#Form|Forms]]:
*** [[#Representation|Representation]]
*** [[#Grammatical Feature|Grammatical Features]]
*** [[Wikibase/DataModel#Statement|Statements]]
** [[#Sense|Senses]]:
*** [[#Gloss|Gloss]]
*** [[Wikibase/DataModel#Statement|Statements]]
</div>__NOTOC__

<translate><!--T:2--> The '''data model of <tvar name=1>{{ll|Extension:WikibaseLexeme|WikibaseLexeme}}</tvar>''' describes the structure of the data that is handled as "Lexemes" in Wikibase, such as words and phrases.</translate>
<translate><!--T:49--> While it would be theoretically possible to model these things using [[Wikibase/DataModel#Items|Items]], a more expressive specialized model helps to reduce complexity, and improve re-use and mappings to other vocabularies.</translate>
<translate><!--T:3--> This data model is conceptual ("Which information do we have to support?") and does not specify how this data should be represented technically ("Which data structures should the software use?") or syntactically ("How should the data be expressed in a file?").</translate>
<translate><!--T:50--> Separate documents describe the serialization of the Wikibase [[w:data model|data model]] in [[<tvar name=1>Special:MyLanguage/Extension:WikibaseLexeme/JSON</tvar>|JSON]] ([[w:JSON|JavaScript Object Notation]]) and in [[<tvar name=2>Special:MyLanguage/Extension:WikibaseLexeme/RDF mapping</tvar>|RDF]] ([[w:Resource Description Framework|Resource Description Framework]]).</translate>
<translate><!--T:4--> The Lexeme data model defines basic concepts and relationships needed to describe [[wikipedia:Lexeme|lexemes]], which act as a fixed [[w:Ontology_(information_science)|ontology]].</translate>
<translate><!--T:51--> This ontology provides a minimal scaffolding that allows [[Wikibase/DataModel#Item|Items]] and [[Wikibase/DataModel#Statement|Statements]] to be used for detailed [[W:Scientific modelling|modeling]] of a lexeme.</translate>
<translate><!--T:5--> The specification of the Lexeme data model is based on the [[Wikibase/DataModel|Wikibase data model]], so the [[d:Wikidata:Glossary|Wikidata glossary]] and the [[Wikibase/DataModel/Primer|Wikibase data model primer]] may be helpful in understanding this document.</translate>
<translate><!--T:52--> The Lexeme data model aims to align with the [https://www.w3.org/2016/05/ontolex/ LEMON model] by the [https://www.w3.org/community/ontolex/ Ontolex] W3C community group, where useful and practical.</translate>
<translate><!--T:53--> However, in the spirit of Wikibase, the Lexeme model is designed to be simple and flexible enough for casual collaborative editing, as opposed to the more formalized approach taken by LEMON.</translate>

<translate>
== Lexeme == <!--T:6-->
</translate>

<div style="float:{{dir|{{pagelang}}|left|right}}; clear:{{dir|{{pagelang}}|left|right}}">
<translate><!--T:45--> [[File:Lexeme data model.svg|thumb|400px|visualization of the Lexeme data model]]</translate>
</div>

<translate><!--T:7--> A Lexeme is a lexical element of a language, such as a word, a phrase, or a prefix (see ''[[wikipedia:Lexeme|Lexeme]]'' on Wikipedia). Lexemes are [[Wikibase/DataModel#Entities|Entities]] in the sense of the Wikibase data model.</translate>
<translate><!--T:8--> A Lexeme is described using the following information:</translate>

<translate>
<!--T:9-->
* An '''ID'''. Lexemes have IDs starting with an "L" followed by a natural number in decimal notation, e.g. <code>L3746552</code>. These IDs are unique within the repository that manages the Lexeme. The ID can be combined with a repository's concept base URI to form a unique URI for the Lexeme.</translate>
<translate>
<!--T:60-->
* A '''[[#Lemma|Lemma]]''' for use as a human readable representation of the lexeme, e.g. ''"run"''.
</translate>
* {{anchor|Language}}<translate><!--T:61--> The '''Language''' to which the lexeme belongs. This is a reference to a concrete [[Wikibase/DataModel#Item|Item]], e.g. [[d:Q1860|Q1860]] for ''English''.</translate>
* {{anchor|Lexical category}}<translate><!--T:62--> The '''Lexical category''' to which the lexeme belongs. This is given as a reference to a concrete [[Wikibase/DataModel#Item|Item]], e.g. [[d:Q34698|Q34698]] for ''adjective''.</translate>
<translate>
<!--T:63-->
* A list of [[Wikibase/DataModel#Statement|Statements]] to describe properties of the lexeme that are not specific to a Form or Sense (e.g. ''derived from'' or ''grammatical gender'' or ''syntactic function'').</translate>
<translate>
<!--T:65-->
* A list of [[#Form|Forms]], typically one for each relevant combination of grammatical features, such as ''2nd person / singular / past tense''.</translate>
<translate>
<!--T:66-->
* A list of [[#Sense|Senses]], describing the different meanings of the lexeme (e.g. "financial institution" and "edge of a body of water" for the English noun ''bank'').
</translate>
<hr style="visibility:hidden; clear:both;"/>
{{:Wikibase/DataModel/Editorial Note|1=<translate><!--T:10--> We should provide some hint regarding how grammatical gender can be modeled using Statements.</translate>}}

<translate>
=== Lexeme statements === <!--T:75-->

==== Instance of ==== <!--T:76-->

<!--T:64-->
In Wikidata they generally use the most general lexical category possible, e.g. ''affix'' and then instead describe which type of affix it is using an ''instance of''-statement.

==== Usage examples ==== <!--T:77-->
</translate>
<translate><!--T:78--> In Wikidata the community decided to have usage examples in one place on the lexeme because then they know where to look for them.</translate>
<translate><!--T:79--> They have to demonstrate two properties: form (<tvar name=1>[[d:Property:P5830]]</tvar>) and sense (<tvar name=2>[[d:Property:P6072]]</tvar>).</translate>
<translate><!--T:80--> They can have multiple examples from different time periods e.g. different centuries and for formality/informality and written/spoken.</translate>

<translate>
=== Lemma === <!--T:11-->
</translate>
<translate><!--T:12--> The lemma is a human readable representation of the lexeme (see ''[[wikipedia:Lemma_(morphology)|Lemma]]'' on Wikipedia). Typically, the canonical form of the lexeme (e.g. the infinitive form of verbs) will be used as the lemma (see also [https://www.w3.org/2016/05/ontolex/#canonicalForm lemon:canonicalForm]).</translate>
<translate><!--T:13--> Lemmas are not simple strings, but [[Wikibase/DataModel#MultilingualTextValues|MultilingualTextValues]], since the same lemma may have multiple spellings. This is specially important for languages that use multiple scripts such as Serbian and Japanese.</translate>

{{:Wikibase/DataModel/Example|<translate><!--T:14--> The Lemma for English noun ''color'' would include "colour" for British English as well as "color" for American English.</translate>}}

<translate>
<!--T:15-->
A Lemma cannot be entirely empty, at least one variant has to be provided.

<!--T:16-->
Note: Lemmas are not unique, nor is the combination of Lemma, Language, and Lexical category. Two distinct lexemes with the same lexical category can exist in the same language if they have different data, it may be gender, etymology, morphology (different forms), and so on.
</translate>

{{:Wikibase/DataModel/Example|<translate><!--T:17--> There are two German nouns with the Lemma "See", differing only in [[w:Grammatical_gender|gender]]: "der See" meaning "the lake", and "die See" meaning "the sea". These two meanings cannot be understood as a single Lexeme, since they have different forms according to their gender.</translate> An example where there would only be one Lexeme would be the German word "Schild", which for its meaning "Shield" can be either masculine or neutral gendered based on the region in Germany (neutral in the north and parts of central Germany).}}

<translate>
== Form == <!--T:18-->

<!--T:19-->
The [[w:Morphology_(linguistics)#Lexeme-based_morphology|morphology]] of the lexeme is understood as a set of Forms. Each form defines how a lexeme changes based on a specific ''syntactic role'' or ''mode'' it may take in a sentence (see also [https://www.w3.org/2016/05/ontolex/#Form lemon:Form]).
</translate>

{{:Wikibase/DataModel/Example|<translate><!--T:20--> The English verb ''run'' becomes "running" as a ''present participle'' and "runs" in ''3rd person singular''.</translate>}}

<translate>
<!--T:21-->
A Form is described using the following information:

<!--T:22-->
* An '''ID'''. Forms have IDs starting with the ID of the Lexeme they belong to, followed by a hyphen ("-") and an "F", followed by a natural number in decimal notation: e.g. <code>L3746552-F7</code>. These IDs are unique within the repository that manages the Lexeme. The ID can be combined with a repository's concept base URI to form a unique URI for the Form.</translate>
<translate>
<!--T:81-->
* A '''[[#Representation|representation]]''', spelling out the Form as a string.</translate>
<translate>
<!--T:82-->
* A list of '''[[#Grammatical Feature|grammatical features]]''' that define for which syntactic role the given form applies. These are given as references to a concrete [[Wikibase/DataModel#Item|Items]], e.g. [[d:Q814722|Q814722]] for ''participle''.</translate>
<translate>
<!--T:83-->
* A list of [[Wikibase/DataModel#Statement|Statements]] further describing the Form or its relations to other Forms or Items (e.g. ''pronunciation audio'', ''rhymes with'', ''used until'', ''used in region'')
</translate>

{{:Wikibase/DataModel/Future|<translate><!--T:46--> We may add the notion of a "form type" that determine what information a Form contains.</translate> <translate><!--T:47--> One possible new type could be "nonexistent", which would allow to to represent forms that are known to not exist (like the infinitive of English "may", or the plural of German "Schnee").</translate> <translate><!--T:48--> Forms of the "nonexistent" kinds would have statements and grammatical features, but no representations.</translate>}}

<translate>
=== Representation === <!--T:23-->

<!--T:24-->
A form's Representation is its written form, as used in a text (compare [https://www.w3.org/2016/05/ontolex/#writtenRep lemon:writtenRep]). Just like [[#Lemma|Lemmas]], Representations are not simple strings, but [[Wikibase/DataModel#MultilingualTextValues|MultilingualTextValues]], since the same form may have multiple spellings, possibly in multiple scripts.

<!--T:25-->
A Representation cannot be entirely empty, at least one variant has to be provided.
</translate>

<translate><!--T:57--> Multiple forms with the same representation are allowed to enable adding usage examples demonstrating each of them.</translate>
<translate><!--T:67--> [https://www.wikidata.org/wiki/Lexeme:L352 Example in Wikidata]</translate>

<translate>
=== Grammatical Feature === <!--T:26-->
</translate>
<translate><!--T:27--> A form's grammatical features specify under which conditions or in which syntactic role that form is used (see [http://lexinfo.net/ontology/2.0/lexinfo.owl#morphosyntacticProperty lexinfo:morphosyntacticProperty] and [[w:Grammatical_category|grammatical category]] on Wikipedia).</translate>
<translate><!--T:58--> Multiple grammatical features can be combined to express under which conditions the language's grammar requires a given form to be used. Grammatical features are represented as references to [[Wikibase/DataModel#Items|Items]].</translate>

{{:Wikibase/DataModel/Example|<translate><!--T:28--> The role ''1st person present tense plural'' can be defined by three features, represented by Wikidata Items: [[d:Q192613|Q192613]] (present tense), [[d:Q21714344|Q21714344]] (first person), and [[d:Q146786|Q146786]] (plural).</translate> }}

{{:Wikibase/DataModel/Editorial Note|1=<translate><!--T:29--> How do we model "a" vs "an"? What item would we use as a feature to describe this? Do we need free text usage notes after all?</translate>}}
{{:Wikibase/DataModel/Editorial Note|1=<translate><!--T:30--> We should note that gender-specific forms like "baroness" can be treated as Forms, or as separate Lexemes, as need be.</translate>}}

<translate>
== Sense == <!--T:31-->

<!--T:32-->
The senses of a lexeme are different meanings which it may represent in a text. The senses are given as natural language definitions or ''glosses'' (compare ''[[w:Extensional_and_intensional_definitions|intensional definitions]]'' on Wikipedia).

<!--T:33-->
A sense is described using the following information:

<!--T:68-->
* An '''ID'''. Senses have IDs starting with the ID of the Lexeme they belong to, followed by a hyphen ("-") and an "S", followed by a natural number in decimal notation: e.g. <code>L3746552-S4</code>. These IDs are unique within the repository that manages the Lexeme. The ID can be combined with a repository's concept base URI to form a unique URI for the Sense.</translate>
<translate>
<!--T:69-->
* A '''Gloss''', defining the meaning of the Sense using natural language.</translate>
<translate>
<!--T:70-->
* A list of [[Wikibase/DataModel#Statement|Statements]] further describing the Sense and its relations to Senses and Items (e.g. ''item for this sense'', ''synonym'', ''antonym'', ''connotation'', ''register'', ''denotes'', ''evokes'').</translate> <translate><!--T:71--> In Wikidata ''image'' is also added to provide a culturally adapted image of the sense, e.g. of a letterbox or color that can vary greatly between cultures.</translate>

{{:Wikibase/DataModel/Editorial Note|1=<translate><!--T:34--> We should find a good place to address a common source of misunderstandings: Senses can be connected to Wikidata Items via an appropriate Statement they evoke or denote (compare [https://www.w3.org/2016/05/ontolex/#denotes lemon:denotes] and [https://www.w3.org/2016/05/ontolex/#evokes lemon:evokes]). However, such a connection should not be interpreted as the lexeme actually representing the concept defined by the item (compare [https://www.w3.org/2016/05/ontolex/#LexicalSense lemon:LexicalSense] and [https://www.w3.org/2016/05/ontolex/#LexicalConcept lemon:LexicalConcept]).</translate> <translate><!--T:59--> In particular, if two lexemes have senses that refer to the same concept in this way, this does not imply that the two lexemes are synonyms.</translate>

<translate>
<!--T:35-->
Example: The lexemes for the English adjectives "hot" and "cold" could both have a sense that refers to [[d:Q11466|Q11466]] (temperature), even though they are antonyms.
</translate>
}}

{{:Wikibase/DataModel/Editorial Note|1=<translate><!--T:36--> We should describe how word ''function'' can be described for things like "to" or "a", using Statements on the Lexeme. We should also explain that function words should not have senses. Do we need free text usage notes?</translate>}}

{{:Wikibase/DataModel/Future|<translate><!--T:37--> We may introduce a field in the Sense for syntactic markers and/or syntactic frames for [[:en:Subcategorization|subcategorization]] (see also [http://www.unlweb.net/wiki/Subcategorization_frames the definition] on the UNL wiki). That would allow "ask for", "ask about", "ask to", "ask out", "ask oneself", etc. to be modeled as sense of the same lexeme, each with a different subcategorization. Some verbs also change the meaning depending on whether they are used reflexively (e.g. German "übernehmen" vs "sich übernehmen"). Compare [https://www.w3.org/2016/05/ontolex/#marker synsem:marker] and [https://www.w3.org/2016/05/ontolex/#syntactic-frames synsem:syntactic-frame].</translate>}}

<translate>
=== Gloss === <!--T:38-->

<!--T:39-->
A sense's gloss gives a natural definition of the sense (see ''[[w:Gloss_(annotation)|Gloss]]'' on Wikipedia and [https://www.w3.org/2009/08/skos-reference/skos.html#definition skos:definition]). Glosses cannot be referenced.
</translate>

<translate><!--T:54--> Similar to [[#Lemma|Lemmas]], Glosses are not simple strings, but [[Wikibase/DataModel#MultilingualTextValues|MultilingualTextValues]].</translate>
<translate><!--T:55--> However, the reason is not providing support for variants, but to allow the gloss to be given in entirely different languages.</translate>
<translate><!--T:56--> E.g. it would be quite useful for a German learning French to have a German gloss for a French sense.</translate>

<translate>
<!--T:40-->
A Gloss cannot be entirely empty, at least one language has to be provided. A good gloss provides little or no space for ambiguity about the meaning. Lexemes with multiple senses should have glosses that are easily distinguishable from each other.

<!--T:72-->
Short glosses of only a single or a few words should be avoided as it leaves too much space for interpretation of the meaning.
</translate>

<translate><!--T:73--> In Wikidata Glosses are often very similar to carefully crafted descriptions on Q-items.</translate>
<translate><!--T:74--> E.g. for apple the Q-items English description ''fruit of the apple tree'' is copied as gloss when using tools like [[<tvar name=1>d:Wikidata:Tools/Lexicographical data</tvar>|MachtSinn]] to match lexemes and Q-items together and create missing senses.</translate>

<translate>
== See also == <!--T:44-->
</translate>
* [[d:Wikidata:Wiktionary/Data model examples|<translate><!--T:43--> Lexeme data model examples</translate>]]