Wikidata:Property proposal/official list URL
official list URL edit
Originally proposed at Wikidata:Property proposal/Generic
Description | URL of a website listing instances of the subject, maintained by the authority on the subject |
---|---|
Data type | URL |
Example 1 | Unicode character (Q29654788)official list URLhttps://www.unicode.org/charts/charindex.html |
Example 2 | Request for Comments (Q212971)official list URLhttps://www.rfc-editor.org/rfc-index.html |
Example 3 | W3C Technical Report (Q115616700)official list URLhttps://www.w3.org/TR/ |
Example 4 | W3C Recommendation (Q2661442)official list URLhttps://www.w3.org/TR/?status=REC |
Example 5 | Discord server (Q63198389)official list URLhttps://discord.com/servers |
Motivation edit
The proposed property would be helpful for data consumers who want to find the official list of instances of a given data item. Furthermore the property could probably be used to compute the coverage of Wikidata of a given class via web scraping.
--Push-f (talk) 10:37, 6 December 2022 (UTC)
Discussion edit
- Notified participants of WikiProject Websites. --Push-f (talk) 10:39, 6 December 2022 (UTC)
- Support. Nomen ad hoc (talk) 10:41, 6 December 2022 (UTC).
- Oppose official website (P856) seems to do the job well enough, and you could add some qualifier to indicate that it points to a list. ChristianKl ❪✉❫ 14:16, 6 December 2022 (UTC)
- @ChristianKl: What does "well enough" mean? Couldn't the same be said for any "URL" property? ... just use URL (P2699) and a qualifier? Besides can you suggest a concrete qualifier to use? Sidenote: Do you realize that we have official blog URL (P1581), official shop URL (P10225), official forum URL (P10027), official map URL (P9601) and official demo URL (P11201)? "official list URL" is likely to be applicable to more items than most of these, so why shouldn't it get its own property? --Push-f (talk) 19:57, 6 December 2022 (UTC)
- Oppose for exactly the reasons Push-f specifies, above, that URLs serving different purposes do not need tailored properties. Let's not compound this mistake by adding yet another. Those relatively few items that might use the proopsed property will as easily take official website (P856) and optionally a qualifier. --Tagishsimon (talk) 21:24, 3 January 2023 (UTC)
- There absolutely should be properties for URLs serving different purposes. A privacy policy, for example, would not be suitable for official website (P856), but still important information to document. -wd-Ryan (Talk/Edits) 23:12, 3 January 2023 (UTC)
- Oppose official website (P856) seems to do the job well enough, and you could add some qualifier to indicate that it points to a list. ChristianKl ❪✉❫ 14:16, 6 December 2022 (UTC)
- Is Discord server (Q63198389) → https://discord.com/servers back on the table? -wd-Ryan (Talk/Edits) 06:00, 9 December 2022 (UTC)
- Yes! Added it as an example :) --Push-f (talk) 06:52, 9 December 2022 (UTC)
- Support -wd-Ryan (Talk/Edits) 16:19, 9 December 2022 (UTC)
- Yes! Added it as an example :) --Push-f (talk) 06:52, 9 December 2022 (UTC)
- Support Laftp0 (talk) 15:47, 9 December 2022 (UTC)
- Support ―BlaueBlüte (talk) 09:21, 31 January 2023 (UTC)
- @Push-f, Nomen ad hoc, Laftp0, BlaueBlüte: Done. --Tinker Bell ★ ♥ 23:13, 31 January 2024 (UTC)