Property talk:P115

From Wikidata
Jump to navigation Jump to search

Documentation

home venue
home stadium or venue of a sports team or applicable performing arts organization
Descriptionhome stadium or venue of a sports team or applicable performing arts organization
Representsstadium (Q483110), concert hall (Q1060829)
Data typeItem
Domainsports organization (Q4438121), sports season (Q27020041), musical group (Q215380), sporting event (Q16510064) or sports competition (Q13406554)
Allowed valuesbuilding (Q41176) (note: this should be moved to the property statements)
ExampleManchester United F.C. (Q18656)Old Trafford (Q83457)
Galatasaray S.K. (Q495299)Rams Park (Q81492)
FC Bayern Munich (Q15789)Allianz Arena (Q127429)
FC Cincinnati (Q20855983)TQL Stadium (Q54465634)
SC DHfK Leipzig (Q1725148)Arena Leipzig (Q316575)
Seattle Symphony (Q2284692)Benaroya Hall (Q3892069)
Tracking: sameno label (Q42533258)
Tracking: differencesno label (Q55283141)
Tracking: usageCategory:Pages using Wikidata property P115 (Q26250069)
Tracking: local yes, WD nono label (Q55283133)
See alsoStadiumDB ID (P5288), World Stadium Database ID (P5289)
Lists
Proposal discussion[not applicable Proposal discussion]
Current uses
Total60,724
Main statement58,80196.8% of uses
Qualifier1,9203.2% of uses
Reference3<0.1% of uses
Search for values
[create Create a translatable help page (preferably in English) for this property to be included here]
Value type “architectural structure (Q811979): This property should use items as value that contain property “instance of (P31)”. On these, the value for instance of (P31) should be an item that uses subclass of (P279) with value architectural structure (Q811979) (or a subclass thereof). (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/P115#Value type Q811979, SPARQL
Inverse property of “occupant (P466):
if [item A] has this property (home venue (P115)) linked to [item B],
then [item B] should also have property “occupant (P466)” linked to [item A]. (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/P115#inverse, SPARQL
Conflicts with “maximum capacity (P1083): 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/P115#Conflicts with P1083, SPARQL
Conflicts with “coordinate location (P625): 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/P115#Conflicts with P625, SPARQL
Contemporaries:
if [item A] has this property (home venue (P115)) 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/P115#Contemporary, hourly updated report, 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/P115#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/P115#Scope, SPARQL
This property is being used by:

Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

Just keep in mind, as for all such properties here, our practice has been to list current and former items, with the expectation that we'll eventually be able to add fields for dates. In fact, I would even add future home stadiums, as there are a number under construction. Shawn in Montreal (talk) 16:01, 27 February 2013 (UTC)[reply]

Alias[edit]

Added en. alias "ground" as it is known in the UK, the club's home ground. Danrok (talk) 01:02, 28 February 2013 (UTC)[reply]

Is there a problem?[edit]

As English Wikipedia states, "stadium" is reserved for a specific type of structure that appears to be distinct from the smaller indoor "arena" or "rink." Yet these are just as much home venues for the basketball, ice hockey and indoor arena football teams that play in them? Do we need to rename the property or create a redirect from "arena"...? Shawn in Montreal (talk) 23:43, 3 March 2013 (UTC)[reply]

I think this one property "home stadium" should cover all sports teams/clubs, as described here: Home (sports). Perhaps it should be renamed. Danrok (talk) 00:47, 4 March 2013 (UTC)[reply]
Agreed. How about "Home sports venue"? Too long or not clear enough? Shawn in Montreal (talk) 00:53, 4 March 2013 (UTC)[reply]
It works for me. Danrok (talk) 01:24, 4 March 2013 (UTC)[reply]
A Google search for "home venue" reveals that it is used for things like ballet companies. So yes, I guess the "sports" is needed in there. Shawn in Montreal (talk) 01:42, 4 March 2013 (UTC)[reply]
But generalizing the property, when the concept is the same, to "home venue" can't be a bad thing can it? Support "home venue". Espeso (talk) 03:32, 4 March 2013 (UTC)[reply]
So it need not apply only to sports teams. Sure. Then the label would need to be changed, too, to reflect non-sports uses such as this. Which happens to be the first Google result when searching "home venue." Shawn in Montreal (talk) 03:46, 4 March 2013 (UTC)[reply]

Should it be used as a place where competitions happen ?[edit]

@Shawn à Montréal, Pasleim: Hi, I'm working in a infobox for sporting event (Q16510064) / sports competition (Q13406554). In this domains, items usually have the competition venues informed in location (P276). I thought home venue (P115) were more appropriate because we're talking about sportive venue, but just a few items have this property and most of them repeating the value of P276. In addition, the P115 shows a constraint because of lack of inverse property P466 in the stadium item.

So, as sporting event (Q16510064), sports competition (Q13406554) are valid domain for this property, but it make no sense to put a occupant (P466) in all the competitions played there, what's your opinion?:

A) To use P115 for competition venues in the event items, and do not apply P466 constraint.

B) To use only P276 for competition venues (as majority now) and eliminate all P115 from event items (and move the value to P276, just in case).

Thanks, Amadalvarez (talk) 03:54, 15 June 2023 (UTC)[reply]

After two months without new opinion, I answer to myself: To use P115 when item is for sports season of a sports club (Q1539532) (or subclasses); to use P276 for esdeveniment esportiu (Q16510064) / competició esportiva (Q13406554). For compatibility reasons, I'll keep existing duplicate use on both P115 & P276 when values were the same, else I'll delete non corresponding use. Salut ! Amadalvarez (talk) 03:37, 10 August 2023 (UTC)[reply]