Dependency Syntax and Universal Dependencies › Limitations and Impact

A dependency annotation is a linguistic analysis. The same sentence may support more than one reading, and guidelines must choose how to encode coordination, ellipsis, names, and other difficult constructions. A common inventory fixes the available relation names, but it does not remove ambiguity. Annotation disagreement is also not a hard mathematical ceiling on a parser's agreement with a particular reference: human-human agreement and system-reference agreement measure different comparisons.

Cross-linguistic consistency has limits. A shared nsubj label does not imply identical case systems, word orders, or subject diagnostics. A model transferred between languages must still handle those differences, and treebanks can differ in genre, size, and annotation coverage. A quantitative transfer claim needs a specific model, dataset release, split, and evaluation protocol. The small examples here establish none of those empirical performance claims.

Non-projectivity is a representational limitation for any parser restricted to projective trees. Its practical importance must be measured on the intended data with a stated denominator. Structural validation helps isolate that limitation, but it cannot decide whether a linguistically plausible attachment is correct. Both trees for the telescope ambiguity can satisfy the same graph constraints.

The basic tree also leaves some interpretation links implicit. Enhanced dependencies provide another layer for shared arguments, relative-clause relations, and ellipsis, but they are optional and need their own graph handling. A program that assumes every DEPS record has one head will lose precisely the information that enhancement was designed to add.

UD's practical contribution is a shared annotation framework and data format. Dependency paths can support language analysis and downstream tasks such as relation extraction, while explicit heads and labels make a system's syntactic assumptions inspectable. Their usefulness is task-dependent: an application may require phrase boundaries, semantic roles, or discourse information beyond the basic dependency tree. Keeping those boundaries clear is part of using syntax responsibly.