Search translations

A <code>unique_value_constraint</code> constraint is assigend to the the "[[Property:$1|$1]]" property hereby only permits unique value annotations, ''$2'' already contains an annotated value with "$3" violating the uniqueness constraint for the current subject.

The statement violates the constraint, but the constraint is just a suggestion.

The statement violates the constraint, but the constraint is not mandatory.

A <code>unique_value_constraint</code> constraint is assigend to the the "[[Property:$1|$1]]" property which only permits unique value assignments and the ''$2'' value annotation was already found to be annotated in the "$3" subject.

The constraint is not implemented.

Checks the constraint parameters of constraint statements.

The property <code>$1</code> is not set.

The statement satisfies the constraint.

The statement violates the constraint.

The subject entity of the statement is a known exception to the constraint.

The constraint parameters are broken.

The constraint has not been checked because the statement is deprecated.

The value for the parameter "$1" must be a property, not "$2".

go to constraint

The constraint is not checked on this kind of snak (main snak, qualifier or reference), so the constraint check is skipped.

These issues are problems with the constraint definition on the property, not with this statement.

Check constraint parameters of all constraints on a property.

The property <code>$1</code> must be of type <code>$2</code> instead of <code>$3</code>.

Constraint report

Unexpected conflict between the Property type "$2" and the value type "$1".

The property defined in the parameters must have a value of the same type as this property.

<code>$1</code> is not a supported value of the <code>$2</code>. The possible values are: $3.

$1 is not a valid scope for the constraint type $2; the only valid {{PLURAL:$3|scope|scopes}} for this constraint type {{PLURAL:$3|is $5.|2=are $5 and $6.|are: $4}}

The property name argument is missing.