Wikidata:Property proposal/has reply

has reply

Originally proposed at Wikidata:Property proposal/Generic

   Not done

Description	MISSING
Represents	has reply (Q81643498)
Data type	Item
Domain	item
Example 1	Electromagnetic fields, polychlorinated biphenyls, and prostate cancer mortality in electric utility workers. (Q47971604) → Re: "Electromagnetic fields, polychlorinated biphenyls, and prostate cancer mortality in electric utility workers" (Q24351894)
Example 2	Re: "Electromagnetic fields, polychlorinated biphenyls, and prostate cancer mortality in electric utility workers" (Q24351894) → Re: Electromagnetic fields, polychlorinated biphenyls, and prostate cancer mortality in electric utility workers - reply (Q23917168)
Example 3	The Phylogenetic Paradigm of Comparative Biology: A Response to Hedberg (Q28958081) → Reply to Neil Snow's "The Phylogenetic Paradigm of Comparative Biology" (Q28958082)
Expected completeness	always incomplete (Q21873886)
See also	reply to (P2675)
Single-value constraint	no
Distinct-values constraint	no

Motivation

We should make a inverse property of reply to (P2675). Sharouser (talk) 15:48, 11 October 2022 (UTC)

Discussion

•  Oppose @Sharouser: Wikidata in general does not need inverse properties. There is a script or gadget that can display inverse relations if needed. ArthurPSmith (talk) 20:25, 13 October 2022 (UTC)
•  Oppose per ArthurPSmith. Inverse properties are not created just for the sake of having an inverse property, but rather only if they are of meaningful value for modelling. --Nw520 (talk) 08:51, 14 October 2022 (UTC)

  @Nw520: Could you mention examples of inverse properties being meaningful for modelling? -- Rdrg109 (talk) 17:55, 16 October 2022 (UTC)

  Generally, in cases where the relationship is notable only in one direction and not the other and that can happen in both directions.  Oppose to the proposal. ChristianKl ❪✉❫ 12:47, 26 November 2022 (UTC)

•  Not done no support for creation of this property --DannyS712 (talk) 01:06, 3 December 2022 (UTC)