Property talk:P1534

Documentation

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

end cause
qualifier to use together with the end date qualifier (P582) to specify the cause

Represents	end cause (Q22087155)
Data type	Item
Example	Benedict XVI (Q2494) → resignation (Q796919) Charlie Sheen (Q103939) → divorce (Q93190) Sara Danius (Q4944209) → dismissed (Q98404905) Kelly Preston (Q236842) → death of subject (Q99521170)
Robot and gadget jobs	DeltaBot does the following jobs: Move source to qualifier
Tracking: usage	Category:Pages using Wikidata property P1534 (Q98275742)
See also	end time (P582), has effect (P1542), has cause (P828)
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/P1534
Proposal discussion	Proposal discussion
Current uses	Total 191,013 Main statement 304 0.2% of uses Qualifier 190,693 99.8% of uses Reference 16 <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 main value (Q54828448): 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/P1534#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/P1534#Entity types

Item “end time (P582)”: Items with this property should also have “end time (P582)”. (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/P1534#Item P582, SPARQL

Value type “occurrence (Q1190554), cause (Q2574811), rule (Q1151067), era (Q6428674), fictional occurrence (Q14136353), compromise agreement (Q646381), human (Q5), occurrent (Q67518978)”: 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 occurrence (Q1190554), cause (Q2574811), rule (Q1151067), era (Q6428674), fictional occurrence (Q14136353), compromise agreement (Q646381), human (Q5), occurrent (Q67518978) (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/P1534#Value type Q1190554, Q2574811, Q1151067, Q6428674, Q14136353, Q646381, Q5, Q67518978, SPARQL

None of suspended account (Q111678787): value must not be any of the specified items.
Replacement property:
Replacement values: account suspension (Q87406427) (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/P1534#none of, SPARQL

Scope ?

I don't understand, it's supposed to be a qualifier for "end date", but the example is not at all consistent ???? author  TomT0m / talk page 18:31, 18 October 2015 (UTC)

• @TomT0m: The thing is that "end date" should be used also as a qualifier, so this property should be used with a property that has end date as a qualifier. Maybe in the example should be specified that the property has both qualifiers? -- Agabi10 (talk) 18:45, 18 October 2015 (UTC)
  • @Agabi10: Yes, AND a change in the descriptions, because the descriptions only says "qualifier for the property end date", which is wrong and uninformative on the usecases. Maybe something like "qualifier to use together with "end date" on a statement to state the cause for the end. author  TomT0m / talk page 18:50, 18 October 2015 (UTC)

"As main property" and "item requires statement constraint"

I added "as main property" (Q54828448) as "property scope constraint" (Q53869507) because "end cause" (P1534) should be allowed to be used as main property as "end time" (P582), which can be used as main property.
And I think that "P582 (end time) or P576 (dissolved, abolished or demolished date)" needs be added as "item requires statement constraint" (Q21503247). But I don't know how to express logical "or" (adding P582 and P576 to two separated Q21503247 means logical "and", but when I added both P582 and P576 to a single Q21503247, there was a warning that "the parameter 'property' must only have a single value"). So I added only P582 (end time) as "item requires statement constraint". --Neo-Jay (talk) 05:15, 26 December 2020 (UTC)

End cause having codomain constraint for types of "end cause"

@Gymnicus: I do not intend to edit war so let's start a discussion here for future documentation. Why do you think the end cause property should not have values that are end causes? --SilentSpike (talk) 10:07, 11 December 2021 (UTC)

Also to provide context previous value constraint item ("Wikidata reason for end cause") was deleted for not fitting our ontology: Wikidata:Requests_for_deletions/Archive/2021/07/28#Q66593009. Which brings me to reason that the values should be "real" end causes. In fact the constraint seems very trivially correct to me so I'm concerned by your undiscussed reversion. Can you point to an example of where it is applied incorrectly? SilentSpike (talk) 10:14, 11 December 2021 (UTC)

Also pinging users involved in deletion discussion of previous value item who may want to weigh in (always nice to have more opinions for consensus), @ChristianKl, Jura1, Emu, Wolverène: SilentSpike (talk) 10:18, 11 December 2021 (UTC)

@SilentSpike: Thanks for pinging me. Your edit seems fine to me but then again, I’m not a expert in value-type constraint (Q21510865) modeling. -- Emu (talk) 10:34, 11 December 2021 (UTC)

It's fine to add "end cause" (Q22087155) to value-type constraint. And I have changed "subclass of" (Q21514624) to "instance or subclass of" (Q30208840). --Neo-Jay (talk) 10:50, 11 December 2021 (UTC)

@Neo-Jay: Thank you for doing so, after stepping away I had the same thought (to clarify for anyone else: e.g. resignation of a specific figure being an instance of a resignation which is a generic end cause). SilentSpike (talk) 11:28, 11 December 2021 (UTC)

I just spotted this due to the generation of new constraint violations. On many human (Q5) items I have been setting military rank (P410) with an end cause (P1534) qualifier of promotion (Q574433). Alternative end causes are resignation (Q796919), demotion (Q464858), retirement (Q946865) and dismissal (Q17052147) (there are probably others but I can't think of them at the moment). Should all these be set with subclass of (P279) end cause (Q22087155)? From Hill To Shore (talk) 03:20, 12 December 2021 (UTC)

@From Hill To Shore, SilentSpike: To fix this problem, I have changed value-type constraint from "end cause" (Q22087155) to "occurrence" (Q1190554). Another solution is setting "occurrence" (Q1190554) to be a subclass of "end cause" (Q22087155). But I am afraid that it would not be appropriate. --Neo-Jay (talk) 16:17, 13 December 2021 (UTC)

@From Hill To Shore, Neo-Jay: How to correctly handle the class hierarchy for this has crossed my mind also, in a sense, any occurrence is an end cause of something (what came before). However, I'm also not confident enough in that reasoning to mark it as a subclass. This is something perhaps WikiProject Ontology has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead. could weight in on. SilentSpike (talk) 17:57, 13 December 2021 (UTC)