Consider changing the name of "complex constraints"
Open, Needs TriagePublic
Actions

Assigned To

None

Authored By

	abian
	Feb 1 2020, 11:08 AM

Description

According to the 2020 report on Property constraints (T244043):

The so-called "complex constraints", which are based on templates, are not so distinguished by their complexity as by the need to specify them from scratch as SPARQL queries. The word "complex" has misleading connotations that may discourage work with these constraints. It is suggested to change the name of these template-based constraints to "custom", a name that is already used on some pages.

Related Objects

Mentioned Here: T244043: suggestions and possible decisions from the 2020 report on Property constraints

Event Timeline

abian created this task.Feb 1 2020, 11:08 AM

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptFeb 1 2020, 11:08 AM

Pasleim subscribed.Feb 1 2020, 3:23 PM

I think rethinking this name is good. I'm not sure custom is the best alternative. Custom to me is slightly problematic because in a sense all constraints are custom. Hmmmm.

Consider changing the name of "complex constraints"Open, Needs TriagePublicActions

Description

Related Objects

Event Timeline

Consider changing the name of "complex constraints"
Open, Needs TriagePublic
Actions