Property talk:P1581
This property was previously considered for deletion but kept. |
Documentation
URL to the blog of this person or organization
Description | URL to the blog of this person or organization | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Represents | official blog (Q41557148) | ||||||||||||
Has quality | official (Q29509043) | ||||||||||||
Data type | URL | ||||||||||||
Corresponding template | Template:Official blog (Q14937496) | ||||||||||||
Domain | Persons, businesses (note: this should be moved to the property statements) | ||||||||||||
Allowed values | According to this template:
URL (Q42253) of the official blog
According to statements in the property:
When possible, data should only be stored as statementshttps?://(\S+\.)+\S+(/\S*)? | ||||||||||||
Example | According to this template:
According to statements in the property:
When possible, data should only be stored as statementsJohn Green (Q630446) → http://fishingboatproceeds.tumblr.com Gil Garduño (Q18198625) → http://www.nmgastronome.com Google (Q95) → https://blog.google/ White House (Q35525) → http://www.whitehouse.gov/blog National Indigenous Knowledge and Language Alliance (Q112289343) → https://www.nikla-ancla.com/blog | ||||||||||||
Robot and gadget jobs | Perhaps a bot could search a URL for its feed, for Tumblr and Wordpress this would be simple to set up. | ||||||||||||
Tracking: differences | Category:Official blog different in Wikidata and Wikipedia (Q21987742) | ||||||||||||
Tracking: usage | Category:Pages using Wikidata property P1581 (Q21798002) | ||||||||||||
Tracking: local yes, WD no | Category:Official blog not in Wikidata (Q21987781) | ||||||||||||
See also | official website (P856), web feed URL (P1019), house publication (P2813), official wiki URL (P12203) | ||||||||||||
Lists |
| ||||||||||||
Proposal discussion | Proposal discussion | ||||||||||||
Current uses |
| ||||||||||||
Search for values |
List of violations of this constraint: Database reports/Constraint violations/P1581#Unique value, SPARQL (every item), SPARQL (by value)
https?://(\S+\.)+\S+(/\S*)?|
”: value must be formatted using this pattern (PCRE syntax). (Help)List of violations of this constraint: Database reports/Constraint violations/P1581#allowed qualifiers, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P1581#mandatory qualifier, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P1581#Entity types
List of violations of this constraint: Database reports/Constraint violations/P1581#Scope, SPARQL
Pattern ^https?://(www\.)?plus\.google\.com/(\d{21}|\+[-\w_À-ÿА-я]+|communities/\d{21})(/(about(\?hl=en)?)?)?$ will be automatically replaced to \2 and moved to Google+ ID (P2847) property. Testing: TODO list |
Pattern ^https?://(www\.)?twitter\.com/([A-Za-z0-9_]{1,15})/?$ will be automatically replaced to \2 and moved to X username (P2002) property. Testing: TODO list |
Pattern ^https?://(www\.)?instagram\.com/([a-z0-9_\.]+)/?$ will be automatically replaced to \2 and moved to Instagram username (P2003) property. Testing: TODO list |
Pattern ^https?://(www\.)?youtube\.com/channel/(UC([A-Za-z0-9_\-]){22})/?$ will be automatically replaced to \2 and moved to YouTube channel ID (P2397) property. Testing: TODO list |
Pattern ^https?://(www\.)?vk\.com/([A-Za-z0-9_\.]{2,32})/?$ will be automatically replaced to \2 and moved to VK ID (P3185) property. Testing: TODO list |
Pattern ^https?://(www\.)?linkedin\.com/in/([\-\&%A-Z0-9a-záâãåäăąćčçéèêěëğîıíłńñøóòôöõřśşșšțúůüýž]+)/?$ will be automatically replaced to \2 and moved to LinkedIn personal profile ID (P6634) property. Testing: TODO list |
Pattern ^https?://(www\.)?([^\s\/]+)\.tumblr\.com/?$ will be automatically replaced to \2 and moved to Tumblr username (P3943) property. Testing: TODO list |
Pattern ^https?://(www\.)?ameblo\.jp/([a-z0-9-]{3,24})/?$ will be automatically replaced to \2 and moved to Ameblo username (P3502) property. Testing: TODO list |
Pattern ^https?://(www\.)?medium\.com/([A-Za-z0-9_\.]{1,30})/?$ will be automatically replaced to \2 and moved to Medium username (P3899) property. Testing: TODO list |
Pattern ^https?://(www\.)?lineblog\.me/([a-z0-9_]+)/?$ will be automatically replaced to \2 and moved to Line Blog user ID (P7211) property. Testing: TODO list |
Pattern ^https?://note\.com/([\da-z_]+)/?$ will be automatically replaced to \1 and moved to note.com user ID (P11401) property. Testing: TODO list |
Reports:
Single value
[edit]Why single-value constraint (Q19474404)? Lluís Ciprés i Paltre (Q61827018) has two blogs. --Davidpar (talk) 13:10, 23 February 2019 (UTC)
- @Davidpar: Agree, removed. --Marsupium (talk) 14:43, 22 March 2020 (UTC)
Please discuss changes to properties before making them.
[edit]@Trade, Valentina.Anitnelav, Trivialist: From Help:Properties#Editing_properties "Major changes to a property should be discussed on its talk page first.". Currently this property has a mandatory qualifier constraint introduced in 2020 without discussion as far as I can see. Please can you revert it to what it was before and if you want to change it discuss it here first. Iwan.Aucamp (talk) 12:14, 22 May 2020 (UTC)
WikiProject Informatics has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead.
Make archive URL non-mandatory
[edit]Having archive URL (P1065) as a required qualifier constraint (Q21510856) encourages editors to add pointless https://web.archive.org/web/*/$1
URLs as qualifiers. However, these archive URLs could be machine-generated for any URL. Archive URLs only make sense if you want to link to a page at a specific point in time, for example the last date before the site went down. Therefore archive URLs are useless for sites that are alive (nobody wants to constantly update the archive URL).
What is the reasoning behind the constraint, @User:Trade? — Dexxor (talk) 16:59, 23 May 2020 (UTC)
- But we do don't have any bot to add machine-generated Arhive URL's to reference URL's. I like the constrwint as a way to future proof URL's. @Dexxor:--Trade (talk) 20:51, 30 May 2020 (UTC)
- Ok, I’m fine with keeping the suggestion to add an archive URL because it reminds us that sites can go down anytime. Though, I will definitely not add something like
https://web.archive.org/web/20200530022744/http://www.example.com/
and update the timestamp every time there is a new blog post. It would be nicer to addhttps://web.archive.org/web/*/https://www.example.com
but that link does not pass the regex and it would be like saying "wet water". The "wet" does not add any information because all water is wet. The same goes for addinghttps://web.archive.org/web/*/$1
as the archive URL to$1
where$1
is the blog URL (that is what I meant when I said it could be machine-generated). — Dexxor (talk) 21:58, 30 May 2020 (UTC)
- Ok, I’m fine with keeping the suggestion to add an archive URL because it reminds us that sites can go down anytime. Though, I will definitely not add something like
- Properties for deletion
- All Properties
- Properties with url-datatype
- Properties used on 10000+ items
- Properties with unique value constraints
- Properties with format constraints
- Properties with qualifiers constraints
- Properties with conflicts with constraints
- Properties with required qualifiers constraints
- Properties with entity type constraints
- Properties with scope constraints