Property talk:P3530
Documentation
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
When possible, data should only be stored as statements | |||||||||
Allowed values | According to this template:
integer
According to statements in the property:
When possible, data should only be stored as statements1 ≤ 𝓧 ≤ 400 | |||||||||
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 |
| |||||||||
Proposal discussion | Proposal discussion | |||||||||
Current uses |
|
List of violations of this constraint: Database reports/Constraint violations/P3530#Range
List of violations of this constraint: Database reports/Constraint violations/P3530#Type Q1048525, Q2990946, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P3530#No Bounds, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P3530#Units
List of violations of this constraint: Database reports/Constraint violations/P3530#integer, SPARQL
Constraints
edit@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)