Property talk:P5017
Documentation
- Start a query
- Current uses
- With precision and calendarmodel
- Statistics by class
- By century
- Date precision
- Calendar models
- List of qualifiers
- Count
date a reference was modified, revised, or updated
List of violations of this constraint: Database reports/Constraint violations/P5017#Scope, SPARQL
This property is being used by: Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.) |
|
Limitation
editWhy this is limited only for the references? Why this cannot be used e.g. for an update of an online article in the magazine? --Juandev (talk) 16:01, 7 September 2019 (UTC)
The property might be used for statements in the items like Farhad Fatkullin named Wikimedian of the Year for 2018 (Q66385139), Offline-Pedia converts old televisions into Wikipedia readers (Q66491069), Q67939617, Ceny za rozvoj české Wikipedie ve fotografii i jinak (Q67922512), The Czech Wikipedia has 150,000 articles (Q67200635) to identify the date of an update which is common for ditital works. So as there is a statement for creation (publication date (P577)) we need a statement for update. Thats why I would propose this property to wider its use and cover also as main value (Q54828448). --Juandev (talk) 19:53, 21 September 2019 (UTC)moved in a new section —Eihel (talk) 22:44, 21 September 2019 (UTC)
Major changes request to last update (P5017)
editMotivation
editThe property might be used for statements in the items like Farhad Fatkullin named Wikimedian of the Year for 2018 (Q66385139), Offline-Pedia converts old televisions into Wikipedia readers (Q66491069), Q67939617, Ceny za rozvoj české Wikipedie ve fotografii i jinak (Q67922512), The Czech Wikipedia has 150,000 articles (Q67200635) to identify the date of an update which is common for ditital works. So as there is a statement for creation (publication date (P577)) we need a statement for update. Thats why I would propose this property to wider its use and cover also as main value (Q54828448). --Juandev (talk) 19:53, 21 September 2019 (UTC)
Notified contributors of the initial discussion of the proposal —Eihel (talk) 22:46, 21 September 2019 (UTC)
- Notified contributors of the initial discussion of the proposal --Trade (talk) 07:10, 17 August 2020 (UTC)
Discussion
edit- The reason for restricting it to references is that doesn't make the statement invalid when the item is updated and wikidata is not aware of that update. It was suggested to use significant event (P793) to record updates to an item that don't already have a suitable property to describe them. ArthurPSmith (talk) 16:49, 23 September 2019 (UTC)
- Really? I would imagine more properties where the value could be updated and the Wikidata might not be aware of it. For example archive URL (P1065) and probably many others. How significant event (P793) could describe, what kind of event is it? --Juandev (talk) 17:37, 23 September 2019 (UTC)
- Probably like this? Q67939617#P793 Vojtěch Dostál (talk) 12:08, 29 September 2019 (UTC)
- Well, I wonder, how well be quering such values! Quering last update (P5017) sounds pretty intuitive, while this way Q67939617#P793. Not so much. Is it a goal of Wikidatiens to encode information, to be hardly discovered, or what is the point behind to try to find the solution, instead create of wider the property? --Juandev (talk) 12:57, 29 September 2019 (UTC)
- Querying is probably not a big issue (it is pretty easy: https://w.wiki/94Q). Predictability might be an issue, though. I am not against your proposal, I'm just explaining what ArthurPSmith meant. Vojtěch Dostál (talk) 16:01, 29 September 2019 (UTC)
- Querying is not a big issue for someone, who know SPARQL. I personally does not have time to learn SPARQL, so I dont understand your code at all. But thanks anyway. --Juandev (talk) 16:37, 29 September 2019 (UTC)
- @Juandev Yeah but Wikidata isn't primarily for people, it's a project to be read by machines or data scientists.Vojtěch Dostál (talk) 15:25, 6 October 2019 (UTC)
- Link? --Juandev (talk) 16:57, 6 October 2019 (UTC)
- @Juandev Yeah but Wikidata isn't primarily for people, it's a project to be read by machines or data scientists.Vojtěch Dostál (talk) 15:25, 6 October 2019 (UTC)
- Querying is not a big issue for someone, who know SPARQL. I personally does not have time to learn SPARQL, so I dont understand your code at all. But thanks anyway. --Juandev (talk) 16:37, 29 September 2019 (UTC)
- Querying is probably not a big issue (it is pretty easy: https://w.wiki/94Q). Predictability might be an issue, though. I am not against your proposal, I'm just explaining what ArthurPSmith meant. Vojtěch Dostál (talk) 16:01, 29 September 2019 (UTC)
- Well, I wonder, how well be quering such values! Quering last update (P5017) sounds pretty intuitive, while this way Q67939617#P793. Not so much. Is it a goal of Wikidatiens to encode information, to be hardly discovered, or what is the point behind to try to find the solution, instead create of wider the property? --Juandev (talk) 12:57, 29 September 2019 (UTC)
- Probably like this? Q67939617#P793 Vojtěch Dostál (talk) 12:08, 29 September 2019 (UTC)
- Really? I would imagine more properties where the value could be updated and the Wikidata might not be aware of it. For example archive URL (P1065) and probably many others. How significant event (P793) could describe, what kind of event is it? --Juandev (talk) 17:37, 23 September 2019 (UTC)