Property talk:P1358
Latest comment: 3 years ago by Joshbaumgartner in topic Use as a main property
Documentation
points for
number of points in a league table or decathlon. (Use P1351 for goals/points in a match)
number of points in a league table or decathlon. (Use P1351 for goals/points in a match)
Description | the number of league points ('Pts') this team has. Use as qualifier to P710 in league items. Use number of points/goals/set scored (P1351) for total goals scored ('GF'). | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type | Quantity | ||||||||||||
Template parameter | put Wikipedia infobox parameters here, if existing; ex: "population" in en:template:infobox settlement | ||||||||||||
Domain | Sports teams (note: this should be moved to the property statements) | ||||||||||||
Allowed values | positive whole numbers (note: this should be moved to the property statements) | ||||||||||||
Allowed units | not applicable | ||||||||||||
Example | 2014 FIFA World Cup Group A (Q10260330). participant (P710):Brazil men's national football team (Q83459) => 6 (note: this information should be moved to a property statement; use property Wikidata property example (P1855), Wikidata property example for properties (P2271), Wikidata property example for lexemes (P5192), Wikidata property example for forms (P5193) or Wikidata property example for senses (P5977)) | ||||||||||||
Source | external reference, Wikipedia list article (either infobox or source) (note: this information should be moved to a property statement; use property source website for the property (P1896)) | ||||||||||||
Robot and gadget jobs | Should or are bots or gadgets doing any task with this? (Checking other properties for consistency, collecting data, etc.) | ||||||||||||
Tracking: usage | Category:Pages using Wikidata property P1358 (Q23909053) | ||||||||||||
See also | test score (P5022), number of points/goals/set scored (P1351) | ||||||||||||
Lists | |||||||||||||
Proposal discussion | Proposal discussion | ||||||||||||
Current uses |
|
[create Create a translatable help page (preferably in English) for this property to be included here]
Scope is as qualifier (Q54828449), as main value (Q54828448): the property must be used by specified way only (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/P1358#Scope, 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/P1358#Units
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/P1358#No Bounds, SPARQL
This property is being used by: Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.) |
Use as a main property
editI see the original use case that led to this property and uses it as a qualifier, but I'm not seeing a reason why this property cannot also be used as a main property on an item, namely on an individual or team to record their aggregate total. Simply removing the constraint property constraint (P2302) > property scope constraint (Q53869507) would seem okay, any objection? Josh Baumgartner (talk) 21:50, 14 October 2021 (UTC)