Organize MediaWiki's catalog of 1000s of extensions using Wikidata. Is this a sensible idea? Reality checks and other opinions are welcome here or at
https://bugzilla.wikimedia.org/show_bug.cgi?id=46704#c33
Pasting the relevant part for convenience:
Has anybody discussed the possibility of creating Wikidata items for extensions, after defining a set of properties to describe them? Linking those Wikidata items to mediawiki.org extension pages, and then playing with templates and what not to keep the semantic data up to date (version number, last release, dependencies, compatible with MediaWiki releases...)? Then play with templates, queries and visualizations to create all kinds of useful output, from structured extension pages to a proper and robust map of extensions.
Hoi, I would seriously consider this for two reasons. Yes, we can include this kind of information, obviously. It is worthwhile information so that is one.
The most important reason why I want to seriously have this information is because the audience we gain. It is the developers of MediaWiki. They gain first hand experience and consequently they will start first to gain experience and use it and second start to consider it for what else Wikidata can do for them.
My blogpost about Commons and Wikidata was written exactly because Wikidata is not understood and considered by this most vital group for the further development of Wikidata and MediaWiki. Thanks, GerardM
http://ultimategerardm.blogspot.nl/2014/03/commons-and-wikidata-architecture...
On 20 March 2014 06:09, Quim Gil qgil@wikimedia.org wrote:
Organize MediaWiki's catalog of 1000s of extensions using Wikidata. Is this a sensible idea? Reality checks and other opinions are welcome here or at
https://bugzilla.wikimedia.org/show_bug.cgi?id=46704#c33
Pasting the relevant part for convenience:
Has anybody discussed the possibility of creating Wikidata items for extensions, after defining a set of properties to describe them? Linking those Wikidata items to mediawiki.org extension pages, and then playing with templates and what not to keep the semantic data up to date (version number, last release, dependencies, compatible with MediaWiki releases...)? Then play with templates, queries and visualizations to create all kinds of useful output, from structured extension pages to a proper and robust map of extensions.
-- Quim Gil Engineering Community Manager @ Wikimedia Foundation http://www.mediawiki.org/wiki/User:Qgil
Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
I would very strongly recommend to use Semantic MediaWiki for this use case. It is more powerful, we use SMW in other WMF contexts already, and supporting the data inside Meta (instead of inside Wikidata and then transcluding it) allows us also to generate workflows in Meta involving local User-accounts, etc., and reduces complexity since the data is saved in one place, and you don't have to switch between Meta and Wikidata to update the data for an extension. It also frees Wikidata for having have to extend their policies to support this specific use case (would MediaWiki extension developers all get their own item per Notability, etc.). Also, SMW already right now supports the uses cases you are asking for right now.
I understand that SMW was already suggested in Bugzilla. I understand Wikidata looks more sexy right now, but I think it is not the most appropriate tool for this use case.
Just my 2 cents.
On Wed Mar 19 2014 at 10:09:34 PM, Quim Gil qgil@wikimedia.org wrote:
Organize MediaWiki's catalog of 1000s of extensions using Wikidata. Is this a sensible idea? Reality checks and other opinions are welcome here or at
https://bugzilla.wikimedia.org/show_bug.cgi?id=46704#c33
Pasting the relevant part for convenience:
Has anybody discussed the possibility of creating Wikidata items for extensions, after defining a set of properties to describe them? Linking those Wikidata items to mediawiki.org extension pages, and then playing with templates and what not to keep the semantic data up to date (version number, last release, dependencies, compatible with MediaWiki releases...)? Then play with templates, queries and visualizations to create all kinds of useful output, from structured extension pages to a proper and robust map of extensions.
-- Quim Gil Engineering Community Manager @ Wikimedia Foundation http://www.mediawiki.org/wiki/User:Qgil _______________________________________________ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
<quote name="Denny Vrandečić" date="2014-03-20" time="16:06:46 +0000">
I would very strongly recommend to use Semantic MediaWiki for this use case. It is more powerful, we use SMW in other WMF contexts already,
Only on wikitech.wikimedia.org, and only until Ryan Lane figures out how to use Wikidata to manage the labs provisioning/etc :)
and supporting the data inside Meta (instead of inside Wikidata and then transcluding it) allows us also to generate workflows in Meta involving local User-accounts, etc., and reduces complexity since the data is saved in one place, and you don't have to switch between Meta and Wikidata to update the data for an extension. It also frees Wikidata for having have to extend their policies to support this specific use case (would MediaWiki extension developers all get their own item per Notability, etc.). Also, SMW already right now supports the uses cases you are asking for right now.
I understand that SMW was already suggested in Bugzilla. I understand Wikidata looks more sexy right now, but I think it is not the most appropriate tool for this use case.
Very useful points though.
I have no horse in this race, but I do want the best tool for the job to win.
Greg