I think no one would disagree that the current viewing experience on the main wikidata.org interface is not ideal. Keep in mind though that this is fundamentally an impossible UI task. There are many many different ways that the data about an item in wikidata might be best used/viewed depending on who is doing the viewing and why. Having the same interface attempt to support viewing data about astronomy and art history is just never going to be great for either. While I applaud and encourage the ongoing development of the default interface, I think it would benefit the community to think past that interface to the kinds of purpose built wikidata-driven applications that serve and benefit from specific communities. Anything we can do to make it easier for people to build good apps (in addition to those in the MediaWiki family) that read and write to wikidata could have a huge impact on its ultimate impact.
One of the things that freebase (RIP) did in this regard was the Acre [1] hosted development environment. While clearly it didn't tip the balance for them, I think it was a powerful idea that we could probably learn from. -Ben [1] http://wiki.freebase.com/wiki/Acre On Tue, May 3, 2016 at 6:37 AM, Gerard Meijssen <[email protected]> wrote: > Hoi, > For several years the Reasonator has done a stellar job. It is much better > at providing information based on the Wikidata data. > > It just does not have a priority to provide an interface like this. The > beauty of the Reasonator that it can easily provide you the same > information in other languages.. > Thanks, > GerardM > > > https://tools.wmflabs.org/reasonator/?q=Q181 > https://tools.wmflabs.org/reasonator/?q=Q181&lang=ru > https://tools.wmflabs.org/reasonator/?q=Q181&lang=ar > https://tools.wmflabs.org/reasonator/?q=Q181&lang=sv > > On 3 May 2016 at 13:07, David Abián <[email protected]> wrote: > >> Hi, >> >> I think that most elements on Wikidata are nowadays too long to be >> easily read by humans. There are many properties (which is great), the >> information is too scattered, and this problem (if you consider it a >> problem) will continue growing up. >> >> Some suggestions come to mind... >> >> * Visually group properties by type, using the division of >> <https://www.wikidata.org/wiki/Wikidata:Property_proposal>, or another. >> >> * Change our current CSS rules to show properties in a more compacted way. >> >> * Create a table of contents that automatically appears when more than N >> properties have been defined for an element. >> >> * Combine some of the above. >> >> Is there something discussed/planned facing this issue? >> >> Regards, >> >> -- >> David Abián - davidabian.com >> Vocal de Comunicación >> >> Wikimedia España >> Vega Sicilia, 2 >> 47008 - Valladolid >> https://wikimedia.es >> >> Wikimedia España es una asociación sin ánimo de lucro española con >> CIF G-10413698 inscrita en el Registro Nacional de Asociaciones, >> Grupo 1, Sección 1, Núm. Nacional 597390. >> >> «Imagina un mundo en el que cada persona >> tenga acceso libre a todo el conocimiento». >> >> _______________________________________________ >> Wikidata mailing list >> [email protected] >> https://lists.wikimedia.org/mailman/listinfo/wikidata >> > > > _______________________________________________ > Wikidata mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/wikidata > >
_______________________________________________ Wikidata mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata
