Totally agree about the wikidata interface convenience, but I suspect it might not cover all usages, in which case it will be a good way for users to start implementing workarounds, and for us to notice the need and meet it with new features.
I don't know enough about template performance impact, although I do hope that a low-limit API call does not impact much more than a complex template with many links/templates/categories. In any case, lets put this on back-burner for later evaluation. On Mon, Feb 18, 2013 at 7:29 AM, Tim Starling <tstarl...@wikimedia.org>wrote: > On 18/02/13 23:24, Yuri Astrakhan wrote: > > How useful would it be for Lua to access to the query/content/parser API > be? > > > > I am suspecting there could be a lot of creative usages of this, > including > > getting data from the wikidata (which won't have to do anything special > to > > enable this) > > If you provided full access to ApiQuery*, resource limiting would be > fairly difficult, since it provides lots of ways to do unlimited table > scanning regardless of result set size. As for the Wikidata > application -- the interface would be awkward compared to something > made specifically for interfacing Wikidata with Lua. > > -- Tim Starling > > > _______________________________________________ > Wikitech-l mailing list > Wikitech-l@lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/wikitech-l > _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
