Property talk:P118
Latest comment: 9 months ago by Сидик из ПТУ in topic Using season (2)
Documentation
league
league in which team or player plays or has played in
league in which team or player plays or has played in
[create Create a translatable help page (preferably in English) for this property to be included here]
Type “sports organization (Q4438121), human (Q5), competition (Q476300), sporting event (Q16510064), sports award (Q15229207), sports transaction (Q18515440)”: item must contain property “instance of (P31)” with classes “sports organization (Q4438121), human (Q5), competition (Q476300), sporting event (Q16510064), sports award (Q15229207), sports transaction (Q18515440)” 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/P118#Type Q4438121, Q5, Q476300, Q16510064, Q15229207, Q18515440, SPARQL
Contemporaries:
if [item A] has this property (league (P118)) linked to [item B],
then [item A] and [item B] have to coincide or coexist at some point of history. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). if [item A] has this property (league (P118)) linked to [item B],
then [item A] and [item B] have to coincide or coexist at some point of history. (Help)
List of violations of this constraint: Database reports/Constraint violations/P118#Contemporary, SPARQL
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/P118#Entity types
Scope is as main value (Q54828448), as qualifier (Q54828449): 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/P118#Scope, SPARQL
Contemporaries:
if [item A] has this property (P118) linked to [item B],
then [item A] and [item B] have to coincide or coexist at some point of history.
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). if [item A] has this property (P118) linked to [item B],
then [item A] and [item B] have to coincide or coexist at some point of history.
List of violations of this constraint: Database reports/Constraint violations/P118#Contemporary, SPARQL
| ||||||||||||||
|
This property is being used by:
Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.) |
Discussion edit
Extend domain to sports persons as well? edit
Some infoboxen on sports persons use a "league" parameter as well to show in which league some sports person is active. Example https://en.wikipedia.org/w/index.php?title=Dennis_Schr%C3%B6der&action=edit&editintro=Template:BLP_editintro :
{{Infobox basketball biography
[...]
| league = NBA
So I think it would make sense to extend the domain of this property to these persons as well. Ideally all information on Wikidata would be 100% complete, then we could get this information another way (e.g. take a look at member of sports team (P54) and get the league information from the team value of that property) but as long as this is not the case, we might need this for those people.--Bthfan (talk) 07:15, 28 June 2014 (UTC)
Support I will change this if no objections come. Steak (talk) 11:58, 3 August 2017 (UTC)- Support. Yes, please. I'm working in person infobox with sportsperson now and it's a common data for people. Thanks,--Amadalvarez (talk) 04:45, 4 August 2017 (UTC)
Done Steak (talk) 10:17, 8 August 2017 (UTC)
Extend domain (2) edit
This property was initial thought to be used only with sports team (Q12973014). Now many sports season of a sports club (Q1539532) items have this property too. Should we extend the domain or delete/replace the claims? --Pasleim (talk) 09:07, 17 October 2015 (UTC)
Using season edit
Hello. This property is using with the league. But why not to use it with season as well? Or only with seasons?
For example, we are using it like:
Is correct. We give the information that Liverpool plays in Premier League. But we can give more information if we use season. For example,
With that we give the information that Liverpool plays in Premier League for the season 2016-17.
Xaris333 (talk) 17:08, 22 December 2016 (UTC)
Using season (2) edit
Currently the scope of this property is as follows, ensured by the property constraints:
We also have around 58k items of the type instance of (P31): sports season of a sports club (Q1539532) which need to be related to a sports season. I proposed a new property for that purpose at Wikidata:Property proposal/sports competition competed at, but the suggestion was made to broaden the scope of this property league (P118) instead to permit use in that scenario as well. We would then be able to use it as follows:
⟨ 2009–10 FC Bayern Munich season (Q135566) 
⟩ league (P118) ⟨ 2009–10 Fußball-Bundesliga (Q121318) ⟩
⟩ league (P118) ⟨ 2009–10 Fußball-Bundesliga (Q121318) ⟩This would require to add sports season of a sports club (Q1539532) to the type constraint, add sports season (Q27020041) to the value constraint, and modify the labels in a way that reflects this broader scope.
Any ideas whether we should prefer this over the creation of a new property? —MisterSynergy (talk) 05:44, 8 May 2018 (UTC)
Wait. P118 is only for leagues. 2009–10 FC Bayern Munich season (Q135566) is not only about 2009–10 Fußball-Bundesliga (Q121318). Is also about 2009–10 DFB-Pokal (Q835773) and 2009–10 UEFA Champions League (Q184182). Both are tournament, not leagues... Maybe we could change the property to "sport competition" that is "competition in which team or player plays or has played in" and list all the competitions. Xaris333 (talk) 18:47, 10 May 2018 (UTC) May
- Coming back to this, I think it would indeed be useful to broaden the scope of this property to include other competitions like tournaments or cups. Currently there seems to be no way to indicate that a team or player has participated in a tournament in a general sense. As a direct example: With a broadenend scope, league (P118) on Jens Lehmann (Q57114) could include UEFA Champions League (Q18756) aswell, showing that the player has played in the UEFA Champions League at any point. Qualifiers could be added that show total games played and goals scored. participant in (P1344) shall still be used to add individual seasons of a cup/tournament/league. What do you think?
Notified participants of WikiProject Sports --Sotho Tal Ker (talk) 23:31, 22 June 2023 (UTC)
- Goals and total games should be shown by total goals in career (P6509) and number of matches played/races/starts (P1350) respectively. For example, look at Q615#P6509 where we can show not only leagues, but also cups, and anything. Moreover, in different sources, the data for goals, points, yellow cards, home runs may differ, therefore it is better to store these data not as qualifiers, but as independent statements with their own sources. Separate storage of data will facilitate subsequent work with them and allow you to get statistics using simpler queries to find out the best scorers of the tournament, the youngest and oldest players in the history of the tournament, to get on the map the birthplaces of all goalscorers, etc. With all this, the height of absurdity is the filling of games and goals with qualifiers for the member of sports team (P54) where it is not even clear which matches were taken into account (friendly? super cup?). Without these clarifications useless numbers are obtained. Сидик из ПТУ (talk) 06:50, 23 June 2023 (UTC)
- That is actually the worst way I can imagine to model this stuff. Who thought that this was a good approach? And why was total goals in career (P6509) introduced when there is number of points/goals/set scored (P1351) which does the same and has a broader scope? Also of (P642) has been made obsolete and will be replaced eventually. --Sotho Tal Ker (talk) 13:45, 23 June 2023 (UTC)
- For some sports (for example, for ice hockey) it is necessary to clearly separate points and goals. In the same place, with the help of qualifiers you can refine individual statistics on powerplay goals, shorthanded goals, etc., without creating separate properties for each type of goals. Сидик из ПТУ (talk) 08:40, 26 June 2023 (UTC)
- Anyway, my main point for extending the scope of this to include tournaments and cups still stands. The mentioned qualifiers are always optional. They can still be used as separate main statements, if that is wanted. A further benefit is the possibility to then replace of (P642) with this property. Unless there are any actual objections, I expect to extend the scope to "sports competition" in general, including leagues, tournaments and cups in July. --Sotho Tal Ker (talk) 20:38, 24 June 2023 (UTC)
- I agree that it is wrong to separate leagues, cups and super bowls according to different properties, but there should be separate qualifiers (point in time (P585), date of the first one (P7124), statement supported by (P3680), etc) for each indicator (goals, yellow cards, home runs). Сидик из ПТУ (talk) 08:40, 26 June 2023 (UTC)
- That is actually the worst way I can imagine to model this stuff. Who thought that this was a good approach? And why was total goals in career (P6509) introduced when there is number of points/goals/set scored (P1351) which does the same and has a broader scope? Also of (P642) has been made obsolete and will be replaced eventually. --Sotho Tal Ker (talk) 13:45, 23 June 2023 (UTC)
- Goals and total games should be shown by total goals in career (P6509) and number of matches played/races/starts (P1350) respectively. For example, look at Q615#P6509 where we can show not only leagues, but also cups, and anything. Moreover, in different sources, the data for goals, points, yellow cards, home runs may differ, therefore it is better to store these data not as qualifiers, but as independent statements with their own sources. Separate storage of data will facilitate subsequent work with them and allow you to get statistics using simpler queries to find out the best scorers of the tournament, the youngest and oldest players in the history of the tournament, to get on the map the birthplaces of all goalscorers, etc. With all this, the height of absurdity is the filling of games and goals with qualifiers for the member of sports team (P54) where it is not even clear which matches were taken into account (friendly? super cup?). Without these clarifications useless numbers are obtained. Сидик из ПТУ (talk) 06:50, 23 June 2023 (UTC)
