If we believe Wikidata and structured data is the way forward though I think we should `be strong` [1] and help lead the community in this direction.
I think mobile could be a safe place to test this, and to respond to community desires and need for customisation of infoboxes and at the same time increase the growth and success of Wikidata.
I am wearing my 'be optimistic' t-shirt today... :)
([1] my take on `be bold` - the <b> tag took on new meaning in HTML5 and I think it's meaning is a little deprecated in the wiki sense and needs updating ;-))
On Tue, Aug 12, 2014 at 3:56 PM, Derk-Jan Hartman d.j.hartman+wmf_ml@gmail.com wrote:
It is problematic, because of two things:
1: you take away editorial control from the community (what fact gets shown and what doesn't and for what reasons). you will have to work on providing editorial controls to do basic manipulation of this. 2: Editors can no longer override WikiData, which is a separate community. You will have to work on bridging the interaction gap between those two sites (we see similar problems with Commons, though they have been mild by stuff "just being an image".
DJ
On 13 aug. 2014, at 00:17, Monte Hurd mhurd@wikimedia.org wrote:
+1 Jon
On Aug 12, 2014, at 10:44 PM, Jon Robson jdlrobson@gmail.com wrote:
Infoboxes cause a huge problem on mobile and I've been asking us to be guinea pigs for this sort of thing.
I would like mobile to scrub infoboxes and then generate them in a more appropriate place in the UI using Wikidata. I was told this would be controversial though...
On Tue, Aug 12, 2014 at 2:26 PM, Amir E. Aharoni amir.aharoni@mail.huji.ac.il wrote:
Just an idea inspired by Brandon's Wikimania talk and some discussions at Wikidata-L: We can completely remove infobox templates. More precisely, the templates may stay, but the code that places them in the article can be removed.
Let me explain: Wikidata makes it possible to write an infobox without any parameters - just {{Infobox settlement}} without any |, = and all that. Wikidata even has a property called "infobox's main topic", a kind of "meta-property" that can automatically identify which infobox does the article need, so that you can simply say something like {{Infobox}}. This is implemented in the Russian Wikipedia using https://ru.wikipedia.org/wiki/Module:Universal_infocard , which is used on hundreds of articles there. So it hasn't replaced the usual templates yet, but the theoretical possibility is there.
Thus, the only thing left to the editor's discretion is where to place the infobox.
This, however, can be handled by Winter. Winter puts infobox-like information on the info rail*, and if we plan to be bold enough to take it completely out of the article's prose flow, why not just remove it from the article completely? If an article has an appropriate infobox template, it is shown on the info rail, and that is it. (The Community will then ask for the __NOINFOBOX__ magic word, but that's a minor thing.)
Thoughts?
- That's how I call the "right rail" until there is consensus on a better
name. See http://lists.wikimedia.org/pipermail/design/2014-August/001897.html
-- Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי http://aharoni.wordpress.com “We're living in pieces, I want to live in peace.” – T. Moore
Design mailing list Design@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/design
-- Jon Robson
Design mailing list Design@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/design
Design mailing list Design@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/design
Design mailing list Design@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/design