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(a)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(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-l