Baking domain knowledge (e.g. about the relationship between bands and members) into the software is not a good thing. In fact, it's pretty horrible. If you can suggest a way to do what you want without hard-coding domain knowledge (e.g. by lettign the software "know" what certain properties "mean"), please do, I'd be very interested.
In general, making the software "smart" requires it to be less flexible for users. If the software is to make assumptions, it also has to enforce these assumptions, taking away freedom. That's the opposite of the wiki principle.
Am 10.12.2014 07:10, schrieb Ricordisamoa:
I think the redirects issue has been raised here to make up for the poor Wikidata-Wikipedia integration we currently have. I imagine Winter showing a list of "related articles in other languages". Reusing one of the examples: when viewing [[en:Rob Bourdon]], the software should infer from [[d:Q19205]] that Rob Bourdon is /member of/ Linkin Park (Q261), for which the German Wikipedia has an article, that will in turn be linked. Very little brain work is needed to understand that the German article about the band is likely to contain information about individual members. While this may sound Reasonator-ish, if correctly implemented in Wikibase it could improve interlanguage and interproject links in a way that just cannot be achieved with redirects. Imagine the Wikipedia entries for "Linkin Park" linking (pun intended) to Wikiquote entries of each member.
Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l