Wikidata:Property proposal/inverse label

inverse label item

Originally proposed at Wikidata:Property proposal/Generic

Done: inverse label item (P7087) (Talk and documentation)

Description	item with labels of the inverse relationship of a property
Data type	Item
Domain	properties with item datatype
Example 1	instance of (P31) → item with label "has instance" (en)
Example 2	subclass of (P279) → item with label "superclass of" (en)
Example 3	place of birth (P19) → item with label "born here" (en)

Motivation

While some properties have an inverse property it is unlikely that we will ever have for all properties with item datatype an inverse. Nevertheless, some tools display inverse relationships even if an explicit inverse property is missing, e.g. reasonator, sqid, derivedstatements. In future, such a functionality could even be implemented in Wikidata itself. To improve these tools it would be good to store the label of the inverse relationship on the property page, see examples above. --Pasleim (talk) 17:03, 14 January 2019 (UTC)[reply]

Discussion

On problem of this solution is that we might end up with 20 values in different languages. That takes up space. Additionally if we need qualifiers we have to copy them again for every language. WikiProject Properties has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead.ChristianKl ❪✉❫ 09:40, 16 January 2019 (UTC)[reply]

I agree that this will take up some space but I don't think this is sever. Property pages like Europe PlayStation Store ID (P5971) and Wolfram Language entity code (P4839) have far more statements. --Pasleim (talk) 10:05, 16 January 2019 (UTC)[reply]

On space - is this what the proposed "multilingual text" datatype was supposed to cover? It does seem like it would be sensible to allow a property to have values that work like the label and description values, allow for one string value in each language. ArthurPSmith (talk) 18:27, 16 January 2019 (UTC)[reply]

Yes, that was the point of the "multilingual text" datatype that we still don't have. ChristianKl ❪✉❫ 19:20, 17 January 2019 (UTC)[reply]

We would probably also want to be able to store inverse aliases. Maybe each property should just have a dedicated item for storing inverse name data? --Yair rand (talk) 00:52, 21 January 2019 (UTC)[reply]
- That's a great idea - 'inverse item' rather than 'inverse label'? ArthurPSmith (talk) 17:35, 22 January 2019 (UTC)[reply]
  - Sounds good to me. --Pasleim (talk) 10:00, 23 January 2019 (UTC)[reply]
  - Support. updated it accordingly --- Jura 11:17, 3 March 2019 (UTC)[reply]
  - tweaked label/description it a bit further. --- Jura 11:53, 10 March 2019 (UTC)[reply]

@Pasleim, ChristianKl, ArthurPSmith, Jura1, Yair rand: Done: inverse label item (P7087). − Pintoch (talk) 21:30, 23 July 2019 (UTC)[reply]