Wikidata:Properties for deletion/P5105

P5105 (P5105)

The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section. A summary of the conclusions reached follows.

Consensus to merge to class of station (P5606) and delete — Martin (MSGJ · talk) 20:59, 12 February 2022 (UTC)[reply]

P5105 (P5105): (delete | history | links | entity usage | logs)

I don't think we need a specialized property than class of station (P5606). GZWDer (talk) 21:46, 8 December 2019 (UTC)[reply]

Notified participants of WikiProject Railways and especially, because it's used by hu:Sablon:Állomás infobox, @B.Zsolt, Tacsipacsi: ^^ --Liuxinyu970226 (talk) 00:54, 10 December 2019 (UTC)[reply]

Delete after data migration. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:05, 10 December 2019 (UTC)[reply]

Keep Wikidata have lot of external identifiers, why need deletion? --B.Zsolt (talk) 13:31, 11 December 2019 (UTC)[reply]

Delete@B.Zsolt: Because there's a more useful identifier as replacement. --Liuxinyu970226 (talk) 14:53, 11 December 2019 (UTC)[reply]

Delete per Andy. This is an item property btw, not an external identifier property. Multichill (talk) 19:04, 12 December 2019 (UTC)[reply]

Delete after data migration. Robin van der Vliet (talk) (contribs) 00:43, 16 December 2019 (UTC)[reply]

Keep The general property explicitly says "use subproperties where available" and has constraints that conflict with their use. No apparent benefit to generalisation over specificity so data migration would just be makework. Thryduulf (talk) 14:27, 16 December 2019 (UTC)[reply]

Delete The specific property (P5105) is largely redundant to the general property (P5606). An argument could be made that the general property should be deleted instead and replaced with specific properties for each network, but here the relationship with the operator can be inferred from the station category items, so including the operator as part of the property is functionally unnecessary. Jc86035 (talk) 23:13, 16 December 2019 (UTC)[reply]

Keep per Thryduulf Michael FV (talk) 04:01, 9 January 2020 (UTC)[reply]
Keep clear scope. Enables reports with @Ivan_A._Krestinin:'s Krbot. --- Jura 11:04, 20 January 2020 (UTC)[reply]
Delete replacement available, no need to create any subproperties for anything that don't affect URL schemes. --117.136.54.109 23:22, 20 January 2020 (UTC)[reply]
Keep per above Germartin1 (talk) 09:55, 2 April 2020 (UTC)[reply]
@Jura1, Germartin1: "Enables reports with someone's bot" isn't a valid keep reason, we can ask them on Github to request cancelling their relative codes. --Liuxinyu970226 (talk) 00:49, 8 April 2020 (UTC)[reply]

Delete As values are only items, merge em back won't hurt anything. --223.104.7.115 22:11, 9 May 2020 (UTC)[reply]

Delete No need to fragment data into multiple properties. --Tinker Bell ★ ♥ 01:55, 25 October 2020 (UTC)[reply]

The above discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section.

Notes

Migrating data to class of station (P5606) ... — Martin (MSGJ · talk) 22:17, 14 February 2022 (UTC)[reply]
Done — Martin (MSGJ · talk) 21:04, 15 February 2022 (UTC)[reply]
Need to update hu:Sablon:Állomás infobox Y
Removing statements now — Martin (MSGJ · talk) 21:04, 15 February 2022 (UTC)[reply]
Deleted — Martin (MSGJ · talk) 21:43, 15 February 2022 (UTC)[reply]