Search translations

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

Properties with constraint "$1" need a parameter "$2".

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

Properties with constraint "$1" need parameters "$2", "$3", and "$4".

Checks the constraint parameters of constraint statements.

The constraint is not implemented.

Properties with constraint "$1" need to have values of type "$2".

The statement satisfies the constraint.

The statement violates the constraint.

Properties with values of type "$1" with constraint "$4" need the parameters "$2" and "$3".

go to constraint

The constraint parameters are broken.

Properties with constraint "$1" need to have values of type "$2" or "$3".

Constraint report

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

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 constraint has not been checked because the statement is deprecated.

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

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.

This is the $1 category.

Check one particular constraint on the item Q2.

The title of the article is mandatory.

$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}}

Enter all the data here to create the properties, template, form and category for a single class. For more options, use the pages $1 instead.