Property talk:P585

From Wikidata
Jump to navigation Jump to search

Documentation

point in time
date something took place, existed or a statement was true; for providing time use the "refine date" property (P4241)
DescriptionA point in time at which something happened or for which the source supports the claim. Commonly used as qualifier. See also start time (P580) and end time (P582).
Representspoint in time (Q186408)
Data typePoint in time
DomainAnything that was confined to a specific time, but not a range of time (note: this should be moved to the property statements)
Allowed valuesAny time (note: this should be moved to the property statements)
Example2012 United States presidential election (Q4226) →
Malaysia Airlines Flight 17 (Q17374096) →
Tracking: sameno label (Q42533398)
Tracking: differencesno label (Q55283195)
Tracking: usageCategory:Pages using Wikidata property P585 (Q20990066)
Tracking: local yes, WD nono label (Q55283197)
See alsostart time (P580), publication date (P577), dissolved, abolished or demolished date (P576), service retirement (P730), located in time zone (P421), time of discovery or invention (P575), day of week (P2894), end time (P582), date of first performance (P1191), retrieved (P813), time of earliest written record (P1249), date of official opening (P1619), time index (P4895), inception (P571), work period (start) (P2031), date depicted (P2913), awarded for period (P4566), closest approach (P6354)
Lists
Proposal discussionProposal discussion
Current uses
Total14,134,758
Main statement989,8127% of uses
Qualifier13,138,85393% of uses
Reference6,093<0.1% of uses
[create Create a translatable help page (preferably in English) for this property to be included here]
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/P585#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/P585#Scope, 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/P585#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.)

This property is being used by:

he:תבנית:אירוויזיון

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

Label[edit]

Can I change the label from "as of" to "date". It sounds a bit weird to say that the US elections took place "as of" November 6, 2012, doesn't it ? --Zolo (talk) 09:34, 19 June 2013 (UTC)[reply]

Yes thats why I had created it saying date but someone changed it. Changed it now to Point in time because hopefully soon the precision will go up.--Saehrimnir (talk) 16:13, 19 June 2013 (UTC)[reply]

Date for event[edit]

Is this the property used to state when an event happens? --Napoleon.tan (talk) 14:24, 8 July 2013 (UTC)[reply]

in principle yes but one should look if it can't be defined by start time (P580) and end time (P582).--Saehrimnir (talk) 22:54, 8 July 2013 (UTC)[reply]

examples for property point in time[edit]

  1. Organisation for the Prohibition of Chemical Weapons (Q842490) point in time 2013

I18n (talk) 16:50, 22 October 2013 (UTC)[reply]

Single value[edit]

Certain elections, like the one in Q18923548, are helt on more than one day, in this case a week apart. This conflicts with the Single value constraint. Can we prevent that or is a new constraint needed to indicate events that can have more than one date for the same edition of an event, where the days aren't connected (so not a period, like for a weekend long festival)? I checked the content of the category:Properties with time-datatype, but no property is beter suited for the aforementioned elections. - cycŋ - (talk • contribs • logs) 06:19, 22 September 2015 (UTC)[reply]

In that case one would want to use start date / end date. There are cases were multiple values make sense, but generally it should be avoided. The advantage of the constraint is also that it find problems like the ones on Q18889137. As long as we bear in mind that exceptions are possible, I don't think it's much of an issue.
I had added a unique value constraint to find duplicates. This worked fairly well. Obviously it wasn't meant to state that only one item could about a specific moment in time ;)
This later changed to single value constraint (with a different purpose). --- Jura 10:54, 22 September 2015 (UTC)[reply]
I understand the benefit of the single value constraint for most events, and start date / end date would be correct if the election is helt in the period between the two dates, and this may sometimes happen with elections. But in general election with more than one date are not helt on the days in between those dates and have, for instance, different rounds, and then using start date / end date is incorrect and even misleading. Elections may may also be helt at different dates for different areas, in witch case one may want to indicate that as well by using Property:P518. - cycŋ - (talk • contribs • logs) 13:00, 22 September 2015 (UTC)[reply]

Future dates[edit]

The descritions are written like this property is only used for past dates. This property is used for future events like 2024 Summer Olympics (Q995653). Shouldn't we change the descriptions? Emijrp (talk) 16:53, 13 July 2017 (UTC)[reply]

Using this property with decades and centuries[edit]

Is it valid to use "1950s" or "1800s" or "12. century" for values of this property? The system allows it, but I get weird results in Reasonator. - PKM (talk) 21:36, 20 January 2018 (UTC)[reply]

Allowed qualifiers constraints[edit]

I just noticed a note saying that some properties apparently can't be used as qualifier for Significant event. To model excavations at archaeological sites, I've been using manager/director as a qualifier for significant event: excavation, but apparently this isn't allowed. As many sites are excavated many times by different teams and directors, I was wondering what would be the best approach here. For an example of a site with several different excavations and directors, see Q42897132. Any ideas? --Zoeperkoe (talk) 11:10, 5 March 2018 (UTC)[reply]

Why limited to one day only?[edit]

Why is this property only allowed with one date through single-value constraint (Q19474404)? Many events take place on two days. Romaine (talk) 18:51, 27 April 2018 (UTC)[reply]

Wouldn't you use start time (P580) & end time (P582) then? — Finn Årup Nielsen (fnielsen) (talk) 19:12, 27 April 2018 (UTC)[reply]
That would be possible in many cases, but not all. For example, a meeting is organised on Friday, and continues on Monday, while is considered to be the same meeting. If we would use start time (P580) & end time (P582) it would suggest the meeting took four days. Also there are sports games in what one single game takes place on different dates with days in between. For those cases we need to find a solution.
In cases of a set of continues days then start time (P580) & end time (P582) can be used. Romaine (talk) 05:46, 28 April 2018 (UTC)[reply]

I have a related problem with dates that are not determined yet, but indicated to be "July 18 or 19 or 20, 2018". This is the case with 1st Workshop on Quality of Open Data (Q48548111). In your case I suppose it makes sense to have multiple dates. — Finn Årup Nielsen (fnielsen) (talk) 09:53, 7 May 2018 (UTC)[reply]

Another problem: what to indicate when an event was at a night? --Infovarius (talk) 10:30, 8 May 2018 (UTC)[reply]

Problem with multiple years in awards[edit]

I'm using this property registering awards, but when a person is awarded more than one year, that's a problem because single-value constraint (Q19474404). Example: Troféu HQ Mix for best writer (Q20052059) (in winner (P1346) section). Any suggestion? Lucio Luiz (talk) 14:52, 1 May 2018 (UTC)[reply]

@Lucio Luiz: The solution is to repeat a value with different qualifier. --Infovarius (talk) 10:31, 8 May 2018 (UTC)[reply]

Parsing: 11/12/2000 gives 2000-11-12 but 11-12-2000 gives 2000-12-11[edit]

And then 25/12/2000 gives 2000-12-25

Is there a reason for that difference? Shouldn't it be always considered as DD/MM/YYYY? The RedBurn (ϕ) 10:12, 23 August 2018 (UTC)[reply]

See T167788
Tracked in Phabricator
Task T167788
The RedBurn (ϕ) 08:40, 2 September 2018 (UTC)[reply]

dokumentation[edit]

please could you document, how P585 is not malformed. what about time? W!B: (talk) 21:54, 15 August 2019 (UTC)[reply]

Adding date and time[edit]

Tracked in Phabricator
Task T57755

Hello. Why cant I add 2016-12-06 06:00:00 (to Wikidata Sandbox (Q4115189), for example)? Attempting to do so gives me this error: Could not save due to an error. Malformed input: +2016-12-06T06:00:00Z. Rehman 06:03, 27 October 2020 (UTC)[reply]

Hmm, apparently it is not possible yet. How sad. Rehman 02:06, 29 October 2020 (UTC)[reply]
Retrieved from "https://www.wikidata.org/w/index.php?title=Property_talk:P585&oldid=2149057807"