WikibaseLexeme
MediaWiki WikibaseLexeme extension
|
This document describes the canonical JSON format used to represent WikibaseLexeme entities in the API, in JSON dumps, as well as by Special:EntityData (when using JSON output). This format can be expected to be reasonably stable, and is designed with flexibility and robustness in mind.
Lexemes are Wikibase entities. While they do not have labels, descriptions, aliases, sitelinks, or a datatype, they do share all the other characteristics of Wikibase entities. For those please see the Wikibase JSON documentation.
In particular, Lexemes have the same structure for Statements as other entities, see the respective section about Statements in the above documentation.
A Lexeme can have one or multiple lemmas, at most one for each language(-variant).
For each language variant, there is a record using the following fields:
Lemmas have the same basic structure as labels, descriptions, and aliases in the Wikibase JSON.
The language and lexical category of a Lexeme are represented by their respective Item IDs.
Forms and Senses are "subentities" of a Lexeme. They can have their own set of statements, but each also have some extra keys that are specific to them.
Each Form has a unique id
. That id consists of two parts, separated by a dash: the Lexeme id, and the number of the Form.
Also, a Form is associated with a set of one or more grammatical features, which are listed by their respective Item IDs.
Finally, a form has one or more representations, which are structured the same way as lemmas: objects, indexed by language code, with the following fields:
As mentioned above, Forms also can have statements in the usual structure under the claims
key.
Each Sense has a unique id
. That id consists of two parts, separated by a dash: the Lexeme id, and the number of the Sense.
A Sense has one or more glosses associated with it, which are structured the same way as lemmas: objects, indexed by language code, with the following fields:
As mentioned above, Senses also can have statements in the usual structure under the claims
key.