Wikidata:Property proposal/within time period
within time period[edit]
Originally proposed at Wikidata:Property proposal/Creative work
| Description | time period (e.g. theatre season) during which an event took place |
|---|---|
| Represents | time interval (Q186081) |
| Data type | Item |
| Domain | event (Q1656682) |
| Example | Eine kleine Stadt (Q43689202) → European Theater Season 1938/39 (Q40008291) |
| Planned use | The property is needed to link performing arts productions to the corresponding theatre season. It will be used in the context of a pilot ingest of a performing arts production database which is further documented here. |
| See also | point in time (P585) (P585 has a format restriction "point in time" and is therefore not appropriate for pointing to a time interval, although one could argue that a theatre season running from August to July is as much a point in time as a year is.) |
- Motivation
Most theatres operate by seasons (in Europe they usually start in August and end in July); therefore, the "season" is typically indicated in production databases, theatre programmes, etc. There are different approaches to modeling theatre seasons. See Wikidata:WikiProject_Performing_arts/Data_sources/CH#Theatre_Seasons for a discussion. I guess the easiest one is to model the season as a time interval (example: European Theater Season 1938/39 (Q40008291)). In theory, point in time (P585) could be used to point to the season, if it were not for the format restriction which calls for a "point in time" and does not allow time intervals. Thus, either the format restriction would need to be lifted on P585, or a new property would need to be created.
Background: In cooperation with staff members of the Swiss Archives for the Performing Arts (formerly: Swiss Theatre Collection) and a member of the German theatre archive community, I'm presently preparing the necessary ontology elements for a pilot ingest of theatre production data (all the productions of the Schauspielhaus Zürich during approx. 30 years). For us, this is a first step towards ingesting all the production data held by the Swiss Archives for the Performing Arts (50'000+ productions). Beat Estermann (talk) 14:04, 26 November 2017 (UTC)
- Discussion
Notified participants of WikiProject Performing arts
Notified participants of WikiProject Theatre
WikiProject Cultural heritage has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead.
Comment time period (P2348) could work for you.
--- Jura 14:13, 26 November 2017 (UTC)- Yes, indeed. If there is general agreement to adapt the definition of time period (P2348) to fit our use case (as it is defined at present, it seems to be more about "historical eras"), I guess we could go with P2348. --Beat Estermann (talk) 15:05, 26 November 2017 (UTC)
Oppose - use P2348. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:24, 26 November 2017 (UTC)- Oppose Duplicate David (talk) 08:28, 28 November 2017 (UTC)
- @ديفيد عادل وهبة خليل 2: It's currently no duplicate. We could change the scope of P2348 but we haven't yet. ChristianKl (✉) 14:28, 28 November 2017 (UTC)
- Comment I don’t like time period (P2348) as a match for this. The relevant subject for this property might be season (Q25938183). And I suggest that the property should be “season” and should be defined so as to apply to theatre, sports, fashion, etc. In fashion, a season might be “fall/winter 2017” so we'd have to allow values that aren’t just date ranges. - PKM (talk) 22:33, 6 December 2017 (UTC)
- Comment A new property "season" would be fine for the use in the context of theatre as well and would be understood more intuitively than "period". We could use "period" for historical eras and "season" for theatre, fashion, sports seasons. Or as an alternative, how about a double-label "period or season"? - Personally, I cannot think of any concrete querying examples that would favor one or the other approach: I don't see the interest of querying both (historical eras & theatre seasons) at once; at the same time it should not be too complicated to filter out the one that is of interest. I also don't see a big risk of people mixing them up when entering the data if we add a comment in the description of each property that points to the other property. --Beat Estermann (talk) 20:25, 8 December 2017 (UTC)
| Lang | P2348 | P1264 |
|---|---|---|
| en | time period | valid in period |
| de | Zeitraum | betroffener Zeitraum |
| es | periodo histórico | periodo aplicable |
| fr | période | période applicable |
| it | periodo | periodo di validità |
| ja | 時代 | 当てはまる期間 |
| pl | era | poprawny w okresie |
| pt | período de tempo | período aplicável |
| ru | эра | действительно для периода |
| zh | 時期 | 有效期 |
- Comment Looks like the labels of valid in period (P1264) and time period (P2348) don't match in many languages. I'd still favor aligning them instead of determining a maximum for a new property.
--- Jura 20:48, 11 December 2017 (UTC) - Comment I have been bold and have adapted the label and the definition of time period (P2348) accordingly (in English, German, and French). I'll leave this property discussion open for now in case there are any opposing reactions. --Beat Estermann (talk) 22:31, 12 December 2017 (UTC)
- Since there haven't been any opposing reactions, I'm withdrawing this proposal. --Beat Estermann (talk) 17:07, 14 January 2018 (UTC)