Range from “15” to “40”: values should be in the range from “15” to “40”. (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P2998#Range

Range from “0” to “100”: values should be in the range from “0” to “100”. (Help)

List of violations of this constraint: Database reports/Constraint violations/P2998#Range, hourly updated report

Units: “years old (Q24564698)”: value unit must be one of listed. (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P2998#Units

Scope is as main value (Q54828448): the property must be used by specified way only (Help)

List of violations of this constraint: Database reports/Constraint violations/P2998#Scope, hourly updated report, SPARQL

Type “geographic region (Q82794), position (Q4164871), public election (Q40231)”: item must contain property “instance of (P31)” with classes “geographic region (Q82794), position (Q4164871), public election (Q40231)” or their subclasses (defined using subclass of (P279)). (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P2998#Type Q82794, Q4164871, Q40231, SPARQL

Citation needed: the property must have at least one reference (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P2998#citation needed

Allowed entity types are Wikibase item (Q29934200): the property may only be used on a certain entity type (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P2998#Entity types

Integer: values should be integers (ie. they shouldn't have a fractional part) (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P2998#integer, SPARQL

@GZWDer, Jura1: et al. This property is currently used in Spain, Australia and South Korea. I think this rather should be put in the item about the position held (P39) or in the item about the legislative body! In Sweden (Q34), I think we have 18 in some places and 16 in others today. Historically it has been even worse, with many more age-limits in different parts of the country and in different chambers. I also think this could be used in position held (P39) who are not elected, when applicable. -- Innocent bystander (talk) 17:02, 28 July 2016 (UTC)[reply]

These minimum age properties give a basic overview and can allow quick comparisons. If it is mostly the same for everything, this can do fine on countries or states. Obviously, there should be a way to find more detailed information. For some, this can be included with "subject of" (linking to detailed items), here "applies to" can work out.

On items for offices, it would be good if we had a property for general requirements for these office-holders, as we do for the voting right in elections. Maybe we could add P2998 on items for offices as well. I don't quite see how it could be included in P39.

Currently, the main problem is that we can't add this property with Quickstatements. Maybe we should drop years old (Q24564698) or add that later if some bot is found. It seems obvious that the number refers to years of age.
--- Jura 08:19, 29 July 2016 (UTC)[reply]

@Jura1: I do not propose that it should be put into P39 itself, but into the subjects of P39 like "President of Scotland", "King of Texas" etc. -- Innocent bystander (talk) 08:47, 29 July 2016 (UTC)[reply]

Ok. I mis-understood the last part "could be used in position held". What do you think about the unit problem?
--- Jura 08:52, 29 July 2016 (UTC)[reply]

You can add without unit to start with. We can change to "years old" later. -- Innocent bystander (talk) 09:16, 29 July 2016 (UTC)[reply]

I agree, this data would be better stored on the items for the positions. --Yair rand (talk) 18:24, 24 May 2018 (UTC)[reply]

@Innocent bystander, Jura1, Yair rand: I added geographic region (Q82794) or position (Q4164871) as a constraint. I see two open questions still: geographic region (Q82794) seems to be way too broad, maybe we could use administrative territorial entity (Q56061) instead; while almost half of the current usages (6 out of 13) are specific legislative election (Q2618461)s. Do we want to allow it? —Tacsipacsi (talk) 19:15, 4 December 2018 (UTC)[reply]

I have replaced 21 years P2312 by 40, which is the minimum age to be elected as president in Germany. It might be even higher in other countries. --1rhb (talk) 03:42, 4 December 2018 (UTC)[reply]