Mova0.5 pre-release⌕
☰
home / docs / dialects / mova — Mova's dialect

mova — Mova's dialect

Mova has its own dialect based on the latest UD at any given time — so future 2.19 changes can already be used — and also based on alternative UD dialects, whose changes are pulled into the dialect when they are judged good.

What mova is (details in The Mova dialect: a UD metadialect, treebanks, and converters):

This folder holds the decisions on ud-next changes and on discrepancies between the 2.18 guidelines and the EWT data, each as a separate seed in seeds/. Decided 2026-09-26: every proposal in the table is taken as proposed. Accepted: 11; "wait" — watched until the 2.19 data (freeze 01.11.2026); "do not accept" — no. Principle: changes from other dialects are pulled into this one when they are judged good.

Decisions

topicorigindecisionwhy, brieflyeffect on export
wh-caseud-next, _en/pos/PRON.mdacceptcase shows the role of who in the clause; lemma who — as in GUM, GENTLE, LinES, ParTUTin 2.18 — drop Case, lemma from form; identity on EWT
discourse-adverbsud-next _u-dep/discourse.md; 2.18 discrepancyacceptthe boundary is by word class; 2.18 already excluded ADV9 EWT tokens (GUM — 78) will diverge from gold, but not from the guideline
features-contextud-next, changes.md No. 18accept the principle; wait on ExponenceEWT already does this; form wins over semantic agreement; Exponence values do not exist yetno change
xpos-not-emptyud-next, validator 0.2.8acceptotherwise a 2.19 validator errorwriter gate
feat-layer-idsud-next, feat-layers.mdaccepta layer is only [a-z]+does not apply to en
spoken-subtypesud-next, fr; #1290waitno universal decision and no English gold datathe subtype is dropped without loss
no-effectud-next: expl:*, validator data, tools, treebank list, other languages; 2.18: v1 labelsaccept as is / not applicable; do not take uposf→xpos into the pipelineno effect on English annotation—
iobj-sole2.18 discrepancyaccept the 2.12 amendment, as EWT doesiobj with ask/tell/allow X to is more informative than obj; the lexicon decides the boundaryidentity
to-phrase-obl2.18 discrepancyaccept obl1285 : 0 in EWT; nmod in the text is a v1 leftoveridentity
imperative-do2.18 discrepancyaccept the EWT custom (Imp|Fin)the same for Go! and Don't go!; 98 of 1068 EWT exceptions will diverge; the letter of VerbForm.md is derived deterministically
subjunctive2.18 discrepancyaccept Mood=Suba clause feature; 57 in EWT, present in GUM and ParTUTidentity; the letter of Mood.md is derived deterministically
modal-mood2.18 discrepancy; #1118waitMood=Pot/Nec is outside the en registry; no decisionno change
depictives2.18 discrepancyaccept advclone answer instead of three; 22 in EWTidentity
clausal-predicate2.18 discrepancyaccept nsubj:outer257 in EWT, 0 of the old analysisidentity

Summary:

Only 3 proposals change mova annotation compared with EWT 2.18:

The rest confirm that mova follows the EWT data where the _en text is out of date.

Rules for the first two are in Converter mova ⇄ ud-next. They were run with the en convert engine on EWT 2.18: the forward one changes 469 words, the reverse one restores everything except 9 discourse. The rule for the third is in Main verb with imperative do — Mood=Imp|VerbForm=Fin — proposal, for EWT ↔ mova — converter; the engine changes exactly 8 words with it.

Outside the decisions, under watch. #1176: dependents of a nominalized adjective are nmod, not obl. The Core Group decision has been declared but not yet written into the guidelines. In EWT 2.18, ADJ in nominal position has nmod 83 times and obl 53. When it lands in docs/, it will be one more ud-next change with a simple rule obl → nmod. Other open discussions are in ud-next — changes after UD 2.18 that will go into 2.19.

This page in Markdown → https://md.mova.elamur.ai/free/en/docs/dialects/mova/