Wikidata:Property proposal/url text

url text edit

Originally proposed at Wikidata:Property proposal/Generic

   Not done
Description(qualifier) for "official website" (P856) statement when WMF settings prevent the URL from being used. Use "unknown" as main value
Data typeString
Example 1(theoretical sample)
Wikidata Sandbox (Q4115189)official website (P856)unknownurl textwww.example.com
Example 2LyricWiki (Q1198063)official website (P856)unknownurl textwww.lyricwiki.org
Example 3Wookieepedia (Q934052)official website (P856)unknownurl textstarwars.wikicities.com

Motivation edit

Settings would generally be the spam blacklist. This way users may retrieve it or not (Add your motivation for this property here.) --- Jura 11:49, 25 March 2021 (UTC)[reply]

Discussion edit

  Comment I see the need, but isn't there an existing qualifier we could use for this? object named as (P1932) maybe? ArthurPSmith (talk) 18:07, 25 March 2021 (UTC)[reply]
  Comment Besides object named as (P1932) another way to look at this through "internet eyes" that might work, Wikimedia Commons namespace (P2307), could be reused in a pinch here without breaking anything, since it's just String. Domains are indeed Namespaces https://en.wikipedia.org/wiki/Namespace --Thadguidry (talk) 19:54, 13 May 2021 (UTC)[reply]
  • I don't get that explanation. In general, properties (as any other entity on Wikidata) shouldn't be repurposed, so I don't see how we could use P2307. If you want to do an alternate proposal with that could include the above, I don't mind looking into it. --- Jura 20:13, 13 May 2021 (UTC)[reply]
  Strong oppose the url blacklist is designed to prohibit inclusion of certain urls, and while I understand that sometimes there is a valid need to report such urls, I don't think we should do it as a qualifier to an official website that is unknown, since it is known, and more importantly I don't think it should be available to add like this to then be retrieved as structured data easily - we don't want to report links that include outing, etc. Also, I can immediately imagine a gadget that reads these and converts them to links for the user, and that would allow effectively bypassing the blacklist - even if this isn't a gadget and users have to manually import a user script or something, it still allows circumventing the blacklist which is undesirable. --DannyS712 (talk) 01:23, 2 January 2022 (UTC)[reply]