Property talk:P4241

Documentation

• Start a query
• Properties using this qualifier (statistics)
• Count

refine date
qualifier to narrow down the precision of a date not fully specified by the Wikidata time datatype precision field

Data type	Item
Domain	qualifiers of time properties (note: this should be moved to the property statements)
Allowed values
Example	Cui Bai (Q709216) → middle of (Q40719748) Adriaen van Utrecht (Q367970) → autumn (northern hemisphere) (Q40720568) Hieronymus Janssens (Q3135313) → summer (northern hemisphere) (Q40720564) 1967 Mudurnu earthquake (Q26258) → 18:57 (Q55812016) Prince Louis of Wales (Q38668629) → 11:01 (Q52716468) Bunehout Manor (Q100806053) → end of (Q40719766)
See also	sourcing circumstances (P1480), floruit (P1317), work period (start) (P2031), work period (end) (P2032), start time (P580), end time (P582), earliest date (P1319), latest date (P1326), inception (P571)
Lists	Most recently created items Items with novalue claims Items with unknown value claims Usage history (total) Usage history (main statement) Chart by item creation date Database reports/Constraint violations/P4241
Proposal discussion	Proposal discussion
Current uses	Total 36,753 Main statement 5 <0.1% of uses Qualifier 36,698 99.9% of uses Reference 50 0.1% of uses
Search for values

[create Create a translatable help page (preferably in English) for this property to be included here]

Scope is as qualifier (Q54828449), as reference (Q54828450): the property must be used by specified way only (Help)

List of violations of this constraint: Database reports/Constraint violations/P4241#Scope, hourly updated report, SPARQL

Value type “term (Q1969448), temporal entity (Q26907166)”: This property should use items as value that contain property “instance of (P31), subclass of (P279)”. On these, the value for instance of (P31), subclass of (P279) should be an item that uses subclass of (P279) with value term (Q1969448), temporal entity (Q26907166) (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/P4241#Value type Q1969448, Q26907166, SPARQL

Allowed entity types are Wikibase item (Q29934200), Wikibase MediaInfo (Q59712033): 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/P4241#Entity types

This property is being used by: c:Module:Wikidata date Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

Accompanying qualifiers

Great we have this property now! Picking up the thoughts of Jheald and PKM I'd like to propose to declare adding of earliest date (P1319) and latest date (P1326) mandatory making this property an intermediate layer between those and object named as (P1932). The list of values for this property should be controlled anyway (no?) and I think we can find static rules to infer numerical dates from them and free the querying from that burden?
Unfortunately required qualifier constraint (Q21510856) only refers to the main statement I guess and we can't reuse it here, but perhaps a way to state that formally could be found.
@Jheald: Using inferred from (P3452) is interesting, what value shall it get, that used as value of stated in (P248) in a source? --Marsupium (talk) 16:16, 22 September 2017 (UTC)

I agree the list should be controlled, with consensus before making changes. I'm not sure about making earliest/latest mandatory - let me think that through. - PKM (talk) 19:27, 22 September 2017 (UTC)

To be honest during writing I became less sure than I was before about that, too. --Marsupium (talk) 06:47, 23 September 2017 (UTC)

Oh good, because I am reluctant to make that mandatory! If the sources give a date range, then we would use that of course. Otherwise we're assuming that "early 17th century" is the same as "earliest date=1600" when no source states that (and I can imagine a date of "early 17th century" that is emphatically after the ascension of James I, so 1603 or later...). If we could tag the qualifier as "inferred based on P4241" that would be different. - PKM (talk) 01:26, 24 September 2017 (UTC)

I think this system works in parallel to earliest date (P1319) / latest date (P1326) and it is based on what is found in sources. In most cases earliest date (P1319) / latest date (P1326) is more precise than this. By the way, I was busy last night creating items for allowed values. Please check those items and see if there are other properties we can add to them. --Jarekt (talk) 02:16, 24 September 2017 (UTC)

The list looks good. I just used it for the first time on Monogrammist E. D. (Q40912154). Now I need to find all the costume and art items where I wished I had this property! - PKM (talk) 20:34, 24 September 2017 (UTC)

Changed English description

I have changed the English description to eliminate "ISO", for the following reasons:

• My guess is that "ISO" refers to w:ISO 8601 but there are many ISO date formats, it is not a good practice to just write "ISO"

• Wikidata does not use the ISO 8601 format, it uses it's own format that resembles ISO 8601, but does not follow the same rules as ISO 8601.

• The Wikidata dateTime precision field has different rules than the precision rules for ISO 8601.

Other languages should have corresponding changes. Jc3s5h (talk) 18:11, 30 October 2017 (UTC)

I think this is reasonable. Thank you! --Marsupium (talk) 00:26, 7 November 2017 (UTC)