Property talk:P3450
Latest comment: 8 months ago by Amadalvarez in topic Sports as a constrain in multi-sport events
Documentation
sports season of league or competition
property that shows the competition of which the item is a season. Use P5138 for "season of club or team".
property that shows the competition of which the item is a season. Use P5138 for "season of club or team".
[create Create a translatable help page (preferably in English) for this property to be included here]
Type “season (Q27020041), recurrent event edition (Q27968055), sports competition (Q13406554)”: item must contain property “instance of (P31)” with classes “season (Q27020041), recurrent event edition (Q27968055), sports competition (Q13406554)” 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/P3450#Type Q27020041, Q27968055, Q13406554, SPARQL
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/P3450#Item P641, search, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P3450#Item P641, search, SPARQL
Property “sport (P641)” declared by target items of “sports season of league or competition (P3450)”: If [item A] has this property with value [item B], [item B] is required to have property “sport (P641)”. (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/P3450#Target required claim P641, SPARQL, SPARQL (by value)
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/P3450#Scope, SPARQL
Conflicts with “instance of (P31): sports season of a sports club (Q1539532)”: this property must not be used with the listed properties and values. (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/P3450#Conflicts with P31, search, SPARQL
Contemporaries:
if [item A] has this property (sports season of league or competition (P3450)) 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 (sports season of league or competition (P3450)) 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/P3450#Contemporary, SPARQL
Qualifiers “follows (P155), followed by (P156), series ordinal (P1545), reason for deprecated rank (P2241), reason for preferred rank (P7452), sourcing circumstances (P1480)”: this property should be used only with the listed qualifiers. (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/P3450#allowed qualifiers, 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/P3450#Entity types
|
This property is being used by:
Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.) |
Labels of items would generally have a year in it
TODO: correct English label, remove statement or define exceptions (Help)
Violations query:
List of this constraint violations: Database reports/Complex constraint violations/P3450#Labels of items would generally have a year in it
TODO: correct English label, remove statement or define exceptions (Help)
Violations query:
SELECT ?item ?value WHERE { ?item wdt:P3450 ?value . ?item rdfs:label ?l . FILTER(lang( ?l) = "en" && !REGEX(?l, "(1[89]\u007C20)\\d\\d") ) FILTER ( ?item != wd:Q2453542 ) FILTER ( ?value != wd:Q1779706 ) } LIMIT 100List of this constraint violations: Database reports/Complex constraint violations/P3450#Labels of items would generally have a year in it
Specify "operating area" for UK values
TODO: if the value has country (P17)=United Kingdom (Q145), please add operating area (P2541). Sample: Q2267464 (Help)
Violations query:
List of this constraint violations: Database reports/Complex constraint violations/P3450#Specify "operating area" for UK values
TODO: if the value has country (P17)=United Kingdom (Q145), please add operating area (P2541). Sample: Q2267464 (Help)
Violations query:
SELECT DISTINCT (?competition as ?item) WHERE { ?season wdt:P3450 ?competition . ?competition wdt:P17 wd:Q145 . FILTER NOT EXISTS { ?competition wdt:P2541 [] } }List of this constraint violations: Database reports/Complex constraint violations/P3450#Specify "operating area" for UK values
Item with Q27020041 would generally have this property
TODO: add P3450 (Help)
Violations query:
List of this constraint violations: [[Wikidata:Database reports/Complex constraint violations/P3450#Item with Q27020041 would generally have this property|Database reports/Complex constraint violations/P3450#Item with Q27020041 would generally have this property]]
TODO: add P3450 (Help)
Violations query:
SELECT ?item WHERE { ?item wdt:P31 wd:Q27020041 . FILTER NOT EXISTS { ?item wdt:P3450 [] } } LIMIT 100List of this constraint violations: [[Wikidata:Database reports/Complex constraint violations/P3450#Item with Q27020041 would generally have this property|Database reports/Complex constraint violations/P3450#Item with Q27020041 would generally have this property]]
Value shouldn't be a disambiguation page
TODO: change value (Help)
Violations query:
List of this constraint violations: Database reports/Complex constraint violations/P3450#Value shouldn't be a disambiguation page
TODO: change value (Help)
Violations query:
SELECT DISTINCT ?item ?value WHERE { ?item wdt:P3450 ?value . ?value wdt:P31 wd:Q4167410 . } LIMIT 100List of this constraint violations: Database reports/Complex constraint violations/P3450#Value shouldn't be a disambiguation page
| ||||||||||||||
Charts
edit
|
Values in sport (P641)edit
| ||||
Values in country (P17)edit
|
Values in organizer (P664)edit
| ||||
Values in operating area (P2541)edit
|
Discussion
editI think this property should mainly be used on items which are instance of season (Q27020041) and not sports season of a sports club (Q1539532). season (Q27020041) is for seasons of a sports league; sports season of a sports club (Q1539532) is for seasons of a sports club. These are two different concepts and shouldn't be mixed up. --Pasleim (talk) 13:52, 16 January 2017 (UTC)
I agree. This property should only be used on items which are instance of season (Q27020041). Is about seasons of a sports competition, not season of a sport club. Xaris333 (talk) 02:53, 30 July 2017 (UTC)
Sports only?
editIf this is for sports only it could perhaps be a little bit more clarified in the description box. Otherwise it might seem it can be used on seasons of tv-series. Or is it supposed to be used there too? Ainali (talk) 07:41, 18 January 2017 (UTC)
- I changed the English label. For TV series I would use part of the series (P179) --Pasleim (talk) 16:48, 20 January 2017 (UTC)
- Makes sense, thanks! Ainali (talk) 13:14, 24 January 2017 (UTC)
@Ainali: I know it's old, but also for future reference: there is season (P4908) added for TV series. Yarl 💭 22:42, 13 May 2018 (UTC)
sub-property of ?
editP31 or P361? Both? d1g (talk) 19:52, 30 July 2017 (UTC)
- I tend to think about P361 in
- from this discussion Wikidata:Project_chat#League_seasons
- d1g (talk) 20:06, 30 July 2017 (UTC)
Broadening of scope to non-seasoned sports competitions; redundancies
editI see that this property is now used as well for sports competitions which are not seasons at all, and not games at all.
- Has this been discussed somewhere?
- It is now analogous to part of the series (P179), but for sports competitions. Do we need both? There is also redundancy with instance of (P31) claims, whose aspired level of granularity is controversial as always of course.
- Can the labels please be adjusted accordingly, in case we want to continue using it for sports competitions of all types?
--MisterSynergy (talk) 20:15, 21 August 2017 (UTC)
Do you have an example? Maybe is my mistake, maybe I have added this property is wrong items. Xaris333 (talk) 00:05, 22 August 2017 (UTC)
- Changes such as these ones in 1989 World Rowing Championships (Q972814). The same applies to basically all items about non-seasoned sports competitions. The concept of a “season” is—if at all—used differently in racing sports. The property sports season of league or competition (P3450) was designed to work with league–season relations, which is not found in all sports.
- I have set up a solid base structure for rowing items long time ago, following the back-then established method with P31/P279. If there now was a change to improve homogeneity or to improve some data about sports competitions, I wouldn’t object to change rowing items as well, but I do expect suitable labels on the properties used in the items, as well as a plan what to do. There are queries in use right now which rely on P31/P279 claims, but they don’t work any longer if you disassemble the established claims. --MisterSynergy (talk) 06:54, 22 August 2017 (UTC)
- @Xaris333: could you please stop your edits and solve this section before you continue? I already lost track of the changes you made, and I am still not at all convinced that they are correct. You are even removing valid statements. Thanks, MisterSynergy (talk) 21:18, 22 August 2017 (UTC)
- Ok. But even I am wrong, the structure of the items allow us to easily correct them with a bot. Xaris333 (talk) 21:21, 22 August 2017 (UTC)
- @Xaris333: could you please stop your edits and solve this section before you continue? I already lost track of the changes you made, and I am still not at all convinced that they are correct. You are even removing valid statements. Thanks, MisterSynergy (talk) 21:18, 22 August 2017 (UTC)
Constraints review
editThis property currently has plenty of constraint which are not crucial for its functionality. The constraint report is meanwhile larger than 1M (in wikisource size), which is probably the reason why Ivan’s bot is no longer able to properly update it (see User talk:Ivan A. Krestinin#P3450). I suggest to review the constraints currently defined in the property. Specifically I suggest to remove these ones:
- ⟨ sports season of (P3450) ⟩ property constraint (P2302)
⟨ value-requires-statement constraint (Q21510864)
property (P2306)- 10545 violations
- Reason: many of the values which currently violate this constraint are unable to use country (P17) claims, as they are supra-national events (query). Examples: UEFA Champions League (Q18756), Mediterranean Games (Q272090), Formula One (Q1968), and so on. We should not define constraints if they do not really apply to the full range of allowed values.
- ⟨ sports season of (P3450) ⟩ property constraint (P2302)
property (P2306)- 20718 violations
- Reason: as in previous bullet point.
- ⟨ sports season of (P3450) ⟩ property constraint (P2302)
property (P2306)- 5737 violations
- Reason: we do not necessarily have templates for all sports competitions.
Any comments? —MisterSynergy (talk) 08:19, 5 May 2018 (UTC)
- Not sure if the actual numbers matter. This is a fairly recent property that applies to tens of thousands of items, many previously without any statements and thus problematic within Wikidata as such. It's important that these include a reasonable number of statements that locate the within the Wikidata universe. Unless the constraints are mandatory, we don't need to target zero or list every exception.
I think it would help if P17 was set to "somevalue" if one or several countries can't be applied. Maybe we should keep the value required one and come up with a complex one for the other.
--- Jura 08:33, 5 May 2018 (UTC)- Numbers matter here because the amount of constraint violations is the reason that the report is dysfunctional now. Sure, Ivan’s covi reports are not the only way to evaluate violations, but they are used a lot by many users (probably much more than SPARQL queries and the constraint gadget). I also understand the value of having them in general, but here it is just too much.
I do not understand your suggestion with “somevalue” (aka “unknown value”) claims; countries in this context are not unknown, there may just be many (e.g. UEFA Champions League) or each time a different one (e.g. Olympic Games), thus the property is not applicable at all. As a side note it is not clear whether the values of country (P17) should include the host countries only or all countries eligible for participation. —MisterSynergy (talk) 10:08, 5 May 2018 (UTC) - @Jura1: can you please have a look at the constraint violations listed above? I don’t have a clue how to substantially reduce their number in all three cases, but as long as the number is above 5000, any fix does not help to reduce the covi report length (the update bot truncates the violation list at 5000 violations per constraint). Right now, the report is accessible only every second day for whatever reason, and I don’t even manage to open past versions (e.g. [1]). —MisterSynergy (talk) 06:56, 9 May 2018 (UTC)
- Good to hear I'm not the only one to worry about working constraint reports. For this particular one, I think we mostly used queries anyways as it didn't work for some other reason as well.
To reduce the size, I deleted most constraints. We can re-add them later once volume is lower.
--- Jura 07:09, 9 May 2018 (UTC)- Thanks. For reference: these constraints were removed. —MisterSynergy (talk) 07:12, 9 May 2018 (UTC)
- Good to hear I'm not the only one to worry about working constraint reports. For this particular one, I think we mostly used queries anyways as it didn't work for some other reason as well.
- Numbers matter here because the amount of constraint violations is the reason that the report is dysfunctional now. Sure, Ivan’s covi reports are not the only way to evaluate violations, but they are used a lot by many users (probably much more than SPARQL queries and the constraint gadget). I also understand the value of having them in general, but here it is just too much.
Removing country
editPer the discussion above, country (P17) does not seem reasonable, as there are literally thousands of entries of supranational competitions. For some reason, it was added again, and I just removed it. Please comment if you feel it is inappropriate or if there's some reason we should keep it. Redgolpe (talk) 15:53, 6 March 2019 (UTC)
Sports as a constrain in multi-sport events
editThe multi-sport event (Q167170) season items usually doesn't have sport (P641) and a constrain appears in sports season of league or competition (P3450) statement. May someone change it?. I tried to do it, without success. Thank you ! Amadalvarez (talk) 05:54, 7 March 2024 (UTC)