Property talk:P3530

Documentation

• Start a query
• Current uses
• Statistics by class
• Units
• Scale of values
• List of qualifiers
• Count

par
predetermined number of strokes a 0-handicap golfer should require to complete a hole, a round or a tournament

Description	the predetermined number of strokes that a scratch golfer should require to complete a hole, a round, or a tournament
Represents	par (Q2304774)
Data type	Quantity
Template parameter	par1 at en:Template:Infobox Golf Facility
Domain	According to this template: golf course/tournament According to statements in the property: golf course (Q1048525) or golf tournament (Q2990946) When possible, data should only be stored as statements
Allowed values	According to this template: integer According to statements in the property: 1 ≤ 𝓧 ≤ 400 When possible, data should only be stored as statements
Allowed units	not applicable
Example	Riviera Country Club (Q7338863) → 71 Augusta National Golf Club (Q765780) → 72
Tracking: usage	Category:Pages using Wikidata property P3530 (Q30128061)
Lists	Items with the most statements of this property Count of items by number of statements (chart) Items with the most statements Items with the fewest statements Count of items by number of sitelinks (chart) Items with the most sitelinks Items with the most sitelinks, but no link to one Wikipedia (sample: Welsh Wikipedia, cywiki) Items with the fewest sitelinks Most linked wikis Items with the most identifier properties Items with no other statements Most recently created items Items with novalue claims Items with unknown value claims Usage history (total) Usage history (main statement) Chart by item creation date Minimum and maximum Items with highest numeric value Items with lowest numeric value Database reports/Constraint violations/P3530 Map Random list
Proposal discussion	Proposal discussion
Current uses	Total 294 Main statement 292 99.3% of uses Qualifier 2 0.7% of uses

[create Create a translatable help page (preferably in English) for this property to be included here]

Range from “1” to “400”: values should be in the range from “1” to “400”. (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/P3530#Range

Type “golf course (Q1048525), golf tournament (Q2990946)”: item must contain property “instance of (P31)” with classes “golf course (Q1048525), golf tournament (Q2990946)” 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/P3530#Type Q1048525, Q2990946, SPARQL

No bounds: values can't have any bounds (e.g. 1 not 1±0) (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/P3530#No Bounds, SPARQL

Units: “novalue”: 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/P3530#Units

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/P3530#integer, SPARQL

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/P3530#Scope, hourly updated report, SPARQL

Constraints

@Thierry Caro, GZWDer: Hi. I'm trying to use this property in tournament items to show the result of winner. See Q104561689#P1346, for instance.

I tried to put P3530= -6, showing the final difference with tournament par, as we can see in en:2021_U.S._Open_(golf)#Final_round, but it gave 2 constraints: to be negative & to be used as qualifier. Then, I tried to inform the par for tournament as property with P3530=284 (and be able to calculate the strokes under par) and then, a constraint to be out of scope (1-100) appears.

So, what should be the better ontology solution? Option a) accept negatives and to be used as qualifiers; option b) increase the limit of par > 100 in order to fit the valid values for a tournament?. thanks, Amadalvarez (talk) 17:17, 28 September 2021 (UTC)

I'm no specialist of this. I cannot really help you. Thierry Caro (talk) 22:44, 28 September 2021 (UTC)

@CroMagnonMan: Could you, please, give us a suggestion ?. Thanks,Amadalvarez (talk) 15:31, 29 September 2021 (UTC)

@GZWDer, CroMagnonMan:Without any other input in two weeks, I choose option b, because it requires fewer and less conflicting changes. I'll increase it to 400 (4 rounds x 100 max.). Any further comment(with ping, please), will be welcome. Thanks, Amadalvarez (talk) 12:08, 11 October 2021 (UTC)