Extension:WikibaseLexeme/RDF mapping

This is the specification of the RDF mapping of the Wikibase Lexeme data model. It is based on the Wikibase RDF dump format. If not stated otherwise the prefixes are defined by this document. When relevant it reuses the LEMON model by the Ontolex W3C community group.

Lexeme
Example:

Comments:


 * Classes
 * The lexeme concept of Wikibase aligns well with . A class  is also used for consistency with   and.


 * Lemma
 * We use the custom property . The closest lemon relation is  but its range is . Using   has instead of the generic   just like item (and maybe also   and ) has the advantage of not having lexemes appearing in existing SPARQL queries that are using   and allows to easily query only lexemes by label with just one triple pattern.


 * Language
 * We use the the Dublin Core  property just like lemon examples. We are not reusing directly  because it is already used for Wikibase sitelinks representation with a BCP 47 language code range. It is planned but not implemented yet to emit this   property as a derived value with as value the BCP 47 language code of the language when it exists.


 * Lexical category
 * We use our own  property in order to avoid a slight abuse of the   from the lexinfo lemon extension that is restricted to parts of speech.


 * Statements
 * For consistency and simplicity we use the same schema as for items and properties.


 * Forms
 * The relation between Lexemes and Forms uses the relation. See the Form section for forms representation.


 * Senses
 * The relation between Lexemes and Forms uses the relation.  See the Sense section for forms representation.

Form
Possible example:

Comments:


 * Classes
 * The form concept of Wikibase aligns with . The additional class  is also used.


 * Representation
 * We use the relation from lemon. We do not use its sub property  in order to not forbid representations in phonetic variants of languages even if the lemon specification recommends to not use  directly.  is also emitted for interoperability reasons.


 * Grammatical Features
 * We use a custom property  because there is no such relation in lemon with  for domain.


 * Statements
 * For consistency and simplicity we use the same schema as for items and properties.

Sense
Possible example:

Comments:


 * Classes
 * The sense concept of Wikibase aligns with . The additional class  is also used.


 * Gloss
 * We use to provide gloss following Lemon usage.   is also emitted for interoperability reasons even if a gloss is not really a label.


 * Statements
 * For consistency and simplicity we use the same schema as for items and properties.

Data node
Example:

For each Lexeme a data node should be returned with the URI  if the Lexeme is. It should use the same schema as for Wikibase items and properties data node. It could also provide some statistics based on page properties just like items.

Note: There is no specific data node for forms and senses because the granularity of data nodes is the data container (wiki page). It is not a strong limitation because it is easy to retrieve the data node of the Lexeme they belong to with the property path  or.

Wikidata Query Service
Wikidata Query Service does not provide the following features (mostly for performance reasons):
 * The,   and   classes.
 * The  relations (more specific equivalents exists for lexemes, forms and senses).
 * Just as for items and properties, the data node is integrated within the  node.

Related work

 * the Wiktionary version of DBpedia