Hi, over the time the questions like "how do I determine programmatically the license of this image?" or "who is the author of that video? no, uploader's username is not enough" are asked quite regularly, and probably now it's time to fix this.
Please take a look here: https://www.mediawiki.org/wiki/Requests_for_comment/Image_information On that page, I'm trying to collect the requirements for extension that would address these problems, as well as the ways of implementation. If all goes well, I'd like to start coding in 1-2 weeks.
On Feb 25, 2013 9:27 AM, "Max Semenik" maxsem.wiki@gmail.com wrote:
Hi, over the time the questions like "how do I determine programmatically the license of this image?" or "who is the author of that video? no, uploader's username is not enough" are asked quite regularly, and probably now it's time to fix this.
I thought maybe this was a goal of Wikidata? Anyway, I'm sure I heard it mentioned in connection with Wikidata. Maybe at Wikimania in DC.
-Jeremy
On 25/02/13 15:26, Max Semenik wrote:
Hi, over the time the questions like "how do I determine programmatically the license of this image?" or "who is the author of that video? no, uploader's username is not enough" are asked quite regularly, and probably now it's time to fix this.
Please take a look here: https://www.mediawiki.org/wiki/Requests_for_comment/Image_information On that page, I'm trying to collect the requirements for extension that would address these problems, as well as the ways of implementation. If all goes well, I'd like to start coding in 1-2 weeks.
I believe it would be the best and easiest if Wikibase extension would be reappropriated for this. Basically the only thing needed is new data editing interface that would be active in the File namespace.
Hi!
There is a related page at https://www.mediawiki.org/wiki/Files_and_licenses_concept
Helder
On Mon, Feb 25, 2013 at 11:26 AM, Max Semenik maxsem.wiki@gmail.com wrote:
Hi, over the time the questions like "how do I determine programmatically the license of this image?" or "who is the author of that video? no, uploader's username is not enough" are asked quite regularly, and probably now it's time to fix this.
Please take a look here: https://www.mediawiki.org/wiki/Requests_for_comment/Image_information On that page, I'm trying to collect the requirements for extension that would address these problems, as well as the ways of implementation. If all goes well, I'd like to start coding in 1-2 weeks.
-- Best regards, Max Semenik ([[User:MaxSem]])
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
While I understand that wikibase would be 'ideal' (allowing reads *and* writes), I do not know if the WikiData people have the personell bandwidth to do that. The separate extension outlined in this RFC would be a bit hackish, but still faaar more efficient than the current solution of having to retrieve the HTML and parse it again (or worse, parse the Wikitext itself). Would also be incredibly more efficient to get the data for multiple images, since you could feed a generator into this.
+1 for implementing this now :)
I certainly don't want to cookie-lick this usecase for Wikidata / Wikibase, but I think that using the Wikibase extension for this might be easier than it looks. The one major point would be a bit of coding to allow claims for the media namespace. But indeed, right now we do not have the bandwidth to do this, and if we are to work on it, it would be deferred to the Summer (the design can be started earlier, obviously).
On the other hand, as said, we don't want to cookie-lick the usecase: if there is a quick way to implement it, it is also obviously clear that moving well-defined structured data from one system to the other is far easier than the original creation of that structured data, and thus inefficient use of human work would be minimized anyway. As long as we are creating such well-defined structured data, I am happy either way.
2013/3/10 Yuvi Panda yuvipanda@gmail.com
While I understand that wikibase would be 'ideal' (allowing reads *and* writes), I do not know if the WikiData people have the personell bandwidth to do that. The separate extension outlined in this RFC would be a bit hackish, but still faaar more efficient than the current solution of having to retrieve the HTML and parse it again (or worse, parse the Wikitext itself). Would also be incredibly more efficient to get the data for multiple images, since you could feed a generator into this.
+1 for implementing this now :)
-- Yuvi Panda T http://yuvi.in/blog _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
On Mon, Mar 11, 2013 at 4:52 AM, Denny Vrandečić denny.vrandecic@wikimedia.de wrote:
I certainly don't want to cookie-lick this usecase for Wikidata / Wikibase, but I think that using the Wikibase extension for this might be easier than it looks. The one major point would be a bit of coding to allow claims for the media namespace. But indeed, right now we do not have the bandwidth to do this, and if we are to work on it, it would be deferred to the Summer (the design can be started earlier, obviously).
Go ahead and lick the cookie for the long-term -- we'll happily eat a smaller cookie in the short term. :)
This structured data really does belong in Wikidata. But for now we just need a way to query this info that already exists using templated microformats, and preferably in a simple server-side way that keeps us from having to reimplement all the parsing on multiple platforms.
On the other hand, as said, we don't want to cookie-lick the usecase: if there is a quick way to implement it, it is also obviously clear that moving well-defined structured data from one system to the other is far easier than the original creation of that structured data, and thus inefficient use of human work would be minimized anyway. As long as we are creating such well-defined structured data, I am happy either way.
*nod*
-- brion
wikitech-l@lists.wikimedia.org