Property talk:P1191
Latest comment: 6 years ago by Jura1 in topic should only be used for live performance
Documentation
- Start a query
- Current uses
- With precision and calendarmodel
- Statistics by class
- By century
- Date precision
- Calendar models
- List of qualifiers
- Count
date of first performance
date a work was first debuted, performed or live-broadcasted
date a work was first debuted, performed or live-broadcasted
[create Create a translatable help page (preferably in English) for this property to be included here]
Range from “-0500-00-00T00:00:00Z” to “now”: values should be in the range from “-0500-00-00T00:00:00Z” to “now”. (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/P1191#Range
Type “work (Q386724), group of works (Q17489659), performing arts production (Q43099500), live broadcast (Q26261757), series of performances (Q43100730)”: item must contain property “instance of (P31)” with classes “work (Q386724), group of works (Q17489659), performing arts production (Q43099500), live broadcast (Q26261757), series of performances (Q43100730)” 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/P1191#Type Q386724, Q17489659, Q43099500, Q26261757, Q43100730, SPARQL
Qualifiers “location (P276), production company (P272), musical conductor (P3300), performer (P175), reason for deprecated rank (P2241), reason for preferred rank (P7452), has characteristic (P1552), location of creation (P1071), broadcast by (P3301), presenter (P371), sourcing circumstances (P1480), of (P642), cast member (P161), place of publication (P291), refine date (P4241), statement is subject of (P805), located in the administrative territorial entity (P131)”: 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/P1191#allowed qualifiers, SPARQL
Single best value: this property generally contains a single value. If there are several, one would have preferred rank (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/P1191#single best value, SPARQL
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/P1191#Scope, 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/P1191#Entity types
Conflicts with “instance of (P31): podcast (Q24634210)”: 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/P1191#Conflicts with P31, SPARQL
|
This property is being used by:
Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.) |
Upper range limit
editWhy is the upper limit for the range the current time? Future dates should be accepted, if they have reference. If they turn out not to happen they can be depreciated (with reference why that didn't happen to be the premiere). – Máté (talk) 18:34, 16 August 2016 (UTC)
- @Máté: This seems acceptable to me too too as long it's trivial or if there is sources. It seems logical to accept value in the future for dates as we already wildely accept items about future concepts, especially for events like 2020 Summer Olympics (Q181278), 2024 Summer Olympics (Q995653), 2028 Summer Olympics (Q1451505), etc. Cdlt, VIGNERON (talk) 18:26, 22 August 2016 (UTC)
Change of the label from "first performance" to "date of first performance"
editReason: Avoid confusion with "first representation of" (which links the item of the first performance to the item of the performing arts production. For more context, see the reasoning at: Wikidata:WikiProject_Performing_arts/Data_sources/CH. --Beat Estermann (talk) 11:15, 25 November 2017 (UTC)
should only be used for live performance
edit
Notified participants of WikiProject Movies
For broadcast media, this should be used only if it is a live broadcast. For non-live broadcast should use publication date (P577) instead. --Ans (talk) 14:11, 30 November 2017 (UTC)
But the first screening (red carpet premiere) is usually not the same as the date of release (publication). The two properties indicate different things. – Máté (talk) 20:37, 6 January 2018 (UTC)
- We need to sort this out. Please comment at Wikidata_talk:WikiProject_Movies#dates_for_episodes.
--- Jura 13:10, 12 March 2018 (UTC)