Wikidata:Property proposal/has forks

From Wikidata
Jump to navigation Jump to search

‎has forks

[edit]

Return to Wikidata:Property proposal/Computing

   Under discussion
DescriptionNotable software forks of this software
Representsfork (Q332903)
Data typeItem
Example 1youtube-dl (Q28401317) has forks: yt-dlp (Q108454371)
Example 2Visual Studio Code (Q19841877) has forks: VSCodium (Q111967621)
Example 3OpenOffice.org (Q511977) has forks: LibreOffice (Q10135)
Example 4Firefox (Q698) has forks: LibreWolf (Q105623664)

Motivation

[edit]

Currently, which notable/used forks a software has and which software was originally forked from (and also when) is either not specified or using the based on property. A bot/script could populate this standardized property. I think it would be useful but many items for notable forks are still missing (there wasn't even one for VSCodium). For example, one could query for all notable forks created in some year or have a software's forks linked at a page about the respective software which can be useful e.g. to people using that software.

based on (Property:P144) is ambiguous and using instance of with an of qualifier is even less usable. I don't know if I can propose two properties at once but if so I'd also like to propose property is fork of and if not would like to propose that later on if nobody else does.

Previous discussion (1 reply).

--Prototyperspective (talk) 17:38, 1 October 2024 (UTC)[reply]

Discussion

[edit]
  •  Conditional support I agree with @Dexxor: from the previous discussion that the inverse "is fork of" would be better for this data. -wd-Ryan (Talk/Edits) 00:26, 2 October 2024 (UTC)[reply]
    The thing is I think both are needed and useful. On a page about some software (it doesn't have to be a Wikipedia page), a way to view all forks of this software would often be useful and querying that data via the has forks property seems like the best way and it would then be also included in the respective Wikidata item. This is similar to e.g. the has parts and part of properties: it needs both except if the second item somehow gets this info added as well dynamically if it's added to the other (currently bots may do this for such dual properties). Prototyperspective (talk) 10:50, 2 October 2024 (UTC)[reply]
  •  Oppose as "has fork"; would support as "is fork of" per Wd-Ryan. Mahir256 (talk) 17:03, 2 October 2024 (UTC)[reply]
    Why not both? Forks are useful information at the respective software just as much as the info what software a given software was forked from. Making a new query for every software on some page which forks it has may not be possible but one could also fetch the has forks values. Why is there an inverse for has part Property:P527 part of Property:P361? Same reasons apply here too. Prototyperspective (talk) 21:04, 2 October 2024 (UTC)[reply]