Revision as of 20:21, 13 May 2013 editPigsonthewing (talk | contribs)Autopatrolled, Event coordinators, Extended confirmed users, Page movers, File movers, IP block exemptions, New page reviewers, Pending changes reviewers, Rollbackers, Template editors266,225 edits →Infobox: c← Previous edit |
Revision as of 20:24, 13 May 2013 edit undoPigsonthewing (talk | contribs)Autopatrolled, Event coordinators, Extended confirmed users, Page movers, File movers, IP block exemptions, New page reviewers, Pending changes reviewers, Rollbackers, Template editors266,225 editsm →Infobox: ceNext edit → |
Line 29: |
Line 29: |
|
::Hi RexxS, likewise thank you for your polite and respectful post, I really wouldn't expect anything less from you. As I said to Andy, I am not opposed to infoboxes on certain articles and can see the use of them on those articles which require a lot of information about that particular subject. However, I do oppose them on biographies as I don't really see the encyclopaedic value in explaining to a reader who so and so's non notable siblings were and what their religion was, who they supported in politics, where they got married, etc... They are also bloody ugly to boot, especially on short stubs such as this. They interfere with the first image (if there is one), often sandwiching the preceding text as a result. |
|
::Hi RexxS, likewise thank you for your polite and respectful post, I really wouldn't expect anything less from you. As I said to Andy, I am not opposed to infoboxes on certain articles and can see the use of them on those articles which require a lot of information about that particular subject. However, I do oppose them on biographies as I don't really see the encyclopaedic value in explaining to a reader who so and so's non notable siblings were and what their religion was, who they supported in politics, where they got married, etc... They are also bloody ugly to boot, especially on short stubs such as this. They interfere with the first image (if there is one), often sandwiching the preceding text as a result. |
|
::I really don't have a clue about the technical side of them, so I trust you implicitly in what you say here. I think SchroCat has fixed the problem perfectly with his capped version and I fully support this. In fact, quite why this hasn't been implemented accross WP, I don't know! I think adding an infobox is a big edit to make and it would only be polite to post the intension on the talk page prior to adding it. It is a bit like adding a <nowiki>{{wait}}</nowiki> tag before doing a big edit, as I think it is proper to warn people that I am in the process of structuring a large edit. Likewise, If I start a big project which I plan on taking to FAC, I build it in my sandbox and then post a message on the talk page asking if anyone agrees or opposes me moving what I have done accross to the mainspace. If I don't hear anything within a week I go ahead with the move. Anyway, great to hear from you and I await your thoughts on SchroCat's idea. --'''<span style="text-shadow:7px 7px 8px Black;">]<sup>]</sup></span>''' 18:55, 13 May 2013 (UTC) |
|
::I really don't have a clue about the technical side of them, so I trust you implicitly in what you say here. I think SchroCat has fixed the problem perfectly with his capped version and I fully support this. In fact, quite why this hasn't been implemented accross WP, I don't know! I think adding an infobox is a big edit to make and it would only be polite to post the intension on the talk page prior to adding it. It is a bit like adding a <nowiki>{{wait}}</nowiki> tag before doing a big edit, as I think it is proper to warn people that I am in the process of structuring a large edit. Likewise, If I start a big project which I plan on taking to FAC, I build it in my sandbox and then post a message on the talk page asking if anyone agrees or opposes me moving what I have done accross to the mainspace. If I don't hear anything within a week I go ahead with the move. Anyway, great to hear from you and I await your thoughts on SchroCat's idea. --'''<span style="text-shadow:7px 7px 8px Black;">]<sup>]</sup></span>''' 18:55, 13 May 2013 (UTC) |
|
:::Rexx and I have both asked that you enumerate "the specific and concrete arguments they are bringing here against the proposed infobox in ''this'' article"; yet all the points that you make, are about infoboxes ''in general''. Your objections include "siblings" (the infobox in this article listed none, let alone non-notable examples), "religion" (not mentioned), "politics" (none again), and "where they got married" (again, no such detail was included). Your reference to "short stubs such as this" suggest you may even have been thinking of the wrong article. Similarly, the infobox in this article did not "" nor "" (though of course that's on my system; it's futile to try to achieve a perfect layout on any one system, since there are so many variables between what each of us uses). Similarly, your claim that "Frank Matcham " occurred four times is demonstrably false. I repeat my suggestion that such generic objections should be made in a centralised RfC. Likewise, the collapsed infobox, with hidden content, hasn't been implemented across WP because it finds no favour, unlike the million-plus uncollapsed infoboxes we have (I'm aware of only a handful of examples; each ] by vehement opponents of infoboxes who have similarly been unable to make a case against having one). Collapsing the infobox not only defeats its primary purpose, of providing a ''quick'' and ''convenient'' fact-list for those readers who desire or find useful such a thing (and there is evidence that readers they do), but also hampers the usefulness of providing accurate machine readable metadata, since hidden content is more likely to be overlooked when pages are updated. However, if you still think we should adopt that model despite such shortcomings, then - again - a centralised RfC should be the way forward. |
|
:::Rexx and I have both asked that you enumerate "the specific and concrete arguments are bringing here against the proposed infobox in ''this'' article"; yet all the points that you make, are about infoboxes ''in general''. Your objections include "siblings" (the infobox in this article listed none, let alone non-notable examples), "religion" (not mentioned), "politics" (none again), and "where they got married" (again, no such detail was included). Your reference to "short stubs such as this" suggest you may even have been thinking of the wrong article. Similarly, the infobox in this article did not "" nor "" (though of course that's on my system; it's futile to try to achieve a perfect layout on any one system, since there are so many variables between what each of us uses). Similarly, your claim that "Frank Matcham " occurred four times is demonstrably false. I repeat my suggestion that such generic objections should be made in a centralised RfC. Likewise, the collapsed infobox, with hidden content, hasn't been implemented across WP because it finds no favour, unlike the million-plus uncollapsed infoboxes we have (I'm aware of only a handful of examples; each ] by vehement opponents of infoboxes who have similarly been unable to make a case against having one). Collapsing the infobox not only defeats its primary purpose, of providing a ''quick'' and ''convenient'' fact-list for those readers who desire or find useful such a thing (and there is evidence that readers they do), but also hampers the usefulness of providing accurate machine readable metadata, since hidden content is more likely to be overlooked when pages are updated. However, if you still think we should adopt that model despite such shortcomings, then - again - a centralised RfC should be the way forward. |
|
::: The information in the infobox ''on this article'' includes birth and death dates and locations, resting place, and nationality, which I trust we can all agree are fundamental and unequivocal. The occupation was given as "Theatrical architect". Do you wish to challenge that? I agree that the "Notable work(s)", Schrocat's only objection to the specific infobox instance in question, were relatively arbitrary; I gave the four that are deemed (equally arbitrarily?) important enough to go in the lede, plus what I considered to be his most well-known example outside London. That choice is open to challenge, but, with this being a wiki, that ls possible without removing the entire infobox. That just leaves "Influenced", which is often a more nebulous matter, but the two names I included were both people who, the article says, were trained by Matcham - and by definition, a trainer influences. Are you perhaps concerned that some other, important detail was omitted? <span class="vcard"><span class="fn">]</span> (<span class="nickname">Pigsonthewing</span>); ]; ]</span> 20:21, 13 May 2013 (UTC) |
|
::: The information in the infobox ''on this article'' includes birth and death dates and locations, resting place, and nationality, which I trust we can all agree are fundamental and unequivocal. The occupation was given as "Theatrical architect". Do you wish to challenge that? I agree that the "Notable work(s)", Schrocat's only objection to the specific infobox instance in question, were relatively arbitrary; I gave the four that are deemed (equally arbitrarily?) important enough to go in the lede, plus what I considered to be his most well-known example outside London. That choice is open to challenge, but, with this being a wiki, that ls possible without removing the entire infobox. That just leaves "Influenced", which is often a more nebulous matter, but the two names I included were both people who, the article says, were trained by Matcham - and by definition, a trainer influences. Are you perhaps concerned that some other, important detail was omitted? <span class="vcard"><span class="fn">]</span> (<span class="nickname">Pigsonthewing</span>); ]; ]</span> 20:21, 13 May 2013 (UTC) |
It is not in the best interests of the project to require consensus before editing an article. Our encyclopedia has grown because we allow anyone to edit and bold editing is the commonest way of establishing consensus, so I would always counsel against bringing forward arguments that relied on an appeal that a consensus has to be sought before editing. The value of infoboxes in any article includes that they do provide the "lazy" overview - they are a condensation of the key points of the lead in just the same way that the lead is a condensation of the key points of the whole article. I would urge everyone not to dismiss lightly the argument that we should not be prejudging how our readers consume articles. If a visitor to our site only wants a brief, "dumbed-down" overview, who are we to deny them that facility? We must always remember we are writing Misplaced Pages for all of our readers (including re-users), not for our editors. Of course the teacher in me wants the reader to read the whole article, but I must recognise that it is not my place to insist on that.
Infoboxes not only supply a very short summary, though. They provide a means of marking up some of the data in standardised format (this is called a microformat) so that the resulting HTML can be read by automated tools and aggregated for easy re-use by third parties. Additionally, for at least the last five years, Google has been using our infoboxes as one of the primary means of improving the natural language capabilities of its page reading tools. For example Google will correctly identify a birth date in the lead perhaps about 70% of the time; if it reads a "birth date" parameter in an infobox then it accurately identifies the correct birth date more like 95% of the time. There's a Google tech talk that describes how they can use common structures like {{infobox person}} (which is used on a massive number of articles) for artificial intelligence research at http://www.youtube.com/watch?v=cqOHbihYbhE for anyone who has the time to watch it. Now I agree that not every editor will put value on writing articles so that they are more usable by Goggle and other third parties, but I submit that it has great value. Our mission is to create a world where every single human being has free access to the total sum of human knowledge. We won't do that on our own, and we are going to have to accept that the Googles of this world and the other re-users are some of the most valuable partners we have in getting closer to our goal.
Just as those three advantages of infoboxes need to be considered, there are many reasons why infoboxes may disadvantage an article: the extra effort of creating and keeping an infobox updated and synchronised with other data in the article; the aesthetic considerations associated with the article's images or a large infobox swamping a stub-sized article; and other perfectly respectable reasons that vary from one article to another. Nevertheless, I would respectfully suggest that we editors are not able to predict with any accuracy which factors are most important in a generic class of article. A very short chemistry article with a huge infobox looks awful, while consensus has agreed that a large, well-crafted biography such as Charles Darwin (a featured article) is able to sustain a large infobox. I would therefore ask that Cassianto and SchroCat (both editors I respect) should consider carefully the arguments I make here and try to explain to Andy (another editor I respect) the specific and concrete arguments they are bringing here against the proposed infobox in this article, and listen to Andy's case with respect - I would equally expect Andy to respect the reasoning of you both even if he does not agree with it and wants to debate point-by-point. Without that dialogue, and a willingness to listen carefully to each other, you won't be seeing where common ground lies and where compromise is possible. We need to be able to do that if we want to avoid the scenario where two distinct sides are polarised and simply edit-war to see who can force their preferred version into an article. That would indeed be a failure of the processes that have created the project we all so passionately believe in. --RexxS (talk) 02:22, 13 May 2013 (UTC)