Am 10.12.2014 13:47, schrieb Adrian Lang: > depends on what you consider ›the software‹. From my point of view, a > software is there to solve domain-specific problems, and as such, has > to have domain knowledge. Otherwise, it's useless. The question is, > which software solves which problem, and which problems are not solved > at all or solved by humans. Wikibase generally shouldn't know about > Wikidata's content. That doesn't mean that no software may know about > it; in fact, some gadgets know a lot about it, and tools do so, too. I > think there is a case for having domain knowledge in PHP code on the > servers, too.
I agree with your general point: we could have an extension or gadget or whatever on top of Wikibase that holds (some) domain specific knowledge about the properties used on wikidata.org. If that knowledge is coded into an extension that needs code review and deployments to be updated, we have to be aware that it's not going to be very flexible. The question is then how to manage the configuration and update of that bit of softare. In general, that kind of thing is more easily done with JS or Lua, since it's under the direct control of the local wiki community. I kind of like the idea of making our Lua integration more powerful, so it could be used to manipulate the skin and talk to the API, not just generate article content. -- Daniel Kinzler Senior Software Developer Wikimedia Deutschland Gesellschaft zur Förderung Freien Wissens e.V. _______________________________________________ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
